Hmm I assume people have tried it with new projects and have done a VST reset and rescan afterwards...?

http://www.cakewalk.com/S...ommended-for-Upgraders

If that works then the issue is that Toontrack didn't test the backward compatibility of it's products very well or it needs an update to handle the latest Sonar X3E update.
 
(edit for typo).

@StumpyV
 
Even Microsoft drops support for older version of software.  XP support was dropped.  It is prohibitively expensive and counter-productive for a company to provide endless support on obsolete versions of software, as it requires additional training and other resources, on top of the fact that companies generate income through sales of new versions and new releases of products.
 
There is a way for you to continue to get SOME assistance with issues in older non-supported versions of Sonar.  It lies in that this forum exists, that it can be searched quite well with Google, and that most solvable issues for an old and no longer supported version of Sonar will have been brought up and resolved in forum posts.
 
What I mean is that there is little likelihood in a solvable issue from a prior version of having been brought up and posted in this forum, and that you can therefore do searches in Google to located helpful posts so that you too can either find a workaround or a solution to most issues raised for your older Sonar version.
 
To search in Google for forum posts, try using this format for your search terms:
 
site:cakewalk.com forum term1 term2 term3 etc... (replace the 'term1' 'term2' and such with whatever you are trying to find info for.
 
Example:
 
site:cakewalk.com forum now time not scrolling
 
The 'site:cakewalk.com forum' portion of the search terms tells Google to only search for results for the Cakewalk web site forums, and then whatever other terms you added are applied to searching that site.  This makes it a pretty good tool for finding info on prior experiences folks have posted about, for a given issue.  Since most issues with a given old release will have been posted to the forum long before it gets to the point of being unsupported, you stand a very good chance of locating whatever available information exists for whatever issues you are searching for.
 
I hope the above helps - please post back if I have confused you or you want additional information.
 
As far as there ever being 'endless support' for anybody's product, it's just not a business reality, and not likely to ever happen, particularly for a small company like Cakewalk.  :)
 
Bob Bone
 

StumpyV
Thanks i checked it out but it didn't help.  Unfortunately I have found out it is a cakewalk issue.
 
The problem is quite simply that EZDrummer 1 had 8 stereo outs and EZDrummer 2 has 16. For some reason Sonar can not deal with the updated EZDrummer changing its number of outputs. Every other host that Toontrack supports works and does not have a problem with this. 

Yes it may be a cakewalk issue but the workaround I described (HERE-->  http://forum.cakewalk.com/FindPost/3045236) gets you back to a workable project.
 
YMMV.
 

I believe that link was posted in #2  above

scook
I believe that link was posted in #2  above

That's a relief. I thought I was having deja vu...

I believe that link was posted in #2  above

Deja vu all over again!
T

CakeAlexS
Whether it's Toontracks fault or not, it's really up to Toontrack to fix it and approach Cakewalk if they think there are any issues with Cakes code (as many VST's are working fine with X3E I would regard it unlikely to be Sonar at fault though). It may work with other software scenarios but that does not rule out any fault with the plugin code. Ta

As of two weeks ago, TT was still waiting for CW to provide some information to help them sort this out.  Unless this has changed, I would remind everyone it takes two to Tango.  Why is CW silent?  I have my suspicions.
 
I place my bet that there is nothing wrong with TT code.  TT supports Mac, VST, RTAS and VST.  Funny that SONAR can't deal with the addition of 8 more outputs and all of the others can.

@ModMod Please refer to posts #16 and #17. Cake does not have access to EZ Drummers source code. It's really is ToonTracks responsibility to get this fixed regardless of who is at fault. They should be communicating with Cake if there are any issues, for all we know it may already be happening.
 
BTW I'm running Addictive Drums on 16 channels quite happily, any backwards compatibility issues from going from 8 to 16 is probably down to plugin. Of course there could be an entirely different issue causing this (none of us know the real problem).

Cheers...

As you can see from my post above, this is a little more serious than having to go in and adjust some INs and OUTs.
 
If it helps Cakewalk/Toontrack isolate the problem, I should let them know that I already had an intermittent problem in which some projects would stop playing VIs (soft synths) after a certain number were added—and the number was not always the same.  Sometimes 13 would be ok and 14 wouldn't; sometimes six would be ok and seven wouldn't.  Sometimes I would lose all project audio.  I did extensive investigation to validate this is not a memory issue.
 
There was also an intermittent issue with Sonar changing VI (synth) routing.  I would load a project and suddenly RealGuitar would not play because it was routed to Fantom or some other random thing.  (RealGuitar is just an example and not the only one to have a problem.) This was annoying but easy to correct once the problem was identified.
 
The old problem was not too bad because things would work after I froze some VIs and/or reboot Sonar.  With EZ D 2, projects get corrupted and synths can't be unfrozen for routing correction.
 
One last bit of information.  Although I could be wrong, I do not recall the old problems ever happening with SI Elec Piano or SI Bass.  Maybe there is something unique about their architecture or outputs.
 
The bad problems did not start until EZ D 2, but I am saying that maybe Cakewalk should look into the areas I noted.  There could be a couple of problematic code paths that are getting blown up by EZ D 2.