Edgar, it’s a shame if your code offerings are not accepted for review (!), I hope they reconsider that position.
It would be good if you had a web page or blog to keep track of changes/releases of your version of Audacity.
Absolutely! Still, in response to my offerings, no exaggeration. I guess I shouldn’t complain as the philosophy engenders an environment where those who wish to charge to modify Audacity have more leverage. I almost never charge for my modifications but those who have paid have paid very well.
I use this forum to propose enhancements and as a repository of code offerings. I use private email with my “clients” to manage their personalized versions (each is distinctly different). As far as my own personal version goes, it’s been stable for quite a few years; there have been a couple of fairly trivial bug fixes (none involving functionality) and some very minor enhancements to improve my own workflow (mainly involving better voice control - due to disabilities, I work hands-free using Dragon Professional (NaturallySpeaking), KnowBrainer and AutoIT3).
To make it even more interesting, I actually have 3 different personal versions - the one you’ve seen here, one highly customized and stripped down to only do Chains, and a 3rd which has no GUI (works only from the command line; has a very tiny memory footprint and does not leak memory like Audacity 2.0.* does; and, among other things, can process thousands of files [Audacity on Windows is limited to something in the ballpark of 500 files before it crashes] doing things like: create a folder based on the file name, move said file into said folder, create an Audacity project from said file and said folder with said project being the result of running various effects and/or chains on said file.
I’m not much into social media so don’t do blogs and my webpage is very static.
@Edgar: your Audacity [ cool: you put some ‘work in-RAM’ options (i guess it shows in ‘record’ but i didn’t see an effect with 'open’or ‘play’ (the Project still grows in size…). It would be great to have the option to have the whole Project in RAM and only save it to disk at will …] I hadn’t tried because some post-v2.06 really needed improvements [new Crossfade Clips, …, specially: VST & Nyquistr preview + presets and Macros + keyboard keys; I have eg many Compressor presets as Macros with shortcuts…].
Finally because of the couloring +, I decided to test it in case Macros shortcuts was maybe added, but I see that even though the ‘selections’ couloring options are there, they only work for the background, the Wave’s Peak and RMS -selected or not- always look the same like in regular Audacity, idk, maybe you put those options there as placeholders for a future when the base code allowed them to work…
When it became obvious that mainstream Audacity was not going to use my concept to color things, I stopped developing options which I would not use unless a client asked/paid me to do so.
Hello,
The feature creep theory is a mountain of a stumbling block to developers, I understand that. Though to put a hold on new menu items or preferences, is a bit strange, as the interface shouldn’t hold back the development, as that is another coding block, so sacrificing development of the interface, jars with my education. But props for the developers for compiling such an amazingly featured program that is also accessible.
The problem with selecting part of a waveform and having a distinct enough edge to increase selection ease, never used to be a problem in previous versions of audacity. I hope the next upgrade sees how important this is.
A beginners interface should be a ‘thing’ if developers are worried to not put them off.
Bye