unable to parse project information

[jesseaudacity]

let me know if you need help on testing the beta/alpha version.
Jesse

[jademan]

let me know if you need help on testing the beta/alpha version.
Jesse

You can check for the most recent Audacity alpha at Workflow runs · audacity/audacity · GitHub

Click on the most recent item with a green check mark, that also has

1. the word “master” highlighted in blue, and
   (2) the phrase “pushed by JamesCrook”

scroll down to Artifacts.

Do NOT use an alpha for production work!

Please report back your findings…

[jesseaudacity]

let me know if you need help on testing the beta/alpha version.
Jesse

You can check for the most recent Audacity alpha at Workflow runs · audacity/audacity · GitHub

Click on the most recent item with a green check mark, that also has

1. the word “master” highlighted in blue, and
   (2) the phrase “pushed by JamesCrook”

scroll down to Artifacts.

Do NOT use an alpha for production work!

Please report back your findings…

Thanks, I did a quick check with two pcs for test.
Following is my steps.

Build number1543

1. save aup3 with PC1 on NAS folder 1 (full path in English.) O:\AUDACITY BUILD

this is file 1

2. open aup3 with PC2 from the same NAS folder. O:\AUDACITY BUILD
3. save aup3 on PC2 to another folder with CHT folder name.

this is file 2
O:\AUDACITY BUILD\繁體中文測試
this take a very long time to completed the saving process.
Also, file been lock for around 10 min.
then, both PC1 and PC2 can’t open the file. can says file save error


File 1 can be open on PC1/2
File 2 file been lock on PC2.

and there is a null file been created in the audacaity folder on PC2.

PC2_Audacity_dbgrpt-23280-20210403T000950.7z (60.2 KB)

[jademan]

Thanks, I did a quick check with two pcs for test.
Following is my steps.

Build number1543

1. save aup3 with PC1 on NAS folder 1 (full path in English.) O:\AUDACITY BUILD

this is file 1

2. open aup3 with PC2 from the same NAS folder. O:\AUDACITY BUILD
3. save aup3 on PC2 to another folder with CHT folder name.

this is file 2
O:\AUDACITY BUILD\繁體中文測試
this take a very long time to completed the saving process.
Also, file been lock for around 10 min.
then, both PC1 and PC2 can’t open the file. can says file save error


File 1 can be open on PC1/2
File 2 file been lock on PC2.

and there is a null file been created in the audacaity folder on PC2.

Thanks for the update. Please take a look at this link and see any of these Microsoft workarounds help: KB4564002: You might have issues on Windows 10, version 20H2 and Windows 10, version 2004 when using some Microsoft IMEs - Microsoft Support

[jesseaudacity]

Thanks, I did a quick check with two pcs for test.
Following is my steps.

Build number1543

1. save aup3 with PC1 on NAS folder 1 (full path in English.) O:\AUDACITY BUILD

this is file 1

2. open aup3 with PC2 from the same NAS folder. O:\AUDACITY BUILD
3. save aup3 on PC2 to another folder with CHT folder name.

this is file 2
O:\AUDACITY BUILD\繁體中文測試
this take a very long time to completed the saving process.
Also, file been lock for around 10 min.
then, both PC1 and PC2 can’t open the file. can says file save error


File 1 can be open on PC1/2
File 2 file been lock on PC2.

and there is a null file been created in the audacaity folder on PC2.

Thanks for the update. Please take a look at this link and see any of these Microsoft workarounds help: KB4564002: You might have issues on Windows 10, version 20H2 and Windows 10, version 2004 when using some Microsoft IMEs - Microsoft Support

confirm above are works normally with first run testing.
But still have null file in the aduacity folder.

[jademan]

…confirm above are works normally with first run testing.
But still have null file in the aduacity folder.

The first Release Candidate for Audacity 3.0.1, RC01, was just released. If you would like, you can test it to whether it addresses your issues:

