Novation V-Station VST crashing and disapearing

The night I installed the Novation V-Station and Bass Station plug ins (soft synths), I saw them working in Sonar as plug ins, and then it disappeared. Could not find it anywhere on the computer. I suspected- Norton Antivirus deleted it as a threat. I re-installed. It worked. Then out of blue it opened with blank window. I called Norton. They could not help much- we re-installed it and set "do not scan" for my plug ins folder. Last night it disappeared again! I do not understand what happens to it all the time. I can find the installer files, but do not see actual exe files like many other plug ins have. In the VST folder they listed with .dll extension. When it opens blank plug in window, I can not close that window or delete the instance- it crashes the Sonar and I have to restart computer. If I leave it alone, Sonar has problems with Playback. V-Station comes with VST and VST3 versions 32 and 64 bit- I think I installed all options first. Then I have tried to install only 64 bit versions. I had V-Station and Bass station listed couple of times on a soft synth list, and I excluded the 32 bit versions. It works when I open and insert, but then I come back and it wont open. I spoke with Novation tech support. They have no idea and blame it on Sonar. Any suggestions? Thank you.   

Ok, the "other" plug ins are working now- they did not load because I canceled "Scan" at the beginning when Sonar opens. This actually should not affect the plug ins as pressing "Cancel" should cancel scan but not disable plug ins. However, the V-station is not loading.
 
I heard something about "safe mode"- how do I do it? I can not delete the V-Station plug in because it crashes Sonar, also the Transport is not working- it grayed out, pressing "Play" starts playback, but then it would not stop as transport becomes inactive, and eventually Sonar fails. How do I get rid of V-Station plug in? I do not want to give up on the song and start it over. Thank you.

Oh - forgot - hold the Shift key down when you click to open a project in Sonar, to have it open in Safe Mode.  It will ask you whether or not to load each plugin.
 
Bob Bone
 
 

Hey, guys
 
This morning I spent about an hour with the Sweetwater tech support guy with distance connect and him trying to make this thing work. Nothing happened. We fixed the current failing project by opening it in Safe mode and not loading V-Station, then deleting it with great difficulties and continuous Sonar crashing. We also re-installed it several times. It opens in separate project, but that particular project would not work with it. I did not have enough time to test it in another project, but we had a feeling- the problem would persist.
Bob, BitBridge actually shows under some different name- forgot what it is, but no- not when V-Station is "running". We believe it is 64 bit. I can not insert it back in to this project and testing it in other projects with no plug ins would not help. I can not use it. This was/is few weeks old project with few tracks recorded. If I inserted it in to full production 64 tracks project and it corrupted it, I would be upset. I don't think I would be comfortable to ever insert it again in to anything. This problem re-appears over and over and it less than month old. It can happen again in any project if I use it again. So I am not sure if Sweetwater would let me return the Launchkey (small midi controller). They say they don't usually have returns on Software...

Bob, thank you for your reply. If you read my last post attentively, you would note that it states- it is not JBridge- it has another name- I thought I wrote it down but I did not. And- no- it does not run. I will attempt to test it. The problem is- it works for a while after re-install, but then it fails, but I would never know when it would happen.

First it disappeared when I just installed it. Now, with many reinstalls, we only installed 64 bit. I had Maschine, 3 instances of Play (East West) and Komplete5 in use- I am not sure which Komplete I am inserting as it shows 3 times in Plugins list. Massive was also used but frozen. Is Massive 32 bit? I do have many 32 bit plug ins and they work fine- well- IK Multimedia suddenly stopped working (all of them) and I had to set Sonar to run as administrator to get them back to work. But no IK multimedia in this project (also- I had one used earlier and then deleted).
_____________________________________________
Off topic- here is some nice web site oriented reading to encourage you thinking about the web sites... http://www.hostbaby.com/assets/ebook/hostbaby-website-optimization.pdf  If it not opens- you may try from here: http://www.hostbaby.com/website-optimization-guide/

Not all plug ins have 32 bit next to them while they are 32 bit. Also- not all 32 but stored in x86 folder and not all 36 bit stored in VST Plug in folder- I noted- they would get installed in to x86 folder while they are 64 bit. So I do not know how to tell if it is 32 or 64. I have Komplete listed 3 times with no marks to it. I should of be careful and make sure I install 32 bit all in x86 folder but I let them install where they wanted, so now I don't know what is what.
 
