For you users who are waiting for an EZdrummer solution from Toontracks, I checked back with them again on this issue.  Erik of Toontrack asked for some help from Cakewalk back on June 16th.  Cakewalk asked them to try some things from within SONAR.  Since then nothing.

Without Cakewalk's help they cannot find where the problem lies.  SONAR is the only host that has this problem and without some inside information from Cakewalk they are at a stand still at finding a final solution.
 
EDIT:
I need to correct my post regarding the timeline of the contacts with Cakewalk.  TT developers sent emails to CW on May 8th.  This was, as I have been told, two days after the release of EZdrummer 2.  Since then, eight more emails have been sent asking why the problem occurred so that changes in EZD2 may be done in order to accommodate SONAR's behavior.

Mod Bod
For you users who are waiting for an EZdrummer solution from Toontracks, I checked back with them again on this issue.  Erik of Toontrack asked for some help from Cakewalk back on June 16th.  Cakewalk asked them to try some things from within SONAR.  Since then nothing.

Without Cakewalk's help they cannot find where the problem lies.  SONAR is the only host that has this problem and without some inside information from Cakewalk they are at a stand still at finding a final solution.
 
EDIT:
I need to correct my post regarding the timeline of the contacts with Cakewalk.  TT developers sent emails to CW on May 8th.  This was, as I have been told, two days after the release of EZdrummer 2.  Since then, eight more emails have been sent asking why the problem occurred so that changes in EZD2 may be done in order to accommodate SONAR's behavior.

Hi, Mod,
I don't think it's a good policy to realease a software/plugin, state full compatibility when upgrading from EZ1 and only after that, try to resolve the problems. In my opinion, I cannot sell anything If I cannot garantee what I'm stating is true.  When you scroll down the "Meet your new drummer" page, in the unsupported hosts, you can see statements like this: "Untested, may work", and even so, the table shows the check mark in some functionalities, which seems contraditory...  It doesn't sound good to me, causes a impression of irresponsability...

The fact of the matter is that these two companies are businesses.  
 
EZDrummer 2 is a plugin that requires a host and Toontrack has 10 or so supported hosts, Sonar being one of them.  Therefore this issue has the potential to effect 1/10th of their customers (assuming all hosts are used equally) 
 
I can't even fathom how many sonar users are out there, because lets not forget that Cakewalk is owned by one of the largest audio manufactures in the world, Roland.  Of these hundreds of thousands of users how many of them use EZDrummer 1?  Of these users how many of them use EZDrummer 1 in Multi out?  Of these users how many of them upgraded to EZDrummer 2 and are still working on old projects that use multi out?  My guess is that its is a lot less than 1/10th of their user base.   And finally of this relatively small amount of users, how motivated would sonar be to solve an issue for old versions of their software (something that does not generate revenue?)... Im not saying that they wont, Just that its not likely a high priority to them.
 
With this logic, which company does this impact more from a business standpoint?  Which company would therefore be more motivated to solve the problem? 
 
 
 

Atsuko

Mod Bod
For you users who are waiting for an EZdrummer solution from Toontracks, I checked back with them again on this issue.  Erik of Toontrack asked for some help from Cakewalk back on June 16th.  Cakewalk asked them to try some things from within SONAR.  Since then nothing.

Without Cakewalk's help they cannot find where the problem lies.  SONAR is the only host that has this problem and without some inside information from Cakewalk they are at a stand still at finding a final solution.
 
EDIT:
I need to correct my post regarding the timeline of the contacts with Cakewalk.  TT developers sent emails to CW on May 8th.  This was, as I have been told, two days after the release of EZdrummer 2.  Since then, eight more emails have been sent asking why the problem occurred so that changes in EZD2 may be done in order to accommodate SONAR's behavior.

Hi, Mod,
I don't think it's a good policy to realease a software/plugin, state full compatibility when upgrading from EZ1 and only after that, try to resolve the problems. In my opinion, I cannot sell anything If I cannot garantee what I'm stating is true.  When you scroll down the "Meet your new drummer" page, in the unsupported hosts, you can see statements like this: "Untested, may work", and even so, the table shows the check mark in some functionalities, which seems contraditory...  It doesn't sound good to me, causes a impression of irresponsability...

If that's the case then maybe Cakewalk should advertise that they aren't fully VST compatible because they don't support dynamic i/o functions between their product and VST plugins?
 
Fact is, Toontrack has the desire and the ability to compensate for one host program if they only knew the secret handshake that Cakewalk requires to get information to and from the plugin.  Now, if a small group of SONAR users want to dig in and support Cakewalk's silence then go ahead.  I'll be using EZdrummer 2 on new SONAR projects as well as projects in Pro Tools 11, Samplitude Pro X, Studio One 2, Reaper and Pro Tools 10 which have formats in RTAS, AAX and VST and all of them don't exhibit this issue.

Or maybe it's as simple as a line of code that says " IF "SONAR user" THEN PRINT "Sorry, SONAR user.  You only get 8 stereo channels.  Buy a different host program for enhanced I/O." 
CALL SHUT_OFF_HALF_THE_CHANNELS_ROUTINE.
 
 

TESLA 82
The fact of the matter is that these two companies are businesses.  
 
EZDrummer 2 is a plugin that requires a host and Toontrack has 10 or so supported hosts, Sonar being one of them.  Therefore this issue has the potential to effect 1/10th of their customers (assuming all hosts are used equally) 
 
