Zeta+ 2 v2.2 major problem for me. PLEASE HELP ME!

So, excited about the new Zeta 2 version, I eagerly downloaded it, anticipating some of the new features.  I played with the stand alone and it works wonderfully.  I started a new session and noticed that instead of being a VST2, it's now a VST3.  Not entirely sure what the difference is, but, therein lies the problem.  I loaded an OLD session, and I get several Error: Program Load Data Failed.  
 
I checked the Cakewalk Content folder (which is NOT on my C drive) and everything was there.  I then looked in my 64bit VST folders, and saw Zeta 2 in there, and it's got the extension of VST3.  I'm thinking my old sessions are looking for the old VST2 file.  

To test, I uninstalled it, struggled in finding the old Cakewalk Store downloads, put my 2.1 back on, and everything worked again.  Can anyone help me figure out why 2.2 won't work with my previous sessions?  
 
Gregg

Pan, for you, this shouldn't be too hard.  Uninstall 2.2.  Go back to 2.1.  Go to Plug In Manager, export your patches.  Then install 2.2.  Import them back in.  My friend Bob Bergen told me about this step.  However, my loss is that I used stock presets.  I may have to go through all my tracks save each preset as a custom, and then do this process.  I'm hoping the bakers can fix this on their end so I don't have to do this.  It will literally take me weeks. 

Does everybody have this issue, or just some of us?

 
From what I'm reading it seems like an issue between the synth updates and Kingston. I didn't update my Z3ta+2 and have not seen this.

I have the issue as well. Loading any pre-2.2 song results in "Error: Program data load failed" and Z3ta loading the default program. Reported to Cakewalk. I hesitate to do the work around of uninstalling 2.2 and reinstalling 2.1 hoping there will be a fix sometime soon.

The other question is how do you roll back from.
 
Installing old Z3TA+2 manually (not via CCC) and then updating via CCC.
 
Don't see a rollback option in CCC.
So we have to uninstall and reinstall?

Yes.  You have to uninstall it via Control Panel and then install from the original purchase you made.  That's where I am at right now.  I'm done beta testing it until they can fix it.  I'm a bit flustered with this.

Stop complaining and make music. '-)
 
 this is the long way around

Paul P
 
Someone has to ask ...
 
Did anyone actually try this update before releasing it ?
 
(this is unfortunately not the first time this thought has crossed my mind)
 
 

 
I'm pretty sure no one tried Rapture Pro before it was released (The original . . . and the worst), or it's subsequent updates that followed, so . . . 
 
What's it now about 8 months since release, nearly time for Rapture Pro 2, so maybe that will be it for Rapture Pro, and better luck next time perhaps ?
 
Z3TA 2 might be out of luck though, not sure it will get a '3'
 
I like Z3TA 2 (and Dim Pro, and Rapture) but I dare not install this update for Z3TA 2, it is and has been running fine for a long time, and if the past is any indication, and the feedback that has been surrounding this 'update' is anything to go by, that's not going to change.

  Oh dear, we heard about an update to z3ta+2, wow after all this time, so i came to check it out. It seems to be rather uninviting from what I have read here so far in the various threads, and might I say a little confusing. Now it seems Cakewalk Command Center is involved, and I'm not touching that with a 40ft pole, it has quite the reputation on other forums I frequent, and it isn't a good one.
 
  I think we will pass on this update, z3ta+2 works good enough for our purposes as it is, and I really don't want things to get messed up as it seems will likely be the result from what I have read. Oh well.

Doktor Avalanche
Yes the fixes took too long to get out (years) and after this patch we are still seeing issues, ...

Issues ?  It doesn't even work
 
Your patience is remarkable, out of character even.
 

Doktor Avalanche
Yes the fixes took too long to get out (years) and after this patch we are still seeing issues, ...

Paul P
Issues ?  It doesn't even work
 
Your patience is remarkable, out of character even.
 

Well ultimately patching Z3TA+2 was the right thing to do, they could have just let it slide.Whilst this is a PITA I don't want to seem ungrateful. The reputation I get is normally from people who polarise my views rather than what I actually write so I'm not surprised it seems out of character... Thx.

Hi All,
 
I assume most of us were doing Thanksgiving related stuff, so sorry about the lack of response to this. Is this happening in any DAW where Z3TA+ 2 was in the project as a VST2?
 
If it's just Sonar, a POSSIBLE workaround (I'm really not sure if it will work at the moment) might be to change the file extension from .vst3 to .dll. That way Sonar might pick it up as a VST2 and potentially resolve your issue (not sure about other DAWs.) 
 
