Hi,
Iv'e just installed an upgrade to my Arturia Spark, as Spark has worked no problem before, I thought I would
run a VST scan, but it wont go past the Spark dll file, and if I try to use spark in Sonar, I get the white screen, any ideas ?
 
Thanks
John

I can't be much help here. Aside from the obvious (mistakenly installed a 32-bit version instead of 64-bit and BitBridge is complaining) or a problematic installation, there's not a lot you can do if Sonar doesn't recognize a plug-in.
 
One thing that has worked for me a couple times is to move the offending DLL out of the VSTplugins folder so that the scan can complete. Then I put the plug-in back in, and everything works for some reason. Why? I have no idea.

I am thinking maybe after applying the upgrade that you might have to re-authorize Spark outside of Sonar, and then I think it might start working.
 
The above is speculation, but I do recall scan issues in the past, and I think that once control is passed to the dll, that Sonar may have to wait for it to respond, so if there is some sort of internal issue that the dll doesn't know what to respond with, (like not being authorized), it might then appear to hang.
 
That might actually be a dll-caused issue.
 
So, I suggest you check out the authorization of Spark, and see if that clears it up.
 
Bob Bone
 

Again speculation ... but (along similar lines as Bob, and some general issues observed in some Steam distros (not me)) ...
 
Try running Sonar as administrator (right click > Run as Administrator) ... at least for initial launch. It may e.g, be trying to access/update the Windows Registry or having an issue with User Access Control due to it's location (e.g, under Program Files).

Hi John,

I use Spark. I'm assuming you upgraded from 1.7 to 2.0. I was able to run both 1.7 and 2.0 in X3e, so am unable to duplicate your issue. I sympathize with your problems though, because I have also experienced VST issues that seem to be occurring only on X3e. I'm starting to think there might have been some change (either purposeful or inadvertent )in the scan process with X3e. Plugins that I had been using in Sonar for years (even under X3a-X3d) would hang the scan process under X3e. Moving the .DLLs would allow the scan to continue but these particular plugins (Waves) wouldn't complete the scan until updated to the most current version. I had an issue a few weeks back with a Kush Audio plugin that was working fine under X3d but not under X3e. This required a change to the plugin from the developer in order for the plugin to work correctly under X3e. Maybe you should contact Arturia and report the problem. Perhaps another user is experiencing the same issue under X3e.