Audacity 3.0.0 is released!

[chk071]

I could never get past the hideous UI, especially when the buttons were done in pastels.

Same. And, no markers is like .

Well... I always was a Wavelab fan anyway. It has the best GUI, and best handling of the audio editors I've tried, including Soundforge, by far. I used to use a haxed version of Wavelab 15 years ago, version 3 point something, and then bought Wavelab Elements about 8 years ago or so. Sold it one time then, just to buy it again. IMO, it's pretty much without competition.

Audacity is a pretty good example of the state most FOSS software is in.

[Dirtgrain]

No way am I paying $100 (or $500 for Wavelab Pro) just because of the GUI. I get along fine with Audacity, and I'm amazed that it is free.

[chk071]

I didn't pay $100 for Wavelab Elements. I got Wavelab LE (from a Keys magazine DVD, I think), and then upgraded to Wavelab Elements, and then upgraded that a few versions, which always cost something like 25 €, with a few discounts over the years, often bringing down the upgrade price to 20 € or so. It's really not that expensive.

Of course, you gotta know if that's worth it for you. With Audacity, you definitely get what you pay for though. Does it even support ASIO natively now, or is it still using PortAudio? Doubt it can even support ASIO natively, due to the license, can it?

[SLiC]

Its free, so it is what it is, but it won't see 64-bit versions of VST plug-ins (or VST3s), so not much use if you want to process with VST fx.

[mike_the_ranger]

Does it even support ASIO natively now, or is it still using PortAudio? Doubt it can even support ASIO natively, due to the license, can it?

The offical Audacity version of course can't support ASIO as it would violate the license agreement of Steinberg (oh damn, not them again...) regarding open source software. But with every official version comes an "unofficial" version, having the ASIO compiled in

I like the development of Audacity over all these years. It shows open source stays relevant, even on Windows/Mac. And the more people get f*cked up by the usual suspects, the more tools like this are in the rise.

[Johnny!]

Wow, it's like Windows 95 is still alive and well...

With free apps like OcenAudio available, I wouldn't use this even if you paid me.

[rasmusklump]

The "expert" again.
No markers ? Yeah...

[Etienne1973]

... no markers is like .

Audacity's markers.

Source: https://manual.audacityteam.org/man/lab ... html#point

[anttimaatteri]

i am waiting for the "why did you leave audacity 3" thread to pop up soon

[KenjiDeVries]

All the GUI style discussion but then we have plugin devs around that are solely famous for their fugly plugins...
Matter of taste and what you want to do with it. I still work with CoolEdit, because it just works and isn't overcomplicated. I guess it's the same for Audacity. And there's a reason why it gets mentioned almost everytime someone asks for an audio editor.

[SonicBlue555]

... no markers is like .

Audacity's markers.

Source: https://manual.audacityteam.org/man/lab ... html#point

Good to know, but, have you tried using them? As soon as you CTRL+M to set a marker your playback button (spacebar) is locked into the label renaming field, and if you press CTRL at the wrong moment, the screen starts to shake back and forth because it still points you to the label renaming thing, and the transport cursor that's moving tries to adjust the view position

[chk071]

I wonder why they don't just use markers. It's much better to see the marker line over the actual waveform, especially when you are trying to hit the zero crossings.

Can you even snap to zero crossings with the labels? That's, like, the minimum I'd expect from markers/labels/whatevers.

[Sam-U]

If markers are the biggest problem, Audacity can't be that bad.

[Etienne1973]

As soon as you CTRL+M to set a marker your playback button (spacebar) is locked into the label renaming field, ...

I give the marker a name and then move on. Problem solved.

... and if you press CTRL at the wrong moment, the screen starts to shake back and forth because it still points you to the label renaming thing, and the transport cursor that's moving tries to adjust the view position

Can't reproduce that here. But I'm on Mac.

I wonder why they don't just use markers. It's much better to see the marker line over the actual waveform, especially when you are trying to hit the zero crossings.

Can you even snap to zero crossings with the labels? That's, like, the minimum I'd expect from markers/labels/whatevers.

Place cursor near zero crossing in audio track(s), Hit Z (snaps to zero) and then CTRL+B (adds label/marker). Done.

[chk071]

If markers are the biggest problem, Audacity can't be that bad.

I think it has already been mentioned that the GUI is a complete train wreck.