VSTs defaulting to patch 1

Author
TimDale
Max Output Level: -90 dBFS
  • Total Posts : 17
  • Joined: 2015/01/21 14:31:39
  • Status: offline
2015/03/11 06:25:02 (permalink)

VSTs defaulting to patch 1

I know several people have had problems with this so I'm hoping someone has a solution .....
Using Sonar X3 (version X3e) ....   I have loads of VST instruments (both bought and free) and three are showing this problem, specifically OP-X (pro2), iloSynth and Shuniji ......
When I load an existing project using one of these synths, the patch always defaults to the first patch of the (correct) bank.  The bar at the top of each window which has the "on" button, the patch name and the "file" menu, shows the correct patch but the main window of each synth doesn't.  Does anyone know of a solution for this?  It's annoying having to re-select the correct patches every time I load a project.
The problem only started with OP-X when I upgraded X3 to version X3e (from X3b), the other two I have installed since, but show the same problem.  Over a dozen other VST2 plugins don't show the problem and work fine.
 
I have just noticed that these 3 synths display a separate icon in the taskbar (i.e. separate to X3), an icon that looks like a blue plug (?). I don't think any of the other VST plugins display this icon, but wouldn't swear to that. Is this a clue? When I right-click on the icon the first menu option is "Teleport Server". Clicking on it doesn't seem to do anything.
 
#1

2 Replies Related Threads

    TimDale
    Max Output Level: -90 dBFS
    • Total Posts : 17
    • Joined: 2015/01/21 14:31:39
    • Status: offline
    Re: VSTs defaulting to patch 1 2015/03/11 07:44:43 (permalink)
    Hmm, I'm running the 64 bit version of X3, on 64 bit Windows 7.  I did a search on Teleport server and found references to bitbridge.  Is this a 32/64 bit issue?  All my VST2 plugins are in D:\Program Files\Cakewalk\Vstplugins.
    #2
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: VSTs defaulting to patch 1 2015/03/11 14:09:14 (permalink)
    It sounds like an issue with these plug-ins and BitBridge. Here are a two ways to determine if a plug-in is 32bit. The browser and plug-in lists append (32-bit) to the plug-in name. The plug-ins do not have the standard VST header.
     
    Generally 32bit plug-ins behave well in a 64bit host but there are exceptions. You could try jBridge or install the 32bit version of X3 and use it when projects call for these plug-ins. The 32bit and 64bit versions of SONAR can be installed on the same machine.
    #3
    Jump to:
    © 2025 APG vNext Commercial Version 5.1