"Configure as Synth" for VST3 is different? Stutter Edit

Author
arachnaut
Max Output Level: -67 dBFS
  • Total Posts : 1168
  • Joined: 2007/05/05 17:24:33
  • Location: Sunnyvale, CA USA
  • Status: offline
2016/06/07 22:07:00 (permalink)

"Configure as Synth" for VST3 is different? Stutter Edit

iZotope Stutter Edit loads by default as a VST audio effect.
 
I click on the properties in the plug-in manager and select it to be configured as a synth.
 
On the next re-scan, the VST2 version appears as a VST instrument.
But the VST3 version stays on the Audio menu in the browser.
If I load the VST3 and check it's properties, it is still marked as a synth and it works fine.
 
In the plug-in manager, the reverse happens - Stutter Edit stays in the VST2 audio folder, but for VST3 it moves to the instrument folder. This is rather bizarre.
 
So this is really not much of a problem, since it works properly, but shouldn't VST2 and 3 work the same way as far as plug-in menu behavior goes?
 
iZotope VocalSynth behaves the same way - works properly as a synth, but the menu display is wonky.

- Jim Hurley -
SONAR Platinum - x64  - Windows 10 Pro 
ASUS P8P67 PRO Rev 3.0;  Core i7-2600K@4.4GHz; 16 GB G.SKILL Ripjaws X;
GeForce GT 740; Saffire Pro14 MixControl 3.7; Axiom 61
64-Bit audio, SR: 48kHz, ASIO 256 samples latency, Rec/Play I/O Buffers 512k, Total Round Trip Latency 13 ms, Pow-r 3 dither 
#1

4 Replies Related Threads

    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: "Configure as Synth" for VST3 is different? Stutter Edit 2016/06/08 10:22:46 (permalink)
    I reported this some time ago. IIRC, the problem starts with the way VST3 inventory records are built. The flag is set in the wrong record (or not completely set depending on how you look at it). I believe this is one motivation for Cakewalk adding the MIDI I/O enable options to the VST drop down in the standard header. This happened at the same time as VST3 support in X3. Using the drop down achieves the goal of exposing the plug-in to MIDI data albetit a per-instance per-session setting.
     
    As an aside, it is my understanding the iZotope VST3 plug-ins are VST3 in name only. They implement the barest part of the spec to load as VST3 plug-ins.
    #2
    sharke
    Max Output Level: 0 dBFS
    • Total Posts : 13933
    • Joined: 2012/08/03 00:13:00
    • Location: NYC
    • Status: offline
    Re: "Configure as Synth" for VST3 is different? Stutter Edit 2016/06/08 11:07:41 (permalink)
    As an aside, is there any particular reason why you're configuring Stutter Edit as a synth? I use it as an effect and it works great like that....

    James
    Windows 10, Sonar SPlat (64-bit), Intel i7-4930K, 32GB RAM, RME Babyface, AKAI MPK Mini, Roland A-800 Pro, Focusrite VRM Box, Komplete 10 Ultimate, 2012 American Telecaster!
    #3
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: "Configure as Synth" for VST3 is different? Stutter Edit 2016/06/08 11:17:27 (permalink)
    Yes, it does work just fine using the drop down, however; given the plug-in would rarely be used without MIDI input, setting as a synth saves the config step for each session instance. The plug-in is not unique in that regard. It would be handy to have control over VST3 plug-ins like there is with VST2. Maybe the upcoming browser updates will address this and some of the other quirks in plug-in management.
     
    #4
    arachnaut
    Max Output Level: -67 dBFS
    • Total Posts : 1168
    • Joined: 2007/05/05 17:24:33
    • Location: Sunnyvale, CA USA
    • Status: offline
    Re: "Configure as Synth" for VST3 is different? Stutter Edit 2016/06/08 11:19:59 (permalink)
    sharke
    As an aside, is there any particular reason why you're configuring Stutter Edit as a synth? I use it as an effect and it works great like that....




    To get MIDI input. This was the older way to do it. Now that we have the MIDI menu on the VST header I guess this isn't necessary.

    - Jim Hurley -
    SONAR Platinum - x64  - Windows 10 Pro 
    ASUS P8P67 PRO Rev 3.0;  Core i7-2600K@4.4GHz; 16 GB G.SKILL Ripjaws X;
    GeForce GT 740; Saffire Pro14 MixControl 3.7; Axiom 61
    64-Bit audio, SR: 48kHz, ASIO 256 samples latency, Rec/Play I/O Buffers 512k, Total Round Trip Latency 13 ms, Pow-r 3 dither 
    #5
    Jump to:
    © 2025 APG vNext Commercial Version 5.1