Nothing on EZ Drummer 2 Issues

Seems to be only Sonar has this issue and some collaborative effort is needed to resolve it... it would be appreciated if Cakewalk and Toontrack worked this out.

I took the one SONAR project that I had using EZdrummer1, saved it as another name and then changed the messed up routing on two softsynths.  I had to split the instrument tracks for both of them.  One of the softsynth tracks referred to a version that I no longer had so I inserted a new soft synth and routed the midi to the new synth tracks.  Took me maybe 5 minutes.   So, are you saying that  sort of thing will not fix your tracks?
 
Based on the release dates of past SONAR versions, I'd be willing to bet that the Cakewalk team are hot and heavy into preparing SONAR X4 for release candidate versions so they can test it before going into gold status.  They probably want to deal with a 3rd party soft synth issue at this time like they want a hole in the head.  I'd be willing to also predict that SONAR X4 won't have this problem.
 
TT went to work immediately on the multi channel crash issue and the recent update fixed that.  They are waiting on CW to get back to them and if there is anything on the TT side of things that can be worked out to make SONAR happy (based on what I've seen) they'll be right on it.  But with every other DAW host picking up the new, extra 8 stereo outputs just fine it looks suspiciously like the issue is with the host.  But even that has a quick workaround. 

Language filters are inherently incapable of understanding context or nuance. Think of them as being somewhat like politicians, but less likely to start wars.

My only gripe with Toontrack is their moderators who answer posts at the Toontrack forums.  Hard to be any more rude in many cases or they totally interpret the question wrong and come back with an answer out of left field.
 
Toontrack does seem to be taking their time on the Superior update to use the EZD2 kits within Superior.

konradh
If Sonar ignores an issue with the most popular virtual drummer in the world because they are preparing a new release, I think they are making a big mistake.

Unfortunately it's not that simple. We all know Sonar works with virtual instruments, including ones that have multiple outputs, but here we have one instrument where there's some kind of issue. Regardless of whether it's due to Toontrack not recognizing Sonar properly or the reverse, having to change code to accommodate one instrument risks breaking the code for instruments that do work. A lot of QCing would have to be done before a patch could be released.
 
Remember the POD Farm 2 issue? It had problems with X3 because X3 changed the plug-in handling to follow protocol more strictly. When Cakewalk came up with a workaround in Sonar to accommodate POD Farm 2, it caused problems with other plug-ins that followed standard plug-in handling behavior. Eventually Sonar had to revert back to the way it was, and so you have to use a simple workaround with POD Farm 2. At least in that situation there was a satisfactory resolution.
 
IIRC a similar situation happened with Universal Audio, where Sonar made some changes to accommodate UA but then UA made some changes that didn't require the changes in Sonar any more. So when UA fixed the problem at their end, it broke the previous Sonar fix. Now everyone has it sorted out, but for a while using UA's updated OS software with Sonar was problematic.

I've fixed weird problems after installing new plug-ins with the reset/rescan routine. Maybe worth a try.

As Craig has mentioned, I have seen the results of two independent teams working to solve an issue between a host and a 3rd party plugin.  It happened early as I came on to the Toontrack betatest team.  I can't recall what it was exactly but because of my report, Toontrack implemented a change in EZdrummer to accommodate a SONAR behavior and almost simultaneously Cakewalk implemented a change to accommodate the EZdrummer behavior and they ended up cancelling each other out and causing other issues.
 
If the softsynth output issue can be resolved by individual users making a manual change in their projects, I'm thinking it would be better to do that than to open a can of worms to fix legacy issues that could snowball into problems for all the other softsynths down the line.
 
My $.02

To clarify, I was not being critical of Cake.  I have developed a lot of software and I know how complex this is.  I just wish Toontrack or Cake would give us a status.
 
As for my problems, they are repeatable and have been replicated by Sweetwater.  The fact that we don't see them on the Toontrack forum is not really indicative since Toontrack has not been updating the forum consistently and it leaves posts in "awaiting moderation" mode for weeks.
 
At this point, I am going to get a refund for the upgrade and buy additional drum kits for Kontakt.

Hill62
Ultimately it is on Toontrack to test their updates on various DAWs.

Indeed, this is the usual protocol. We often have manufacturers contact us for a copy of Sonar they can use to test their plug-ins, ReWire compatibility, etc. If you think about it, it's much easier to test a plug-in with a very finite number of DAWs then to test a DAW with a virtually unlimited number of plug-ins.
 
It's generally considered inappropriate to have one company beta test another company's product. This isn't just a matter of courtesy, but for competitive reasons the manufacturer might not want to divulge details of a new product while it's still being developed.
 
This doesn't rule out companies working together to solve problems, but that usually happens after the product is out, or an update occurs during a product lifetime that breaks compatibility. 
 
There is one exception because I remain on good terms with many software developers. They will test their products with Sonar but they are not always Sonar experts. If I'm a long-term user of their products, sometimes they'll make sure I have a copy because they know I'll put it to real-world use and will report back on the results.

I have EZ Drummer 2.  I don't use it on every project, but I didn't have any issues with it and Sonar.  Am I in for a rude awakening?

Well, I am finished with the drums for our first song and did them with EZD2 loops. Sounds pretty good to me. I didn't have any issues, and I had to reinstall a few plugins after moving everything to the SSD, one of which was EZD2.  It couldn't find a few things,as it was with Nectar and Bias. After reinstalling, it was all ready to go when I opened the project. I am a noob, so take it for what it's worth.

FULL DISCLOSURE:  I just remembered that I am still having one issue: sometimes drums come out on the wrong track.  Example: snare, toms, and kick all bleeding into the snare track.  I had to open a separate instance for just the snare.

olemon
I guess EZD 2 was released about this time last year.  I upgraded at about the same time as the OP.  Was this a fairly isolated problem that only a few Sonar users experienced?

The routing issue affected everyone using Sonar, AFAIK.  A workaround was supplied with the update - using the steps Konrad supplied above.
 
The other issues seem to only have only affected a few users.  I was not one of them.

Thanks all!  I emailed tech support (Cakewalk) about this and they suggested the re routing thing that many of you suggested.  I don't quite understand the concept of the "Simple Instrument Track" but the tech guy seemed to imply that in a MIDI instrument track there is also an audio track.  Could somebody please clarify that for me.  I'm used to just thinking of it as a MIDI track being played by a VSTI with no audio (per se) involved.  konradh, when I get a moment I will try your suggestion about un installing and re installing EZD 1 & 2.
 
Peace
 
John B

Johnbee58, I hope it all works out.
 
It sounds like you have a question about Simple Instrument Tracks, so I will try to help.  Forgive me if I am saying stuff you already know.
 
1-An external synth requires two tracks: a MIDI track to send it the notes, volume, etc. and an audio track that plays the sound coming from the synth that is plugged into your interface.  Sonar does not know these are connected or are part of the same instrument.  It is up to you to name them and keep them straight (e.g., Motif MIDI, Motif Audio).
2-Virtual instruments are the same, except that since both the audio track and the instrument itself reside in your computer and in Sonar, Sonar knows the MIDI and audio tracks go together.  If you mute or solo one, the other follows along.
3-When you add a soft synth (virtual instrument) in Sonar, Sonar asks you if you want a Simple Instrument Track, or separate audio and MIDI tracks.
4-If you choose Simple Instrument Track, you will just see one track in Sonar, but in Inspector there will be tabs so you can look at the MIDI or the audio parts of the track.  You can also highlight the track, right click, and ask to split it into an audio track and a MIDI track (but Sonar will still know they belong together).  If you split the Instrument track, you can also have Sonar put them back together again later if you choose.
5-Instead of choosing Simple Instrument Track, you can tell Sonar to create separate audio and MIDI tracks.  You can also choose to have multiple audio tracks and one MIDI track which is a good choice for drums since you may want separate tracks with separate volume, reverb, and EQ for kick, snare, hi-hat, toms, cymbals, etc.
 
A lot of people here always use separate tracks instead of Simple Instrument tracks.  I am mixed.  I use Simple Instrument Tracks for single sounds like Piano or Bass.  I use separate MIDI and audio tracks for drums or string sections when I want to control each sound separately.
 
For RealGuitar, I have two MIDI tracks and one audio track because I want notes for chords on one MIDI track, and keyswitches for strumming on another track.  I do that by telling Sonar to create a separate MIDI and audio tracks, and then cloning the MIDI track before I enter any notes.