Ezd2 overwrites ezd1 upon upgrade. Evidently the demo does not.
Tom

DeeringAmps
Ezd2 overwrites ezd1 upon upgrade. Evidently the demo does not.
Tom

Ah thank you.  Thanks for the warning.  Maybe its possible to use the installer to specify a separate location so that does not happen?
 
 

Oddly, I opened old projects with EZD1 and YES, the other soft synth routing was changed.  Once changed back it was ok. Synths were frozen as well... Acted the same except for the changed routing.

StumpyV
So I guess you have to pay for the upgrade to get support. Typical for software companies...I don't care how old a product is, the manufacturer should always try to offer some support. 

If you buy Logic Pro X, you get 90 days of free complimentary phone support. After that, it's $99 per incident. Or you can buy one year of email/phone Professional Audio support, which is valid for only the latest version. I tried to find the price but couldn't; when I called the number on the Apple web site to check price I had to enter a registration code, which I didn't have. They do not list the price although they do list the price for 1 year of video support, which is $799. Presumably the pro audio support is less.
 
Cakewalk continues to offer free support. The tradeoff is that it's for current users. But, they are the ones working their way through new software and likely have the most questions. Cakewalk could just charge everyone for support, but I think most people if offered a choice between a plan like Apple's or free support for current users would pick the latter.

Have to disagree with the blame being with toontrack.  If a plugin works on every other daw with no issues and the one that it doesn't work with makes no effort to get it to work than I think the fault is with the daw.
 
That being said, I am a long time Cakewalk/Sonar user and i love it.  This is the first time I have never been able to resolve an issue.  I would put my Sonar against my friends Logic any day of the week.  However I think they dropped the ball on this one.  That's just the way I feel a bout it.  I am very disappointed because I really wanted to explore ezdrummer2.  But I have used ezd1 on just about all of my projects since I got it (tough to get a drummer when you need one) and it has also always served me well.
 
Also in my opinion software companies stop supporting older products because they want you to buy their bigger, better, newer products.  If something doesn't work with an older version just say so and thats all the support I need. 
 
Also for those of you that have had trouble with toontrack support I can only say that they were fast, courteous and very informative.
 

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

StumpyV
Have to disagree with the blame being with toontrack.  If a plugin works on every other daw with no issues and the one that it doesn't work with makes no effort to get it to work than I think the fault is with the daw.

 
Maybe, maybe not. Regardless, the usual protocol is that plug-in manufacturers test their product with various DAWs to insure compatibility. Cakewalk gets regular requests from plug-in developers for X3 copies suitable for testing.
 
The reason it can't work the other way around is because Cakewalk isn't developing the plug-in. So, it's not Cakewalk's responsibility to find issues a plug-in might have with Sonar while the plug-in is being coded. However, if the plug-in manufacturer alerts Cakewalk that there is a problem during the coding process, and it's because of something non-standard Cakewalk is doing, it's either Cakewalk's responsibility to fix it, or for one company or the other to find a workaround until it can be fixed.
 
Finding there's a compatibility problem after a product has been released is problematic. There are already plans in place and timelines to be followed, so a company like Cakewalk can't just drop everything and work on a fix without causing disruptions. For example if they're working on X3e bugs they want to correct for a future version, they would have to decide whether to put that on the back burner so they can deal with whatever the problem is with EZD2.
 
What's more, finding a fix is not sufficient as there then needs to be considerable QC to make sure fixing one issue hasn't broken other things, like what happened when Sonar did a fix to accommodate POD Farm but which caused problems with other plug-ins.
 
None of this stuff is as simple as I would hope...

I'm not sure this problem can/will be fixed. I believe it is caused by the way Sonar handles/names its I/O tables. Which would be a major re-write of Sonar's routing paradigm code. If Toontrack can hand off the new outputs to every other major DAW and those DAWs can handle it, then Sonar is doing something non-standard with its I/O routing. Which some of us have assumed for years.(ie "Why can't I route a synth to an audio track and record it live?") If Sonar does re-visit its routing, we probably won't see it until X4 or X5. By then most users will have "fixed" their old projects or reverted back to EZD1. So I'm not sure it would be a priority for Cakewalk.

> I'm not sure this problem can/will be fixed.  I believe it is caused by the way Sonar handles/names its I/O tables.
 
Interesting speculation but none of us have the EZD source code, probably not even Cakewalk.
 
So the question is, what makes EZDrummer 2 so different over Addictive Drums 2(which works) or Session Drummer when hooking into a Sonar? They are both similar products how come XLN can handle this? If XLN can do it I don't see why another third party couldn't right now, unless they haven't accommodated for Sonar correctly and tested it... Or EZD is trying to use a different VST supported hook in point that AD2 and Session drummer do not use (unlikely) which causes a different set of issues.
 
Cheers...

I think he issue is caused by EZD2 having twice as many outs as EZD1.  EZD2 also overwrites/replaces EZD1 when it is installed.  This causes projects that used EZD1 to mess up the routing of the entire project.
 
It doesn't affect other VSTs like Addictive Drums or Session drummer because they haven't doubled the number their outputs, AFAIK.
 
I have no idea where the problem lies, be it Cakewalk, Toontrack or both/neither.
 
I would like it fixed, if at all possible.  There obviously is a workaround, but it can be time consuming on complex projects.
 
Ho hum..