Audacity devel

Please DO NOT run production with this release.

[nightraven]

I tested 3.0.1 RC01 twice and the issue didn’t occur. I will test it further.

[waxcylinder]

The Release Candidate for 3.0.2 is just out now (we skipped 3.0.1)

Peter.

[jesseaudacity]

The Release Candidate for 3.0.2 is just out now (we skipped 3.0.1)

Peter.

Please note that the null file in the root folder is normal or not.
thanks.

[waxcylinder]

Please note that the null file in the root folder is normal or not.

This was raised with the Release Manager - he replied:

The null file is from March 28th, and I have no idea what it means.

We will keep an eye on this.

WC

[TakamiChie]

I extracted and checked the attachment Windows_64bit_ac71178 of CMake Build #1581.

The results are as follows:

1. open the aup3 file saved as aup3 in 3.0.0… success
2. overwrite the opened file… success
3. save the opened file as an alias file… generally succeeds, but in rare cases it fails to save.
   
   
   For 3, I tried to analyze why the file could not be saved, but I could not figure it out.

The file that I couldn’t save was originally an aup file created with 2.x and loaded. However, it does not necessarily mean that the file cannot be saved.

However, once the write operation failed, the file could not be saved until I restarted Audacity.

[jademan]

I extracted and checked the attachment Windows_64bit_ac71178 of CMake Build #1581.

Thank you very much for your report. The build you are using is not an official alpha build, and this build is not important. It was done by someone indirectly related to the project and includes experimental and/or proposed code that may or may not be related to Audacity. As I said earlier, be sure to:

Click on the most recent item with a green check mark, that also has

1. the word “master” highlighted in blue, and
   (2) the phrase “pushed by JamesCrook”

However, in this particular case, I don’t believe it makes any difference. I have forwarded your report to the developers. They are keenly interested. Thank you very much.

Now that we are getting extremely close to the 3.0.2 release, the developers are posting Release Candidates. The most recent one can be found here: PRE RELEASE Audacity devel. Right now, it is RC01, but I believe RC02 is expected with a day or so. These release candidates are preferred for testing over the alpha builds. Thanks again very much for your efforts and your reports, they are greatly appreciated, and please do continue.

[J_Aguinaldo]

Unable to parse project information
the log showed

Error: Unable to parse project information.
16:11:10: Help button pressed: PageName FAQ:Errors_on_opening_or_recovering_an_Audacity_project, releasePageName faq_errors_on_opening_or_recovering_an_audacity_project.html
16:11:10: webHelpPage https://manual.audacityteam.org/man/faq_errors_on_opening_or_recovering_an_audacity_project.html, localHelpPage C:\Program Files (x86)\audacity\help\manual\man\faq_errors_on_opening_or_recovering_an_audacity_project.html
16:18:09: ParseString error: Error: not well-formed (invalid token) at line 1
===begin===ã¼€ç €æ´€æ°€â€€à°€
===end===
16:18:09: DBConnection SetError
ErrorCode: 0
LastError: Unable to parse project information.
LibraryError: Error: not well-formed (invalid token) at line 1

[jademan]

Thanks for your report.

What version of Audacity were you runninng? Help > About Audacity

What language are you using?

A screen-shot is always useful, along with any other detail about the history of the project and what you were doing at the time of the problem.

[Immortal]

I have been working on a project for a few days now, I spent several hours in the recording, but suddenly audacity crashed when I was trying to playback my audio. Audacity was not responding and I had to close the program, hoping that I’d be able to recover my project the next time I open it.
I clicked on ‘Recover’, but it wasn’t able to recover my project, instead it showed a dialog box which said ‘unable to parse project information’. I have attached the screenshot of the dialog box.

NOTE : I am using the Audacity version 3.0.2

This is what I am getting after clicking on the ‘show log’ button :

