Live data from Hacker News

Audacity 4.0

github.com

161–170 of 278 posts

Re: Audacity 4.0

#162
post #97

Earlier quoted context omitted.

My understanding is that the Qt 6 build system is vastly easier to work with. Also, Audacity is not the first major FOSS project to successfully migrate from wxWidgets to Qt: Dolphin, the GameCube/Wii emulator, made a similar migration several years ago[0][1][2][3]. [0]: https://dolphin-emu.org/blog/2017/06/03/dolphin-progress-rep... [1]: https://dolphin-emu.org/blog/2018/02/03/dolphin-progress-rep... [2]: https://do…

>Qt 6 build system is vastly easier to work with. The Audacity team imported their existing Qt interface code from a previous project. Depending on the design, the code smell could have a lot of vestigial parts unrelated to the new project. I have always seen FOSS as the last stop for public domain software. It is supposed to become the stable road future kids walk down to become professionals. The Qt framework is of…

[flagged]

Re: Audacity 4.0

#165

Earlier quoted context omitted.

> or getting a "clicking" noise across clips that I had to remove by manually fading in/out each end of the clip Are you sure this isn't just the typical "clip/crop a sample at the wrong moment, in the middle of a soundwave, and you'll get a pop/click"? This problem happens all across DAWs and hardware samplers and such, usually there is a way to "align to zero-crossings" when you wanna avoid it, or called something…

I think you're right. Audacity does have a "zero-crossings" thing, but when I tried using it a long time ago, it didn't seem to work, and I just learned to do fade-in/out for everything. Maybe I did something incorrectly.

> I just learned to do fade-in/out for everything. Maybe I did something incorrectly.

This is the de-facto standard practice for fixing/working around that particular issue, so I don't think it's incorrect at all :) Besides, however you fix an issue and it sounds good, it's correct :)

Re: Audacity 4.0

#166
post #59

Whatever happened with the post-telemetry fork debacle projects? Tenacity, Sneedacity, or something...

Someone mentions it here: https://news.ycombinator.com/item?id=49549040 https://tenacityaudio.org Seem like they have a few commit every week. 32 Issues closed in a year: https://codeberg.org/tenacityteam/tenacity/activity/yearly Looks healthy?

The Mac build isn't really usable. You have to manually remove the quarantine flag.

Re: Audacity 4.0

#168
post #9

I highly recommend this video [1] by the Head of Software at Muse who had a big part in the development of Audacity 4.0. Some great insights and really fun to watch! [1] https://www.youtube.com/watch?v=QYM3TWf_G38

all of his videos are amazing

Re: Audacity 4.0

#169

Earlier quoted context omitted.

Notation is cool and just right, the more I learned the more I appreciated how great contemporary notation is. Yes it's challenging to read sometines but the subject is challenging too, surely you could try to simplify it for certain applications but you'd lose a lot of flexibility. Fighting notation is like fighting piano keyboard which is also extremely convenient thing to play compared to other stuff, even to grid…

I find conventional Western notation works quite well for communicating notes, rhythms, and basic expression, but it breaks down pretty quickly once you move beyond that. E.g. a lot of the common techniques on electric guitar (bends, palm muting, tremolo/whammy bar stuff, pick slides, slap/thumping, pinch harmonics, raking) don't really have a convenient notational shorthand. That's without even mentioning synthesize…

I'm not sure what you are talking about wrt guitar and standard notation. Finger (PIMA) indication, staccato/legato, vibrato, tremolo, slurs, hammer, pulls, etc...it's all there. I don't see as much notation around hammer/pull as a classical player, but pick up a classical guitar music book sometime...you'll find that everything (guitar-related) you mentioned needing to be included, is already included.

Re: Audacity 4.0

#170

Earlier quoted context omitted.

>Qt 6 build system is vastly easier to work with. The Audacity team imported their existing Qt interface code from a previous project. Depending on the design, the code smell could have a lot of vestigial parts unrelated to the new project. I have always seen FOSS as the last stop for public domain software. It is supposed to become the stable road future kids walk down to become professionals. The Qt framework is of…

[flagged]

Don't worry about it =3
Post reply on HN