• SONAR
  • [Solved] X1d Producer projects won't play in new X3e upgrade
2014/10/25 16:22:50
emeraldsoul
Hi, apologies to all if this has already been covered. I searched but found nothing.
 
For years I created X1d Producer projects, 40-50 tracks, with my RME Fireface 400 card. Mixing latencies set at 1024.
 
I just recently upgraded to X3e - and whenever I open up an old X1 project, it loads, but won't play. No spacebar, no clicking "play" on the transport, nuttin'.
 
So, I go back to X1, open them, and they play just fine.
 
I noticed - that when you open them in X3, all the plug-ins load but there are no open plug-in windows, except for in my case AD2. There are many plugins on the project (Equilibrium, Glue, Microshift, S-Gear 2, and a few more) and they show as loaded and "on" in the Inspector. But in X1, they always opened up their little plug-in windows in an annoying stack which I had to click through to minimize them all. Which was, annoying.
 
When I open up the project in X3e, all the plug-ins show as loaded and on in the inspector, but there are no plug-in windows open.
 
So, as a test, in X3, I clicked on all the plug-ins in the inspector, and they opened up their little plug-in windows just fine. But the project still won't play at all - no spacebar, no transport.
 
I should say, if I start a NEW project in X3e, everything works just great. No problems with starts! It just won't "play" an older X1project.
 
thanks for any help, I feel this must have come up before. I want to love x3!
 
cheers,
-Tom
 
2014/10/25 16:28:40
YouDontHasToCallMeJohnson
I have just spent two weeks converting a project from 8.5.3
 
Two issues:
All tracks had to be cloned to work correctly with colors and with icons.
Most buses had to be cloned to provide output.
Spent way too much time figgering this, and then doing it.
And last night I had to clone some midi tracks again to get to work with dropzone.
 
I am way sad about opening other projects.
 
2014/10/25 16:59:29
emeraldsoul
Thanks for the ideas - for my X1 to X3 experience, the buses exist and are created from X1 to X3.
I'm still wondering about the lack of opened plug-in windows upon opening a project in X3 that was started in X1.
 
I can start a project brand new in X3, pop in a few dozen plug-ins, close the project, re-open it, and it gives me stacks of open plug-in windows.
 
When I open any X1 project in X3, there are no open plug-in windows at all. Except for AD2 and BFD Eco DV, a jbridged cymbal vsti. Those windows open up "opened"
 
Do I have to close and remove my existing plugins from my X1 mix, and reopen them and remix them in X3? Is there a problem with "plug-in states" when you do this upgrade?
 
Hope not!!!
 
thanks, great forum!
-Tom
2014/10/25 17:05:42
emeraldsoul
And yes, I had read this:
http://www.cakewalk.com/Support/Knowledge-Base/2007013315/SONAR-X3-Full-VST-Rescan-Recommended-for-Upgraders
 
but, reading it again, it seems that a VST Reset will remove any plug-in settings that I had in my X1 mixes, and I'll get the fun bonus of having to remix all the plugins from scratch, just so I can get them going in X3.
 
Is this correct?
 
thanks,
-Tom
2014/10/25 17:12:33
scook
The VST reset does not affect settings in projects. The reset clears out the VST Inventory in the registry. The VST Inventory in the registry is the list of available plug-ins. The list contains information about the plug-ins such as if the plug-in is a synth, can generate MIDI, number of inputs and outputs.
2014/10/25 17:50:22
YouDontHasToCallMeJohnson
No problems with new projects.
 
Old projects may require duplicating tracks and buses.
 
When testing old projects in X2 and X3 trial I did need to replace DP and SD to get midi in and sound out.
But resetting the VST scan did not fix it.
2014/10/25 20:49:37
John
This is strange, I have projects going back to Pro Audio each and every one can be opened in X3 and will play back fine. I have many projects from X1 and X2 as well with the same results. The need to clone tracks has never come up before on this forum.  
 
People have noted on rare occasions issues with a particular project that could have been corrupted but not as a regular situation. Something else is causing this problem.  
2014/10/26 13:04:03
emeraldsoul
thanks, John. My problem is X1 to X3 upgrade, and I have no issue with recreating buses or tracks. Every bit of the X1 (Producer Expanded) project is present when I open it in X3e.
 
It just won't play, or record, either from clicking the transport buttons, or the spacebar.
 
I did the recommended "rescan" and "reset" of my plugins.
 
My next test will be this: I will go to the original X1 project, make a copy, remove all the plugins, save it, bring it into X3, and see what happens.
 
Unless there is something blindingly obvious that I'm missing? I know a lot of people have upgraded to X3 recently. Any similar issues? Any info would be of tremendous help, thank you!
 
cheers,
-Tom
2014/10/26 13:15:13
emeraldsoul
OK, I did the "remove plugs in X1 experiment / save / open it up in X3"  and . . . it . . . plays . . .back.!
 
That's the good news. Now I must hunt out if it's one particular plug-in that's the culprit. Or, as it is a large-ish project (50 tracks) perhaps the amount of plugins X1 was handling exceeds my cpu capacity when run in X3?
 
Why spend time making music, when you can be Sherlock Holmes?  :)
 
thanks for any ideas . . .
-Tom
2014/10/26 14:10:05
emeraldsoul
Star date 10.26.14. I am alone on the bridge. I document these results only for the future benefit of humanity.
 
Well, I open up an X1 project in my new X3. My mix in x1 had 50+ tracks, 10+ instances of Equilibrium, a few Glues, some Soundtoys Microshifts, a couple of PSP VintageWarmers, some Breezes, S-Gear2, and a few Toneboosters Barricade plus a VBC.
 
It ran fine in X1. It won't play in X3 and I notice the "Audio Engine" symbol is greyed out. There is nothing happening in the "core meter" window - totally blank.
 
So I systematically begin peeling off the plugins. After removing most of them, and noticing it doesn't matter particularly which ones, I get to a "tipping point" where the project will run. Needless to say, with the plugins 80% removed, my original X1 mix is a goner.
 
So, the conclusion is - X3 will run fewer plugins than X1, because X3 must place more demands on the CPU than X1 did. Right?
 
Wrong . . . I can create a new project in X3, load it to the gills with the same plugins, and it works fine.
 
The sample rates I have been experimenting with are both 44.1 and 88.2, and the same issue exists.
 
Boiling it down, the question is, why do I have to remove 80% of the plugins used in an X1 mix, just so the audio engine will come back to life and run it in X3?
 
Have I entered a VST2 / VST3  upgrade wormhole?
 
I have no clue at this point. Maybe a fellow upgrader has some ideas . . .
 
thanks,
-Tom
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account