I can't even fathom how many sonar users are out there, because lets not forget that Cakewalk is owned by one of the largest audio manufactures in the world, Roland.  Of these hundreds of thousands of users how many of them use EZDrummer 1?  Of these users how many of them use EZDrummer 1 in Multi out?  Of these users how many of them upgraded to EZDrummer 2 and are still working on old projects that use multi out?  My guess is that its is a lot less than 1/10th of their user base.   And finally of this relatively small amount of users, how motivated would sonar be to solve an issue for old versions of their software (something that does not generate revenue?)... Im not saying that they wont, Just that its not likely a high priority to them.
 
With this logic, which company does this impact more from a business stand point?  Which company would therefore be more motivated to solve the problem? 
  

As far as I know, all EZ1 user's that upgraded are having problems, not only with multi outs but with other VST's that are in the project that simply looses setup in Sonar. As a plugin manufacturer, I'd never assume hosts are used equaly but I could accept that I was making something to work just for a few and would put Sonar in the unsupported table list with the "Not tested, may work" information for those who have EZ1 installed.
Another thing I didn't see informed in Toontrack's site is that EZ2 would cover EZ1, at least, it isn't very clear for me. The consumer should have the option to have both installed.  I really don't matter with the motivation of the business's companies, when I'm interested in buying anything I reference myself in the given information about the product to make my decisions, but if the information given is wrong or insufficient?
 
P.S.: Cakewalk is a Gibson company, now.

 
 

Mod Bod
If that's the case then maybe Cakewalk should advertise that they aren't fully VST compatible because they don't support dynamic i/o functions between their product and VST plugins?

I agree with you on this matter.  All the information for the consumers is the best practice.

Mod Bod
Fact is, Toontrack has the desire and the ability to compensate for one host program if they only knew the secret handshake that Cakewalk requires to get information to and from the plugin.  Now, if a small group of SONAR users want to dig in and support Cakewalk's silence then go ahead.  I'll be using EZdrummer 2 on new SONAR projects as well as projects in Pro Tools 11, Samplitude Pro X, Studio One 2, Reaper and Pro Tools 10 which have formats in RTAS, AAX and VST and all of them don't exhibit this issue.

Or maybe it's as simple as a line of code that says " IF "SONAR user" THEN PRINT "Sorry, SONAR user.  You only get 8 stereo channels.  Buy a different host program for enhanced I/O." 
CALL SHUT_OFF_HALF_THE_CHANNELS_ROUTINE.
 

It's not the case of support "silence" of Cakewalk, not me, I'm just questioning information given by Toontracks in their own site. As a consumer, I would feel misguided.  And I wouldn't bother if they really tested and printed this, as you put: " IF "SONAR user" THEN PRINT "Sorry, SONAR user.  You only get 8 stereo channels.  Buy a different host program for enhanced I/O." CALL SHUT_OFF_HALF_THE_CHANNELS_ROUTINE."  And I would add, "OR STAY WITH EZ1".
 
For me, it'd show more responsability with their consumer, specially, EZ1 owners, could have the right information to make their decisions. I really hope all these issues to be solved because I really liked EZ2 features but I'm gonna wait for the resolution.

Cakewalk would probably argue no DAW is fully VST compatible. Not that anybody knows what the real isssue is.
 
Regardless I'm probably way off base here but I keep getting the feeling it (now we are talking about multi-outs) might be related to this issue (even though it is completely different we do see issues when using lots of channels):
http://forum.cakewalk.com/Kontakt-Error-in-Sonar-X3E-m3064712.aspx
 
Or it's a problem with EzDrummer source code.
 
There is no use in speculating though, nobody knows the answers (they don't have the source code to look at for either product) so anybody who says they know what the problem is (including me), is probably wildly inaccurate.

You could be right, Alex.  TT has to make special concessions for the I/O names for the SONAR X series so that they show up with some sort of normal naming convention.  For example, the output names in Superior were displaying as expected in SONAR 8 but they didn't make much sense at all in SONAR X3 until this last SD2 update.
 
We can all speculate who, what or why this issue manifested with EZdrummer 2 but I can say without a shadow of a doubt, that Toontrack is actively fixing issues,making improvements to and adding minor features to EZdrummer 2 as I type this message.  They want to do anything they can on their side to help the folks with active legacy EZdrummer 1 projects enjoy the EZD2 product as much as those of us who aren't affected by the input/output shift.  (This isn't a put down - I don't have any active EZdrummer 1 projects in SONAR because all of them are finished and archived and I don't have a need to reload, open them and revisit the projects or I converted them to Superior Drummer projects long ago.)

But until the SONAR community starts letting the CW developers know that they want to use EZdrummer with the same ease as the Pro Tools, Reaper, Cubase, Studio One, Logic and Samplitude users (and others that I have probably missed.)  I dunno, maybe we should send a quarter in an envelope for the call?    Just respond to the email requests from Toontrack for more information

Heck, I'd be ok if it's something that can't be fixed because of legacy compatability in SONAR and we just had to be satisfied with a workaround until X4 addresses the issue.  Just let the users know.
 
 

My status:  Paid for EZD2, can't use it and had to uninstall it because it corrupted projects, and I am not getting updates from Toontrack.
 
Not good.