Helpful ReplyPicking up some VST plug-in errors - X3

Author
Post
Essentials Only Full Version
QuadCore
Max Output Level: -86 dBFS
  • Total Posts : 219
  • Joined: 2009/05/04 15:50:49
  • Status: offline
2013/11/08 16:14:40 (permalink)

Picking up some VST plug-in errors - X3

I'm picking up some VST location error messages in X3 - i had a few with X1/2, but X1/2 the amp plug-ins then loaded up just fine - now with X3 all i get is the 'plugin-missing' in the effects bins. 
I wonder what went wrong...
Is there a recommended procedure when this happens?
 
I could delete the missing plugin, insert it again from the effects menu, and reprogram it, but I was very happy with the programming i had done.
I put a lot of time into the programming of the amp sim plugs - is there a way to save the programming i did to the (missing) plug-ins?  Now, when i reload the plug-in it comes up in default mode. [all plugs present and accounted for - not been moved]
Or is there a deeper problem i need to sort out?
 
I have GuitarRig4 and Amplitube3 coming up in these errors.
 

Thanks for your help.
 
Win7 Pro - 64bit
post edited by QuadCore - 2013/11/08 16:25:39
#1
List Solutions Only

7 Replies Related Threads
    QuadCore
    Max Output Level: -86 dBFS
    • Total Posts : 219
    • Joined: 2009/05/04 15:50:49
    • Status: offline
    Re: Picking up some VST plug-in errors - X3 2013/11/08 19:15:19 (permalink)
    Just a thought - X3 has a new plug-in selection method.  Did X3 move my plugs around by any chance?
    #2
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Picking up some VST plug-in errors - X3 2013/11/08 19:33:47 (permalink) ☄ Helpfulby QuadCore 2013/11/10 15:50:15
    If the projects open correctly in a previous version of SONAR, you could save the plug-in programming in the projects as presets then when the project is re-opened in X3 the programming will not be lost.
    #3
    QuadCore
    Max Output Level: -86 dBFS
    • Total Posts : 219
    • Joined: 2009/05/04 15:50:49
    • Status: offline
    Re: Picking up some VST plug-in errors - X3 2013/11/10 15:51:04 (permalink)
    Thanks, scook. 
     
    #4
    lawp
    Max Output Level: -67 dBFS
    • Total Posts : 1154
    • Joined: 2012/06/28 13:27:41
    • Status: offline
    Re: Picking up some VST plug-in errors - X3 2013/11/10 16:09:43 (permalink)
    could it be the 8.3 ~ causing trouble?
    #5
    Grem
    Max Output Level: -19.5 dBFS
    • Total Posts : 5562
    • Joined: 2005/06/28 09:26:32
    • Location: Baton Rouge Area
    • Status: offline
    Re: Picking up some VST plug-in errors - X3 2013/11/10 16:28:48 (permalink)
    No the installation of any CW program doesn't change you VST folders.

    I would rescan you plug ins.

    Same thing happens to me when I open an older project, X3 sees an older 32bit plug and offers to replace it with a 64bit plug. But the id# is different. Yours seem to be the same, which maybe a clue to why it is doing it.

    Grem

    Michael
     
    Music PC
    i7 2600K; 64gb Ram; 3 256gb SSD, System, Samples, Audio; 1TB & 2TB Project Storage; 2TB system BkUp; RME FireFace 400; Win 10 Pro 64; CWbBL 64, 
    Home PC
    AMD FX 6300; 8gb Ram; 256 SSD sys; 2TB audio/samples; Realtek WASAPI; Win 10 Home 64; CWbBL 64 
    Surface Pro 3
    Win 10  i7 8gb RAM; CWbBL 64
    #6
    TheSteven
    Max Output Level: -55 dBFS
    • Total Posts : 2037
    • Joined: 2005/03/05 01:17:06
    • Location: Southern California
    • Status: offline
    Re: Picking up some VST plug-in errors - X3 2013/11/11 02:28:59 (permalink)
    I was getting the same message for several of my plug-ins.  If i remember correctly the message does necessarily mean the plug-in is missing, just that there are possible alternatives (such as 64 bit versions vs 32 bit) and Sonar needs to know which to use. Unfortunately Sonar is using the same dialog box as the 'plug-in is missing' dialog box and didn't change the caption to something like 'I don't know which one to use'.
     
    If you want to get rid of the message - identify the ones you don't want and rename their extensions so they drop out of the database at the next scan.  
    You can always rename them back if it turns out that you need the them in an old project in an older version of Sonar.
    post edited by TheSteven - 2013/11/11 02:37:00

    "Time is a great teacher, but unfortunately it kills all its pupils" Loius-Hector Berlioz

    www.AgitatedState.com MenuMagic - plug-in management powertools!
    My Tunes
    #7
    Lance Riley [Cakewalk]
    Max Output Level: -84 dBFS
    • Total Posts : 337
    • Joined: 2011/05/17 17:18:01
    • Status: offline
    Re: Picking up some VST plug-in errors - X3 2013/11/11 12:52:09 (permalink)
    This dialog is intended to pop up. In some cases SONAR can know what plug-in you intend to load when multiple versions are scanned. For instance if you have both the 32bit and 64bit plug-ins we automatically load the version based on the SONAR version opened 32bit or 64bit. In some cases we don't know which one needs to be loaded. If you have both VST2 and VST3 plug-in types and both 64bit and 32bit versions of each there are some times when we need to ask. Usually though this should only happen once and after the project is saved we'll continue to load the project the same way unless any of those used plug-ins are uninstalled and then you may see this message again.

    Lance Riley
    Product Manager
    #8
    Jump to:
    © 2025 APG vNext Commercial Version 5.1