I had one of those follow on emails from Sweetwater asking how I was getting on with EZdrummer2.
 
I decided to answer.
 
For those who did not follow the issues with routing, here is my original thread.
 
http://forum.cakewalk.com/Problems-after-installing-EZdrummer2-m3035781.aspx
 
The Senior Sales Engineer replied that he would have a word with the Toontrack rep who was in that day.
 
His reply was that " It looks like Sonar has some weird funkiness when you open an existing session.
This doesn't affect new sessions, only old ones. Sonar has no plans to fix the
problem."
 
Hmmm.  So is this a Sonar issue, or a Toontrack one?  Both seem to blame the other.
 
Cakewalk staff did get back to me about looking into it.  Toontrack did not even have the courtesy to reply.
 
I know there is a workaround to this - i.e. reroute every single VSTi in a project created with EZdrummer1, but that is not the point.  This has cost me a lot of time, and still is rearing its ugly head.

I've haven't had any problems at all with old projects that have EzDrummer v1 tracks, after upgrading to EzDrummer v2. I note that I have never used single-instrument tracks. I've always routed midi and audio separately. 

Might have been better to continue the original thread rather than start a new one otherwise those following the original thread don't get notified and we get into the realm of duplication and noisy repeating/looping

Regardless I was confused, are you saying that Toontrack says that Cakewalk has no plans to fix it (which sounds like an odd thing to say from their perspective), or are you saying Cakewalk said that directly?

Guess you are waiting for a statement from cake regardless..

Cheers..

Sorry for the confusion. I thought it was relatively clear.
 
The quote in my OP is a direct quote from the email that I received from Sweetwater's Sales Engineer, after he spoke to the Toontrack rep. - "Sonar has no plans to fix the problem."
 
Cakewalk have not stated this to me.  I am not privy to the conversations between Cakewalk and Toontrack.
 
I can only report what the Sweetwater Sales rep says that the Toontrack rep said.
 
HTH.

like SuperG says, do you have the same issue(s) when using non-simple-instrument-tracks? (ie, the audio & midi tracks are separate) and as an afterthought, shouldn't a multi-out vst always use non-SITs?

lawp
like SuperG says, do you have the same issue(s) when using non-simple-instrument-tracks? (ie, the audio & midi tracks are separate) and as an afterthought, shouldn't a multi-out vst always use non-SITs?

From reports in the original thread it affected S.I.T.s and separate Audio/MIDI tracks.
 
EZdrummer can be set up as multi out or stereo out.  So, if using only stereo outs it works fine as an S.I.T.
 
 

sorry, must have missed that