Audacity Forum

Even if I'm always cited as the "original" author of the "Vocoder" effect, it was never *my* idea to include the vocoder in the standard Audacity distribution, mainly because Audacity lacks nearly everything that's needed to work with the "Vocoder" in an at least semi-reasonable way. The main reason...

The "quick & dirty" solution would be to type the frequency value with the keyboard into the small text window beside the slider. As far as I can see from the code, the plugin works with frequencies up to samplefrequency/2, the 10kHz is only an artificial limitation of the slider range. Just tested ...

I guess that we could eventually end up lots of different vocoder effects. I still would like to have a "unified" vocoder effect, but I'm afraid that this is again a lot of work. There are still a lot of internal Nyquist details I still haven't fully understood. If I use e.g. a single Nyquist "osc"...

I agree, the "Vocoder" is a fundamentally different effect than the "Easy Vocoder", even if both names sound very similar. The main internal difference and the main reason why combining both effects is not as easy as it sounds is that the "Vocoder" uses one single carrier for all vocoder bands, whil...

If anybody wants to play with the "Easy Vocoder" effect: Download: http://www.audacity-forum.de/download/edgar/plugins/vocoder/easy-vocoder.ny - right-click -> save target as... The "Easy Vocoder" needs no special stereo audio tracks with "carrier" and "modulator" channels, it can be applied to an o...

An audio track rectifier with Nyquist in Audacity_1.3.13-beta is dead easy. Select the [part of the] Audacity audio track you want to rectify, then open "Effect > Nyquist Prompt" and copy the following code into the "Nyquist Prompt" text field: (s-abs s) Then click "OK". A complete "analyze" plugin ...

A few hours later the next one, this time on a Mac: [*] http://www.audacity-forum.de/post/21795 - error: "Reference to invalid character in line 9" @Gale: I will try to produce a broken Audacity project with detailed descriptions and attach it here in a post, so you (or any other person) may test it...

I don't know what GEdit says but I know that Gedit is crap. GEdit can handle UTF-8 only and everything else is pretty much a mess. That's why I don't use it. Emacs says: http://www.audacity-forum.de/post/21648 - ISO-8859-1- [project name contains german umlauts] http://www.audacity-forum.de/post/216...

The bug has nothing to do with Unicode vs. non-Unicode builds, its always one and the same Audacity build that cannot read its own project files any more. It's correct that non-Unicode Audacity builds write ISO-8859 encoded .aup-files, what is strictly spoken wrong according to the XML specification...

With Audacity_1.3.12 and 1.3.13 beta in the german Audacity support forum I have an increasing number of complaints that Audacity cannot read .aup project files that Audacity itself has written before without raising errors. The effect is that the complete project cannot be opened anymore. Examples ...