• SONAR
  • Even though they are installed and working, plugins in X1 projects come up as missing when those projects are opened in X3, Help?
2014/01/06 09:04:45
samson7842
So, I've upgraded to X3 Pro from X1 Pro Expanded and in doing so I've gone from XP Pro SP3, 32 bit to Windows 8 64bit. I've also upgraded some of my plugins to their newest versions. The problem is when I pull up my old X1 project in X3 any Waves plugins or instances of Melodyne Assistant I used are flagged as missing. However, they are not missing. They are installed, X3 sees them and they are fully functional. X3 just doesn't seem to "connect" the old plugin instance with it's newer counterparts.

I've done quite a bit of automation using a few plugins and I'd hate to have to redo all of it. To my thinking, X3 should just "point" the track's FX bin to the correct plugins. Or, is there a way I can do that manually? I've scanned and rescanned all of my plugins. X3 sees them and they all work fine. There are no issues except this. When I load my X1 32bit Windows XP project into my X3 64bit Windows 8 setup, all of the instances of my Waves plugins and Melodyne Assistant are flagged as "missing plugins." None of my other plugins are giving me that problem. Sonitus, Massive, Maschine 2 (upgrade from Maschine 1.8), EZMix 2 (upgrade from EZmix 1) all come up as they should when I open my X1 projects in X3. It's just the Waves and the Melodyne Assistant plugins doing this.

Any help you guys could give would be greatly appreciated.
2014/01/06 09:34:46
Starise
I had a similar problem that resulted from not having my folders in the same places. X3 has a default installation folder for  Plug-ins and if it was ever modified or another folder was added then X3 needs to be told through preferences to rescan the folders you added.
 
I'm not sure if you did a clean install or an upgrade install but there is a possibility, especially since you made such a huge leap in software generations, that folders in win8 are in slightly different configurations. Maybe someone more familar with that can comment. Also I believe  X3 allows you to exclude 32 bit versions of plug-ins if they have 64 bit counterparts. If you used 32 bit plug-ins then there could be a discrepancy in trying to open those files in 64 bit. I'm guessing you carried over some 32 bit plugs to use in X3 with bitbridge.
 
When you load up an old project it only knows where things were the last time it was launched.If anything has changed it isn't smart enough to find it without help.
 
 
2014/01/06 17:04:04
samson7842
Hey, thanks for replying.

I did a clean instal on a new PC. The old one crapped out. Motherboard died on me. So, I did a clean instal from scratch. I've scanned every folder known to man. Still does the same thing. I'm at a loss for ideas.

Wish there was a way to manually "point" or connect the missing plugin spot to the right VST.
2014/01/07 03:47:17
Bristol_Jonesey
When you load up an old project it only knows where things were the last time it was launched.If anything has changed it isn't smart enough to find it without help.

 
No it isn't.
 
But it SHOULD be smart enough to say, "hey, plugin XXX was at location YYY last time you saved this project and it's not there anymore"
 
And then give you the option to repoint the currently held location to wherever it is on your system
2014/01/07 05:33:30
samson7842
Oops.
2014/01/07 05:35:08
samson7842
Bristol_Jonesey
When you load up an old project it only knows where things were the last time it was launched.If anything has changed it isn't smart enough to find it without help.

 
No it isn't.
 
But it SHOULD be smart enough to say, "hey, plugin XXX was at location YYY last time you saved this project and it's not there anymore"
 
And then give you the option to repoint the currently held location to wherever it is on your system



Exactly! It seems so simple. There has to be a way to do that.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account