I am not exactly understanding Formats for renaming, what you mean by it? Thank you.

Can you please list the search paths you have included in your x64 Sonar install?
 
Bob Bone
 

Well, I am wondering if you are picking up 32-bit versions of plugins without knowing it.  In addition, you have indicated your scan time is long, and I am wondering if you have a bunch of 32-bit plugins that you don't use in x64 X2 getting scanned when you could move things a bit to streamline what gets scanned.
 
If it is of any use to you, I do NOT bring in all of my 32-bit plugins into x64 Sonar.  I put the ones I KNOW work into a SUB-folder within my normal folder of 32-bit plugins, and then THAT is the only 32-bit folder path I include in the x64 Sonar search path.  Then, ONLY those 32-bit plugins I want to show up in x64 Sonar show up, and yet ALL 32-bit plugins still show up in x32 Sonar because by specifying the whole path to the parent folder for 32-bit plugins, Sonar still searches the sub-folders and gets those plugins too.
 
I have no idea what the state of things on your computer is, so I am trying to see what you have specified.  That is why I was asking.  These issues are only happening to YOUR computer, so one or multiple things are amiss with YOUR environment.  I do not know if your supplying that information will or will not help, but I DO know that things are jazzed up and if you want assistance in getting to the bottom of it you might want to be more forthcoming on answering requests for information.  Otherwise, you will end up figuring this out on your own.
 
I am trying to help you - if that is not what you want I'll back out.
 
Bob Bone
 

OK I will try to explain why I was asking - perhaps it will make sense, sorry for any confusion.
 
Yes, I know Sonar will scan whatever you tell it to, as far as paths in the search list.  I was trying to figure out if you were scanning a bunch of extra stuff, PRECISELY because Sonar will scan whatever you provide it.  I was thinking that you may have had all kinds of 32-bit plugins being scanned, even though you might not be using them in x64 Sonar, and I was also wondering if you had some PARENT folder that was telling it to scan like maybe your whole C:\Program Files folder or anything like that.
 
I also had earlier tried to explain why a lot of plugins, like Kontakt, get listed multiple times.  I will try again - sorry for any confusion there too.  Lots of plugins have multiple ways of being loaded, and because of this, a single plugin (like Kontakt) will have multiple listings, even though it is the same program.  It shows up multiple times because it allows you to load in one of 3 ways: a version with 8 available audio outputs, a version with 16 available audio outputs, and a version with 64 available audio outputs.   This is why I had suggested you edit the names in Plugin Manager, so that you could tell the different versions apart when you are trying to insert a plugin.  If you need that post again, please let me know and I will post back with the exact post I included those steps in.
 
I rarely use 32-bit Sonar, BUT because I created a sub-folder within my 32-bit plugins main folder to contain the ones I want to use in both x32 and x64 Sonar, it all works well and all of the intended 32-bit plugins show up as intended for each version of Sonar.
 
My main 32-bit plugins folder is:
 
C:\Program Files (x86)\VSTPlugins
 
The SUB-folder I created within that for 32-bit plugins I want to use in x64 Sonar is: 
 
C:\Program Files (x86)\VSTPlugins\Approved for x64
 
Since Sonar scans all sub-folders within the folder you put in the search path, ALL 32-bit plugins are detected by x32 Sonar by just including the C:\Program Files (x86)\VSTPlugins path, as it will know to also look in the 'Approved for x64' sub-folder.
 
I ONLY add the C:\Program Files (x86)\VSTPlugins\Approved for x64 path to x64 Sonar's search path to pick up ONLY the 32-bit plugins I have made sure work in 64-bit Sonar, and no other 32-bit plugins are then detected by the x64 Sonar's VST scan.
 
Bob Bone
 
 
 

Sorry - I missed your link - can you either post it again or send me an email?
 
I gave you the steps to change the VST display names - go ahead and follow them.  They work.
 
Also, whatever path or paths you add to the plugin manager's search list does NOT actually move anything at all.  Those paths simply tell Sonar where to search for plugins.  
 
Bob Bone