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.   

Wow- here is more: missing plug ins:
Maschine (Synth Rack)
Play (Synth Rack)
Play (Synth Rack)
Play (Synth Rack)
Kontakt 5 (Synth Rack)
V-Station (Synth Rack)

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.

Vlada - you kill me :)
 
Was there a message during install of where it wanted to place the plugins?  Most install processes either tell you where it installs things or give you a default location with opportunity to change it.
 
I always let scans run when they choose to.
 
I wish V-Station ran as a stand-alone synth, to see how it behaves outside of Sonar, but it seems to not run that way - just as a soft-synth dll.
 
Also, I do not at all understand what is happening with your transport controls, so if you could explain that a bit more it might help me understand how that came to be.
 
If you start a new project, then insert V-Station, and you have no other plugins loaded yet, can you check in Task Manager to see if BitBridge is running?  If so, then that would mean you are loading the 32-bit version of V-Station, which may or may not work well in x64 with BitBridge.  (You can always move the V-Station 32-bit plugin to some folder that is NOT present in the search paths for your x64 Sonar, to make sure only the 64-bit version of V-Station is available for loading into x64 Sonar).
 
Bob Bone
 

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
 
 

works here.. well v-station installed.. I don't use norton though.. can u specify the DLL or folder in an exempt list?
 
was gonna say the update from 3-4 months back , but you already did that... are you using other stuff like automap etc ? as a shell
 

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...

Sure - I certainly am not recommending you load it into an existing project.
 
I was meaning that I would like to see if BitBridge (or JBridge) loads into the computer's memory when you are loading V-Station, IN A NEW BLANK PROJECT - so that nothing will get corrupted if the test project goes belly up.
 
I am just wondering if in an empty new project, if you load that in, are you running the 32-bit one or the 64-bit one, and if your loading the 32-bit one than you will see one of those two bridging programs loading (BitBridge or JBridge).
 
Can you perform that test with a new project with nothing else in it and post back?
 
Thanks, 
 
Bob Bone
 

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.

Yup - I do try to pay attention to your posts (early on with you I had missed some things, but think I have been better at that) :)
 
I knew you said it wasn't BitBridge, but since you hadn't indicated what it was, I just listed that as a generic bridging component, not knowing what else to list it as.
 
I suppose another way to approach it is to make sure that the PATH to where the 32-bit install of V-Station is located is NOT in the search path for x64 Sonar.  That would ensure that you are running the 64-bit V-Station.
 
I am wondering also if it could be that some 32-bit plugin, NOT part of V-Station, is somehow interfering with the presence of V-Station in your projects.  I wish you could do some dedicated testing of V-Station in a project that used ONLY 64-bit plugins, to try to see if it stabilizes in that manner, because it sounds like other folks are using it successfully, so it would seem that something particular to your project environment is not playing nice with it.
 
Bob Bone