Did Cakewalk make any comment yet?

konradh
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.

OK, here's your update.  It's not getting fixed until Cakewalk tells them where the problem is occurring in the SONAR program.

Well, then let me modify my statement to this:
 
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 Cakewalk.  Not good.

Sorry if Cakewalk stopped production every time a plugin didn't work they wouldn't get anywhere. The guys who make the plugin should be updating and taking the initiative, not Cake regardless of fault. If there's an issue with Sonar don't expect a fix until X3F (hopefully) or X4. Or hassle Toon for a patch.

I think speculation as to how Toon or Cakewalk is communicating is unhelpful to be honest. Nobody knows what is going on right now.

I'm sure more info will come available when they have the time to get around to it.

Cheers...

konradh
Well, then let me modify my statement to this:
 
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 Cakewalk.  Not good.

My status: Paid for EZ2, can't use it and had to uninstall it because of corrupted projects, Toontrack tell me no solution to issue, got a refund from sweetwater.

Wow lots of speculation and confusion on this thread. Sorry I hadn't seen this specific thread earlier or would have commented :(
 
So from what I understand, the new version of EZdrummer upped the number of outputs exposed by the plugin but did not rev the VST ID. What that means is the host (SONAR) has no idea that the number of outputs changed dynamically. Keep in mind that dynamic I/O's were officially only specified as part of VST3 so this is NOT a spec issue as someone suggested. As such SONAR doesn't detect and handle this situation. Further explanation below:
 
Virtual instrument audio input ports in SONAR are manufactured based on the number of outputs of a synth. So if you have multiple synths in the project and one of them changes the number of outputs dynamically, all the port numbers will slide by the "extra" ports causing unwanted behavior. Note that this only impacts projects saved with the OLD version of EZDrummer that are now opened using the new version. New versions will always have the new number of ports and will be fine.
Anyway, its important to understand that this is the root cause of the problems being faced here - i.e. projects saved with the old version and opened using the new version.
 
So how do we fix it? Every version of SONAR will be susceptible to this problem - X3 and lower. Some options:
 
1. There are several simple workarounds on this thread to break up instrument tracks and reassign the ports, then convert back to instrument tracks.
 
2. Toontracks can add a simple workaround to their plugin preferences that allows the user to set the default number of outputs (the default should be the old number). That way users can choose how many outputs they want on demand when creating the instrument. 
 
3. A future version of SONAR would need to add code to save the number of outputs in use by the plugin at the project level. Then when the project is loaded we would detect that the saved version and the new version is different and go through an automatic port remapping for all tracks in the project to fixup the new ports added.
(I just checked our code and fortunately we do save the number of outputs and the output names, phew!) 
 
In summary, its an unusual thing for a plugin to change its published number of outputs for the same version without revising the VST ID in VST2. As such its not something we commonly encounter. Its unfortunate that this was not detected in Toontracks beta process - Cakewalk isn't officially on their beta so we'd never have seen it, but more surprising is why their SONAR testers didn't find it, since it would be a very basic compatibility test to load older projects. Cakewalk gives numerous plugin vendors access to all our beta's to catch problems early and notify us. Waves for example is one such vendor who worked extensively with us on X3. Anyway, I think it would be a good thing for us to guard against in the future so I will try and add fixup code for this in the next version of SONAR. That doesn't help users of prior versions obviously so one of the other solutions I listed should be pursued for that case.
 

Thanks for clarification Noel

Thanks Noel for the response.  What puzzles me still is how Reaper, Samplitude Pro X and Studio One 2 didn't get bit by the same bug?

Hopefully, now we can move forward toward a workable compromise solution till all projects are finished with EZdrummer 1 and everyone works with SONAR X4.
 
EDIT:  For the record and the forum member's information, I am one of two SONAR users that are betatesters and frequently visit this forum.  I wish I had caught it but all of my active projects were in Pro Tools 11, Samplitude Pro X and Studio One 2 this development cycle.  None of those platforms exhibited the behavior.  My time has been relatively full of active projects for clients and no game stopping bugs appeared while working on those tunes in other platforms.  
 
All of my old EZdrummer/SONAR projects have been long finished and archived over a year ago.  I did create some test projects in SONAR but because they were created from a clean slate, no problems appeared.  It didn't occur to me that SONAR would be any different regarding legacy projects.

I don't actively use SONAR anymore but I've been a Cakewalk user for so long and I have such an affinity for this forum that I will try to still represent the SONAR user base and liaison between Toontrack and Cakewalk users to the best of my abilities as time permits.

Noel is the Kontakt issue related in the slightest?
http://forum.cakewalk.com...aspx?m=3064712&p=1

Thanks..

CakeAlexS
Noel is the Kontakt issue related in the slightest?
http://forum.cakewalk.com...aspx?m=3064712&p=1

Thanks..

I don't think so. Its a different issue - that string is coming from the Synth not SONAR.