Audacity Version 3.4.0 Released - But There's a Bug!

[@audacity]

Hotfix coming very shortly. Apologies for this issue.

[@mmmisterslsl]

Yay

[@slipthetrap]

The 3.3.3 version also had an issue: any check for updates on a Mac causes the software to crash. But the software does work properly when I disabled the auto-check for updates and not check for updates. Thanks for these videos.

[@leafsfanforever2896]

Among other bugs: - Change Pitch does not work (sometimes; usually only if decreasing pitch of selected file; if it works, the selected audio clip moves far out of place). The same movement applies to Change Tempo - Crossfade Tracks bugged (if sitting adjacent to other sections ahead of the selected clip(s))

[@LearnAudacity]

Good to know. Thanks!

[@JesseMortonVO]

God bless ya, man. Hopefully, Audacity folks can find a solution soon for those like me who need to record in 24-bit every now and then

[@LearnAudacity]

It will be fixed in 3.4.1

[@minty_Joe]

I'd recommend, if you can, recording at 32-bit resolution regardless. I find it to be vastly greater quality overall on sound and virtually zero noise (except if there's any coming from a bad cable or such). Sure, the file sizes may be bigger, but it's worth it for the quality of the recording.

[@JesseMortonVO]

@@minty_Joe understandable, it's just that as a voice actor, my clients often request specific audio properties and formats for both auditions and jobs.

[@craigdavis-VOtalent]

Mike, great info. I've done some platforms at 16bit and then mostly up at 32bit. So, never ran into the recent issue you explained. However. ---- I did run into THIS issue... When adding new (or revising) audio in a track...audacity is good at adding an independent audio track (marked by a dark vertical line) within the existing track. No big deal. When you completed your work, you could quickly integrate the audio into your master track by simply putting your cursor and click over the dark vertical line to remove it. But now (in 3.4.0) it does not allow you to remove it and all your similar edits are locked. Now when you hover over the line, it illustrates a bracket that you can widen or thin the new audio to your needs. But you can not eliminate the vertical marker. Maybe I'm missing something. Hope this makes sense. Not sure I may be explaining properly.

[@phetrop2243]

Thank you for having pointed this out! Here on my system (Windows 10, Steinberg UR-242, WASAPI; actually I tried any combination to get below issue sorted, BUT…) I discovered another phenomenon: with 32-bit FP setting the described issue is gone, but there is still an annoying digital „feedback“ artifact in the recording. When I set and pull up line level only high enough, the system starts self-oscillating. Looks as if Audacity picks up noise from the PC or audio i/f even when there is no Instrument played, which is then rocking up, as if there is an „always on“ feedback setting active. This feedback is also clearly audible in the recording. Mhhh…

[@LearnAudacity]

Thanks for the info...

[@deepsleeper]

Thanks for explaining the 24 vs 32 bit float. It had me worried

[@DJWendyJ]

OMG I had this bad noise using Audacity! Now this tells all! I switched to Adobe Audition and my noise floor is minimal.

[@fluffyfetlocks]

I love audition but I don’t believe in subscription software when it isn’t actively innovating

[@baconsledge]

I thought I heard Steve Gibson of SGR say that current versions of Audacity contained many security risks so I have avoided it for a couple years.

[@petersampson9673]

It is fixed in 3.4.1, I just tested on W10 with the 3.4.1 test build

[@LearnAudacity]

Thanks Peter! Are we still looking at next week for the release?

[@petersampson9673]

@@LearnAudacity I think they're trying to get 3.4.1 out today, they are well aware that they have caused problems and need to fix them quickly. And there will be a 3.4.2 which will add a preference for direct copying with creating the splits that they introduced with Copy in 3.4.0 - I've just been testing the developer's branch build for that).

[@petersampson9673]

@@LearnAudacity Muse have just released 3.4.1

[@Fretless1]

Thanks so much😀

[@LearnAudacity]

You're welcome

[@Tomaslaravo]

Audio stops in 3.3 for me when playing back fx from izotope suite of plugins

[@amazinghazels9625]

Thanks !! Just learning :-

[@Kayanlay8803]

How to re-records in the middle of recording track ?

[@_-martin-_]

Why does Audacity still look like a Windows 3.11 application???

[@SpeccyMan]

Probably because it is an application that focuses on function over form.

[@TravelMaximizer]

Nice Thumbnail sir.

[@Rulestoned]

*Sorry there's no such a bug* but my lack of knowledge 😁. -The SOLO button will remain pressed on more than one track,- losing its whole purpose, It has to be turned off manually. In older versions this button couldn't be pressed on more than one track at the same time.

[@minty_Joe]

Did you set the Solo button in Preferences to be for "multi-track" mode? If not, then that's the problem. By default, Audacity sets the solo button to "simplified", which won't allow you to solo more than one track.

[@Rulestoned]

​@@minty_Joe That's exactly what I wanted, *the Solo button to play only one track at a time* (so that clicking it releases any other solo button, muting all tracks except one ) but this version 3.4.1 came with multitrack mode set by default, thanks a lot man, it helped me big time. Peace out =)

[@minty_Joe]

@@Rulestoned I'm glad to be of help to you. It sounds like you may have to play around with that setting and alter it depending on your needs (obviously). There's a few other things I'd like Audacity to add in and hope the team does in the near future. For one, how about multiple input sources being recorded at once and split up into their own separate track? That way if someone has an audio interface with say 8 or more inputs can send those to Audacity, it puts each into their own track. You won't have to record single sessions over and over to get each element separately. And why not? Most digital consoles (like the Midas M32R Live) can do that already.

[@Rivenworld]

It's still spyware no matter what the bit depth.

[@kandavanamsivaguru1861]

👌👌👌