Trouble with VST3 Plugins from Arturia and u-he

Thanks we'll start a dialog with the developers and try and resolve these issues.
 

Hello Dan,
 
I use only the 64bit Version for all of my VST`s. Including Arturia. I can`t see them in the list when I will insert a new VST / VST3 instrument. Only the u-he VST3 plugins are there. But all of my vst3 plugins are installed in the same folder.
 
Best regards.
Frank

Update:
The Steinberg RND Portico issue has been resolved on our end. It was actually a bug in the VST3.5 SDK (confirmed by Steinberg) that could lead to this crash. I managed to work around the bug.
 
The Arturia issue is a crash in the plugin and details have been passed on to Arturia. The interesting thing here is that the new silent scan was swallowing the error so you wouldnt see it. I've addressed that part on our end. Now if a plugin fails you will get a notification and a dialog allowing you to skip or keep the plugin.
Tip: You can actually get the Arturia plugin to work but it requires editing the registry and clearing the isBad flag for the plugin. I recommend waiting for a fix if you don't want to mess with your registry.

Well, not much have happend here, still issues with VST 3 version of Arturias V Collection (SEM V, Wurlitz V, Analog Lab).... 

Uhe's Diva definitely is out of tune in vst3 mode... I am using vst2
 

That's all true, but it's still a workaround. I suspect the industry has a way to go before everyone's on the same page concerning the VST3 spec.

Any real adavantage ofvusing vst 3 ?

I know what vst 3 is suppose to but the 2 mainnthing that interest me ( zero processing when no audio and gui resize) seems to be never implemented .....vst 2 here and for a long time unless Craig convices me to take the risk to go vst 3 !!!

VST 3 will apparently offer support of individual expression per note. One can see this could have great potential but would not be easy to use.

I have not had issues with VST 3 effects but VST 3 synths have been very problematic.

robert_e_bone
...it may be a bunch of internal stuff that might make it easier/better for developers.

It's actually just the opposite: VST3 was a major PIA for developers, who almost unanimously resisted it for as long as they could.
 
There is one reason to use VST3, and that's specifically for synths or samplers that can use the note expression feature. If you don't know what that is, then you're probably not an orchestrator and you probably don't give a rat's ass about note expression. Your MIDI drum tracks don't need it, your piano libraries don't need it, and your kickass EDM pumping supersaws certainly don't need it.
 
For effect plugins, there is no benefit to VST3 over VST2.
 
So if you're experiencing problems with the VST3 version of a plugin, just uninstall it and use the VST2 version. You won't be missing out on anything.
 
 

mike_mccue
VST3 was introduced 6 years ago, back in 2008.
 
Here's a list of improvements over the circa 2001 VST2 implementation:
 

Note Expression is a biggy.  I'm currently thinking about switching over to Cubase because when you are trying to control expression + various articulations, etc, having to assign a specific midi channel and then only have 16 channels of MIDI CCs is not only limiting, it's a pain in the butt.
 
Really, I wish I didn't have to switch, but I think I am going to have to pull that trigger... which means more wasted HD space for all the crap that comes with the full version of Cubase :(
 
That, and I have an unresolved problem with my one 8Dio library where the danged thing loads out-of-tune after saving a project (is fine if I reload it, and then redo any tweaks, but who wants to do that every time you load a project).
 
But... it's VST Expression that is really lacking in Sonar.  So sad. 

stevec
VST Expression also has to be supported by the instrument itself, so I would check that the ones you want to use can actually take advantage of it.
 

I don't think this statement makes any sense in terms of what an expression map does as I understand it anyway.  It's true that not every library may be mapped the same way,  and every library may not be pre-mapped, but the way I understand it (only from being told by folks that use it) is that you can create your own expression maps, so you can map note information for key switch articulations, you can map CCs for instrument controllers, and you can even use midi-learn from your VST instrument and simulate a CC knob/slider movement to map a particular CC to the particular VST instrument control, and the expression map and lane expression data supersedes any other MIDI data going to the VST instrument.
 
Once you are mapped, then, you can freely draw CC information for any number of tracks without affecting other tracks, and you can use note expression to manage key switching.   Essentially, the DAW's expression map supersedes any incoming midi data for that track/lane, so now you are no longer limited to 16 midi channels for controlling your VSTs.
 
And if you think about it, you can already to that pretty much with note data in Sonar (minus the nifty note expression symbols, etc), but you can't do it with CC data (at least I haven't found a way to do it--please, please correct me if I am wrong because I don't want to migrate to a new DAW).
 
My experience is that Sonar forces me to choose a channel for a CC, and once I do this, that channel/CC is marked in use for the whole project, and that CC will affect every instrument on that midi channel that responds to that CC. If CC data were to remain local to the track or to supersede incoming MIDI CCs if written to a track lane, and if every track lane could re-use MIDI channel CCs, there'd be no reason to move, and that's leaving out the nifty expression map note data and the fact that helps when you are printing out score notation.
 
At any rate, I am primarily looking at this as a way to simplify workflow for Kontakt-based instruments, and that's what the folks using Cubase tell me about VST expression.  The devil may be in the details, but there seem to be a lot of people sold on this, and they are using it for a reason, and that reason isn't--I don't think--that they are just Cubase fanboys.

My experience is that Sonar forces me to choose a channel for a CC, and once I do this, that channel/CC is marked in use for the whole project, and that CC will affect every instrument on that midi channel that responds to that CC.

Are you sure about this? I routinely use the same CC for different things on different tracks. Basic functionality such as CC7 for volume wouldn't work if it was true. For that matter, multi-track MIDI wouldn't be possible if one track's MIDI commands were sent to every track assigned to the same MIDI channel.
 
Not saying you're wrong about this. I may have just misunderstood your explanation.
 

I didn't have any problems when I initially installed Analog Lab - they must have gotten into the right folders, but Arturia were definitely visible.
My problems came up when I installed Melodyne Studio...there was nothing I could do to get X3 to recognize Analogue Lab.
Long story short - I did a System Restore to an older date, and it came back the right way. 
 

Appending to an old thread is not the best idea.
 
Arturia Analog Lab 2 should work after installing and authorizing from Arturia then scanning the plug-in in SONAR. No special action is necessary.
 
The delay in hearing a note being played is either a misconfigured audio interface and/or plug-ins in the project. Information about the audio interface used might be helpful. To bypass all effects in the project use the shortcut "E" or the FX button in the mix module.