Hey All,
 
Sorry this will probably be my last question and then I'll be able to leave you all alone for a while! Haha.
 
So I just upgraded from Sonar 8.5 to Sonar X3. Everything is going fine, but you know how each track used to have that box in it that you can put an effect in it? Well that's the way I've always known to load iZotope's Stutter Edit. Make an audio track, put the audio in the track, and Stutter Edit in that box. Then Create a MIDI track and for output choose that Stutter Edit... Only in X3 that box isn't there anymore.
 
I'm kind of at a loss for how to use Stutter Edit in this situation. I tried adding it directly to the wav clip (although really I'd rather it be for the whole track...What if I want to split the clip in the middle or something), but then when I make my MIDI track Stutter Edit isn't one of the available outputs... As if it's not even loaded.
 
I found an old thread about this from 2 years ago that had all these registry tweaks that supposedly can fix it, but I'd really much rather not have to edit the registry for this... You'd think that there would be a better way... Also Even if I did that, I still don't know how to load it properly without putting it in the Effects Bin (hey that's the name for that box, isn't it!).
 
Sorry if this should have been in the Instruments Forum... I thought in the X Series would be more appropriate because its a Sonar X3 usage issue...
 
Thanks for your help!

Add Stutter Edit to the FX bin in the audio track
Make sure "Enable MIDI Input" is checked in the Stutter Edit VST header drop down
Add a MIDI track selecting Stutter Edit in the output drop down

But there is nowhere to add an effect to a track as far as I can see in X3... There used to be the effects bin. You can still add an effect to a clip within the track, but not the full track...

Wait I'm half way there!!
 
I found the effects bin, but you can apparently only get to it from the Console View and not the Tracks view like you used to be able to...
 
Now the only problem I have is it only lets me use the 32 bit version of the plugin. I'm pretty sure it's got a 64 bit version, but it doesn't seem to allow it to be selected as an Output from a midi track... And yes I went into plugin properties and hit "Configure As Synth" for both of them...
 

At the top of the track view, just below the track menu, there is a track header filter drop down. Change the value to "all".

YES! Alright now we're almost there. If I can just figure out how to get the 64 bit instead of 32 bit plugin to show up I'll be home free. I'm gonna check the Plugin Manager and double check I didn't miss it somehow...

Depends on what you installed. There is a VST3 and a VST2 version. I believe the 32 and 64 bit versions have the same name.

Yea it's weird cause the one in the VST3 folder shows that it's in my regular Program Files iZotope folder, but the VST2 one shows its in the x86 Program Files iZotope folder... And I'm using the one that should be 64 bit... Just on a hunch I'm gonna try the opposite one since the one that should be 64 bit won't show up in my list of Soft Synths even though it's definitely added to my list...

Using the "Default All Plugin" layout, 32bit plug-ins show up in green in the browser and have (32-bit) appended to their name in the browser and menus. The plug-in no longer needs to be configured as a synth as effects can send and receive MIDI in X3 (if the effect supports the feature). It is also possible to drop Stutter Edit into the ProChannel, just like any other effect plug-in. In the ProChannel, the plug-in will be wrapped in an FX Chain.

Well the good news is at least in the meantime I can use Stutter Edit with X3 now where I couldn't before I posted the thread... However even though it's showing as a 64 bit (not green in the Default All Plugins Layout), when I go to the info panel within the Stutter Edit plugin, it shows me that its the 32 bit version... or at least I think that's what v1.04.552.WIN32.VST would mean... So weird...
 
Thanks for the help though! For now I'm happy to at least be able to use it... I don't use it enough to think using 32vs64bit is gonna really matter for the time being... And really it seems like it is the 64 bit anyway haha.