LibraryError: Error: not well-formed (invalid token) at line 1
16:02:12: Error: Could not parse file “D:\Recordings\Numb\Numb.aup3”.
Error: Unable to parse project information.
16:13:33: ParseString error: Error: not well-formed (invalid token) at line 1
===begin===ã¼€ç €æ´€æ°€â€€à°€
===end===
16:13:33: DBConnection SetError
ErrorCode: 0
LastError: Unable to parse project information.
LibraryError: Error: not well-formed (invalid token) at line 1

Please help fixing this issue as soon as possible

[jademan]

Curious… This looks identical to akingreid’s post: https://forum.audacityteam.org/t/unable-to-open-project-due-to-unable-to-parse-project-information-message/62364/1

I almost wonder if it is the same file. Nonetheless,

I’ll take a look at this file if you care to zip it up and upload it to a public file server, then post or PM me the link. No promises.

[Staxomatix]

Hello All,

Fingers crossed you can help.

Error Opening Project / Unable to parse project information

Audacity Version: Audacity 3.1.2
Windows Version: 10.0.19043 Build 19043
System uses English US, English Canada Multilingual Standard, and German keyboards. Unsure which was active when creating project.

The log is too long to screenshot. I have pasted a copy below with the waveblock positions stripped out.

Assistance or redirects would be most appreciated. Already attempted swapping project and autosave in SQL DB Browser.

{
“timestamp”: 1638485113,
“event_id”: “fc179eeb48d1dd4da0d19468342f79ea”,
“platform”: “native”,
“release”: “audacity@3.1.2”,
“contexts”: {
“os”: {
“type”: “os”,
“name”: “Windows”,
“version”: “10.0.19043”
}
},
“exception”: {
“values”: [
{
“type”: “Error_Opening_Project”,
“value”: “Unable to parse project information.”,
“mechanism”: {
“type”: “runtime_error”,
“handled”: false,
“data”: {
“log”: "Error: Unable to parse project information.\n17:45:13: ParseString error: Error: not well-formed (invalid token) at line 3\n===begin===<?xml version=\"\" standalone=\"no\" ?>\n<!DOCTYPE project PUBLIC \"-//EN" "http://" >\n<project xmlns="http://" version="" audacityversion="" sel0="" sel1="" vpos="0" h="0" zoom="" rate="44100" snapto="off" selectionformat="hh:mm:ss + milliseconds" frequencyformat="Hz" bandwidthformat="octaves"><><wavetrack name="Audio Track" isSelected="1" height="150" minimized="0" channel="0" linked="3" mute="0" solo="0" rate="44100" gain="1" pan="0" colorindex="0" sampleformat="262159"><waveclip offset="" trimLeft="0" trimRight="0" name="Audio Track #2" colorindex="0"><sequence maxsamples="262144" sampleformat="262159" numsamples="90930075"><waveblock start="0" blockid="3036"/><waveblock start="262144" blockid="2262"/><waveblock start="524288" blockid="3041"/><waveblock start="786432" blockid="2264"/><waveblock start="1048576"

…
[several thousand lines of waveblocks]
…

\n===end===\n17:45:13: DBConnection SetError\n\tErrorCode: 0\n\tLastError: Unable to parse project information.\n\tLibraryError: Error: not well-formed (invalid token) at line 3\n"
}
}
}
]
}
}

[jademan]

Assistance or redirects would be most appreciated. Already attempted swapping project and autosave in SQL DB Browser.

It is good to see that you are showing initiative.

So go ahead and zip up your .aup3 file and upload it to a public file sharing service. Post (or PM me) a link. I’ll take a look at it.

[Staxomatix]

You can download a copy here:

[link removed by jademan for privacy]

[jademan]

OK, so the good news is that your project will load in the new 3.1.3 beta. See this post for additional information and insight: https://forum.audacityteam.org/t/help-internal-error-at-d-a-audacity/63456/4

Please report back on your final status (especially if you need any additional help). I have removed your link for privacy considerations.