Then again maybe it's not the best idea to mess around with files...
 
- John

John Joseph [Cakewalk]
Hi All,
 
I assume most of us were doing Thanksgiving related stuff, so sorry about the lack of response to this. Is this happening in any DAW where Z3TA+ 2 was in the project as a VST2?
 
If it's just Sonar, a POSSIBLE workaround (I'm really not sure if it will work at the moment) might be to change the file extension from .vst3 to .dll. That way Sonar might pick it up as a VST2 and potentially resolve your issue (not sure about other DAWs.) 
 
Then again maybe it's not the best idea to mess around with files...
 
- John

It doesn't matter VST3 or VST2. I mean I didn't do VST rescan when I install 2.2, so it tried to load VST2, and it produced error.

 
Is this happening in any DAW where Z3TA+ 2 was in the project as a VST2?

Yes, Ableton Live here. I suspect the problem is the 2.2 version is not reading the Z3TA+ 2 program data out of the application files (.cwp, .als, etc.) correctly.

Same thing here. Actually I have two z3ta+2 installations: the normal and the Virus-mod. I'm having the same issue with "normal" z3ta+2 with older projects, but Virus-mod loads just fine (obviously it was not updated as it sits in it's own separate folder). I suggest if you are experienced user you could try a temporary workaround (WARNING1: I have not tried it yet, USE AT YOUR OWN RISK, and I don't know how it will behave with VST3's. WARNING2: since it's a temporary workaround, all your projects done WITH this workaround will have missing z3ta+2 synths AFTERWARDS, when the official fix for 2.2 will be available. To me, no big deal because you can save needful patches if you need them after said fix, but YMMV). 
 
0. Back up your installations, etc, etc. I suggest backing up
- "Cakewalk Content\Z3ta+2",
- your whole "VstPlugins" folder(s)
- and VST3 folder(s) which sit in "C:\Program Files\Common Files".
Please keep in mind that on x64 systems there are two "Program Files" folders, for x64 and x86. I will be referencing to x64 paths only to keep things clearer and since I never installed x86 versions of z3ta.
 
1. Since Sonar allows multiple instances of the same VSTis, you can copy your NEW 2.2 z3ta+2 to a folder in VstPlugins (say, "z3ta+2_new"). Now you will have two z3ta folders in your VstPlugins path. It should look like this:
"C:\Program Files\Cakewalk\VstPlugins\Z3TA+ 2"
"C:\Program Files\Cakewalk\VstPlugins\Z3TA+ 2_new"
(Obviously, if you have a custom Vstplugins path, do it there instead).
 
2. Go to your "VstPlugins\Z3TA+ 2_new" folder and rename the dll from "Z3TA+ 2_64.dll" to "Z3TA+ 2_64_new.dll". Now (might be unnecessary! but I would have done that to be sure) go to "C:\Program Files\Common Files\VST3\Z3TA+ 2" and do the same there.
 
3. Roll back z3ta+2 to 2.1 (it will roll back z3ta+2 sitting in the default folder, but will leave your "z3ta+2_new" unchanged).
 
Now, you could skip steps 4 and 5 and try and go straight to 6, but if doesn't work, do the steps 4 and 5.
 
4. Go to "Cakewalk Content\Z3TA+ 2" folder and copy everything (patches, arpeggiator, etc) from it to:
"C:\Program Files\Cakewalk\VstPlugins\Z3TA+ 2"
"C:\Program Files\Cakewalk\VstPlugins\Z3TA+ 2_new"
"C:\Program Files\Common Files\VST3\Z3TA+ 2" (again, might be unnecessary - but still).
 
5. Delete contents of "Cakewalk Content\Z3TA+ 2" OR BETTER just rename it to some other name so Z3ta+2 would not find it's content there and would search in it's VstPlugins folders instead.
 
6. Start Sonar and perform a VST scan. You should now have two Z3ta+2 instances, one called Z3ta+2 64, and the other Z3ta+2 64_new.
How it should work: your older projects will load "Z3ta+2 64.dll" from "VstPlugins\Z3TA+ 2" which is v2.1, and you can try your new "Z3ta+2 64_new" which is v2.2.
 
Now, since I personally almost never return to my older projects AND I definitely love the new Z3ta+2 (the fix for the nasty LFO sync/waveshaper bug is finally here, yay!), I don't see the point of doing it myself. Sorry about that, you'll have to test it on your own. But - again - my Virusmod Z3ta+2 loads fine, so this should work. Please comment if any steps are unclear how to perform them. I hope this can be helpful to someone.