Audacity 3.4 is out now!

Tomorrow…

11 posts were split to a new topic: Joint Stereo vs Stereo

After this update came out, my latest project (with about 3 hours of recording in it) won’t open any longer. When I attempt to open it, it gives me the “Audacity failed to read from a file in C:.” error message. After going through all the steps for the suggested fix (downloading 2 exe files from github, putting them in a special folder in your downloads, etc. I then load up my cmd prompt, go through the steps, and after I go through the “dir” command, nothing else works. It simply stops by saying “unable to open database file.”

So, I’m not sure what to do now.

I installed 3.4 this morning and I have a problem now that I do not know how to fix. When I try to record the entire track is filled with bright red. No purple waveforms as I is usual. I tried rebooting my 'puter, downloading it again and re-installing— none of that works. My microphone and speakers are fine. Does anybody have any ideas what is wrong? I just used Audacity last week and everything was fine. I’m sad today!

It is a bug on 24-bit recording with Audacity 3.4.0 . Audacity team said they will fix a release of this today

1 Like

As mentioned in step 10 of the directions here: Corrupt or Otherwise Broken Audacity Project Recovery, the message “unable to open database file”, [means] you have simply mistyped the file name or the .aup3 file name extension.

Note: Windows sometimes hides file extensions. To make them visible, go to File Explorer, and click on the View Tab. On Windows 10 in the three checkboxes, select “File name extensions”; On Windows 11, select “Show”, then “File name extensions”.

Updated Audacity to 3.4.0 None of the previous project files are now readable. Running Win11.
image
It states 'the following projects were not saved properly the last time Audacity was run … ’ The Recover Selected option does not work. I get a crash report but a message ‘Failed to send crash report’

Got it. Thank you so much. Works now.

Although, I will say, the next snag I came to (incase someone else is reading this having the same issue) was that I had labeled the file “broken.aup3” myself, then of course the program labels the file with it’s own instance of “.aup3” - stupid mistake, I know, but caused me a lot of hastle. Next was that even though it eventually DID work and there was now a file in the cmd directory that was a recovered version (in my case, due to my mistake, now labeled “broken.aup3.recovered.aup3”), I finally realized I couldn’t just go to File>Open in Audacity and open the file there. I actually had to just copy paste the correct file name in the cmd prompt and hit enter and have it launch from there…since for whatever reason that recovered file only shows up in the cmd dir, and not from your File>Open file folder for AudRecover.

I’m certain there’s a shorter way of saying that (if someone needs clarification later on, lmk). I don’t have time to edit rn—I have to get in there and get the file finished and sent to my client! Thanks again, jademan :green_circle:! :slight_smile:

Do you have the same issue with Audacity 3.3.3: Old Audacity versions download

or with Audacity 3.4.1 which hopefully will be available later today here: Audacity ® | Downloads

Glad you got this sorted! :grinning:

1 Like

We published two patches for this release.

3.4.1

Full changelog: https://support.audacityteam.org/additional-resources/changelog/audacity-3.4.1

Highlights:

  • #5467 Fix 24-bit recording.
  • #5488 Fix a crash with .aup importing.
  • #5389 Stereo tracks no longer randomly split into mono.
  • #5007 When exporting a file, the file extension is now always added (except for custom FFmpeg and external program exports).

3.4.2

Changelog: Audacity 3.4.2 - Audacity Support

Highlights:

  • #5555 Copy-pasting behavior now pastes into clips again by default. This can be changed via Preferences → Track Behavior → Always paste audio as new clips.
  • #5571 Fix clips shifting to the right when effects are applied to them.
  • #5106 Fix clicks occurring when overdubbing a project with muted tracks.

Thank you all for your patience!

When exporting, if I name a file and I don’t type “.mp3” after the end of the name of the file, it exports as a document. Usually I can just type whatever file name I want without having to physically type “.mp3” and it will know it export it as mp3. Thanks

@linneas88 install the patch we just released, that fixes that issue!

Thank you for the patch, tho I have a question. The majority of the issues have been fixed but there are bunch more that I addressed in this topic. Especially the first one with “loop selection”. Tested it out in 3.4.1 it still bugs out an crashes audacity/won’t play the audio fully and I work with looping sounds very very often. Above all the list I provided in this topic there is still one more thing that happens to the audio. After “Mix and Render” it lowers the rate from 192 to 44 for some reason. I hope to see them fixed in the future release.

The mix and render thing is probably because you have your project sample rate set to 44.1. You can change it in Audio Setup → Audio Settings.

4 posts were split to a new topic: Opening AUP3 file crashes Audacity

File is from 2022-12-08…

I’m unsure what version I updated from. I’m usually on the latest version.

I have been looking at my project files. Only a handful have been created recently. Those few created after 1 September 2022 are readable. The rest are not.

All the FLAC files created in the export process are readable. The FLAC files on a separate backup are also readable. So I do have a successful way of managing old files.

I’ll wait for 3.4.1 and see what happens.

3.4.1 loaded, and …

No problems.

Many thanks for your speedy work behind the scenes.

Glad to hear you back in business. :grinning: