Archive for the ‘VST’ Category

Adobe Premiere CS5.5: Issues With VST

Saturday, September 1st, 2012

Just as I’m starting to get used to Adobe Premiere CS5.5, I notice that its audio effects listing (in menus etc.) does not my system’s VST collection.  Most annoyingly, because of that, my iZotope Ozone effects are excluded from Premiere.  Seems unreasonable, given my long track record of employing such plugins in Sony Vegas.

I spent a good hour or two trying to understand and solve this, including much googling.  At the end of that, I’m not sure what the problem is exactly, but it does look to me like Premiere is slightly lacking with regard to its ability to interface to VST effects.  For a start, one of its assumed registry entries appears inappropriate to Windows 7 64-bit.  Having hacked that into shape, Premiere at least noticed the existence of Ozone (and other VST effects on my system) then found itself unable to load it.

The best solution I found was really a work-around.   Prom Premiere timeline, [aClip >RtClk> Edit in Adobe Audition].   That application has no trouble recognising iZotope plugins.  However before getting too blinkered, try the native Audition effects first, including Noise Reduction, because they are pretty-good.

(more…)

Posted in Adobe, audio, iZotope Ozone, Premiere, Uncategorized, VST | No Comments »

VST Plugins with Adobe Premiere

Monday, January 2nd, 2012
  • http://premierepro.wikia.com/wiki/Virtual_Studio_Technology
    • <<<
    • If you want to actively prevent Premiere Pro from using one or more VST plug-ins, create a text file called Blacklist.txt listing the filename of each plug-in one per line. Put the text file in the same folder as the plug-in files, one blacklist file per folder. The blacklist file is read only when Premiere Pro starts up.
      • You must restart your computer for the Blacklist.txt to work.
    • ….there is a limit to the number of VST effects that can appear in the list in the mixer panel, however all supported VST effects should appear in the list in the effects panel.
    • If some VST effects are not available in Premiere Pro when you expect them to be, search your hard drive for a file called Plugin Loading.log after configuring your search to find hidden files. The log may tell you why a plug-in is not being loaded.
    • >>>

Posted in Adobe, audio, Premiere, VST | No Comments »

VST Plugins

Monday, January 2nd, 2012
  • http://premierepro.wikia.com/wiki/Virtual_Studio_Technology
    • <<<
    • If you don’t have any VST plug-ins there are a number of them at:
      • http://www.kvraudio.com/get.php
      • http://www.kjaerhusaudio.com/classic-series.php
        • (Great Reverb, Compressor/Limiter, Delay, EQ and more… They sound good as well).
      • at http://www.elementalaudio.com you can download a free VST ‘effect’ called “Inspector” which will monitor your audio as you play your sequence, and, among other things, tell you by how much you have exceeded the 0dB maximum permitted level. You can then reduce the monitored fader by that amount and be confident there should be no clipping. It comes remarkably well documented (for freeware) and the help file is worth a quick check through. And another tip – if you export just the audio of your project with the “Inspector” vst window visible, it will provide the analysis of levels and clipping at high speed – on my PC, in about 4 mins for a 40 minute .avi – and the results it gives correlate with analysis in Audition, so it appears you can depend on it. In my test file, it showed that the level needed to be reduced by 0.4dB to avoid clipping – which was the amount by which I’d pushed the fader up before running the test. Using this method it would appear you don’t have to sit glued to the meters all the way through your project to avoid clipping.
    • >>>

Posted in audio, VST | No Comments »

iZotope Ozone 5 in Adobe Premiere?

Sunday, January 1st, 2012

I am a novice user of Adobe Premiere.  Having installed iZotope Ozone 5 I expected it to just appear as one of the audio filters.  However I saw no sign of it.

