I have Audacity 2.2.2 and just installed Izotope RX7 on my computer. Izotope’s System Requirements page says:
“RX 7 can be used as a standalone audio editor, as a standalone audio editor connected to your host via RX Connect, or as a suite of plug-ins…Supported Hosts: Audition CC 2018, Ableton Live 9 - 10, Cubase 9.5, Digital Performer 9, Final Cut Pro X*, FL Studio 12, Logic Pro X, Nuendo 8, Premiere Pro CC 2018, Pro Tools 10 - 12, Reaper 5, Reason 10, Studio One 3 - 4”.
– Does this mean that RX7 won’t integrate with Audacity? Or just that to use with Audacity it must be treated as a plug-in suite?
– If the latter, where are instructions on how to setup RX7 for this purpose?
– RX7 has both 32-bit and 64-bit versions. Which should I use with Audacity?
– Same questions for Audacity v2.3, which I’ll probably install soon.
In Windows10 with Audacity v2.4.2 I use several Izotope RX7 plugins (especially Mouth DeClick) fairly successfully with Audacity.
Questions about Enable checkbox and Bypass button, using Mouth DeClick as an example:
At the bottom of the plug-in’s control screen there is an Enable check box and three arrow icons indicating forward, fast backward, and fast forward.
With the Enable box unchecked the plug-in works OK after clicking Apply; no audio output is produced while the plugin is working. Clicking the arrows has no effect.
With the Enable box checked, the Apply button works the same as with the box unchecked. But clicking the forward arrow triggers very slow plugin action that creates distorted audio output as it works; the other two arrows have no apparent effect.
The Bypass button toggles on and off, and the plugin is apparently inactivated with Bypass is on.
– What is the purpose of running the plugin with Enable checked?
– With Enable checked, why do the fast back & forward arrows have no effect?
– What is the purpose of running the plugin with Bypass on, as opposed to not running the plugin at all?
Further, Izotope guru Don Baarns says that the Enable box and three arrows aren’t in RX7’s own control panel for these effects, but were added to them by Audacity for use as plug-ins. If he is correct, why so?
I think you need to look at how these controls work in an effect that is fully supported by Audacity, such as the “Bass and Treble” effect (Bass and Treble - Audacity Manual)
– It is sometimes useful, especially when using subtle effects, to compare the sound with the effect against the “dry” sound without the effect (when the effect is “bypassed”). You can do this by toggling the “Enable” checkbox on and off while playing the track.
– Fast forward / reverse should work whether the “Enable” checkbox is checked or not.
– Currently there is no point in applying the plug-in with the effect disabled - that will do nothing.
There is a point to being able to toggle the effect on / off when previewing.
In a future version of Audacity it is likely that you will be able to create a stack of effects. It can be useful to be able to enable / disable single effects within the stack individually.
Audacity uses a common framework for all “real-time preview” effect. Technically, they all inherit from the same base class. This allows Audacity to support many different types of effect (necessary for a cross-platform app) including VST, AU, LV2 and built-in effects without having to develop and maintain separate frameworks for each type and then conditionally compile for each combination that is supported on each platform.
It also means that future development for one type of effect on one platform will benefit all supported effects on all platforms. For example, if a Linux developer adds support for “side chains” in LV2 effects, then Windows users gain that feature for VST effects and Mac users gain that feature for AU effects.