Web-research:

  • http://help.adobe.com/en_US/PremierePro/4.0/WS1c9bc5c2e465a58a91cf0b1038518aef7-7f0fa.html
    • <<<
    • Premiere Pro supports the Steinberg VST (Virtual Studio Technology) audio plug-in format so that you can add VST audio effects from third-party vendors. Premiere Pro includes VST plug-in effects that are available in both the Audio Mixer and the Effect Controls panel. Track-based VST plug-ins may provide additional controls. Apply VST effects the same way you apply other audio effects to tracks or clips.
    • In the Effects And Sends panels of the Audio Mixer, VST effects appear in the Effect Selection menus. In the Effects panel, they appear in the Audio Effects bin so you can apply them to individual clips. In most cases, VST effects appear in the Audio Effects bin and track type that corresponds to the number of channels the effect supports. For example, stereo VST effects appear in the Audio Mixer track effect menus for stereo tracks only, and in the Stereo bin in the Audio Effects bin in the Effects panel. After you apply any VST effect, you can open a window with all of its controls. You can leave multiple VST editor windows open as long as you want, such as when automating effects, but Premiere Pro closes all VST editor windows when you close the project.
    • If you previously installed a VST-compatible application other tha Premiere Pro, Premiere Pro finds VST effects in the VST folder that already exists. Inside the Plug-ins folder of the Premiere Pro application folder, there is also a VSTPlugins folder with plug-ins that are used only by Premiere Pro.
    • Note: When you use a VST effect not provided by Adobe, the specific control layout and results of the plug-in are the responsibility of the plug-in manufacturer. Adobe Premiere Pro only displays the controls and processes the results.
    • >>>
  • http://forums.adobe.com/thread/682375?start=0&tstart=0
    • <<<
    • I use a set of VST plugins by Voxengo with 32-bit CS4. I recently upgraded to 64-bit CS5. So, I went and snagged the 64-bit versions of these Voxengo plugins. I put them in the C:\Program Files\Adobe\Adobe Premiere Pro CS5\Plug-ins\en_US\VSTPlugins\.
    •  Here’s the info in the Plugin Loading.log file:
      •  Loading C:\Program Files\Adobe\Adobe Premiere Pro CS5\Plug-ins\en_US\VSTPlugins\Elephant.dll
        Loading from the registry…
        The plugin was successfully loaded from the registry.
    •  Yet, the plugins do not show up in the mixer or in the effects list.
    •  I do not get any error messages. Also, I’m using Vista.  Any ideas?
    •  If you’d like to try the plugins yourself, there are free trials here:
    •  Thanks! – Jamez
    • >>>
    • <<<
    • I tried the 8 free Voxengo plugins in Premiere CS5, all of them 64bit and they did not show up.  Curiously enough, these 8 plugins are listed at ehe Adobe websiste  here: http://www.adobe.com/products/plugins/premiere/.
    • I tried the 32bit versions with Soundbooth CS5 (which is a a 32bit app) and they did not show up there either.
    • >>>
  • http://premierepro.wikia.com/wiki/Virtual_Studio_Technology
    • <<<
    • If you want to actively prevent Premiere Pro from using one or more VST plug-ins, create a text file called Blacklist.txt listing the filename of each plug-in one per line. Put the text file in the same folder as the plug-in files, one blacklist file per folder. The blacklist file is read only when Premiere Pro starts up.
      • You must restart your computer for the Blacklist.txt to work
    • If some VST effects are not available in Premiere Pro when you expect them to be, search your hard drive for a file called Plugin Loading.log after configuring your search to find hidden files. The log may tell you why a plug-in is not being loaded.
    • >>>
  • http://forums.adobe.com/thread/679366?start=0&tstart=0
  • http://forum.recordingreview.com/f44/plz-help-me-abt-izotope-ozone-plugin-18721/
  • http://forums.adobe.com/message/2970290#2970290

    Posted in Adobe, audio, iZotope Ozone, Premiere, VST | No Comments »

    VST Plugins: Folder & Registry Entry

    Sunday, January 1st, 2012

    Trying to understand why Ozone 5 will/won’t show up in various Windows 7 applications,  I discovered that:

    The folder on my system is:

    • [C:\Program Files (x86)\Vstplugins]

    The corresponding registry entry is:

    • HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > VST > VSTPluginsPath
      • The name [Wow6432Node] sounds somewhat unprofessional, but I checked on my system and indeed that’s how it is.

    In Registry Editor:

    • In left-hand “explorer” pane, dial-down to [HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > VST]
    • At that location:
      • Name: (REG_SZ) = [VSTPluginsPath]
      • Value: (REG_SZ) = [C:\Program Files (x86)\Vstplugins]

    Posted in audio, REGISTRY, VST, Windows 7 | No Comments »