daveny5

RogerH
How do they (Cakewalk) expect us to find and report bugs, when the updates comes so fast?????

You're the first person to ever complain the updates came too fast. 

Thanks. Finaly I'm first at something 

I wish my wife could say that to me... lol
 

Please please please!  Fix the no suck button! Mine is stuck in the "suck enabled mode"!
 
Really liking  X3.   thanks.

So far...
 
I had some issues with Pro-Channel. Seems I had two Pro-Channels working on several midi-audio tracks. I could display one in the console view, and another in the Inspector. The Inspector one did not manipulate the light/buttons in the console view, but both were active as I hear changes when modifying either EQ. In addition, there were other midi-audio tracks that would not display a Pro-Channel in the Inspector at all, although they would in the console view.
 
Thinking back - I believe I originally started the project in X2 Essential. I decided to delete these tracks, since they were only VST synth audio outs, and quickly recreate them. (Colored tracks and busses made this really easy...). Problem solved - it's likely there's a corner-case type of problem when opening a file from a non-ProChannel version of Sonar - but it's unlikely that most folks will run into it.
 
One bad 32 bit plug-in made the teleport bridge blow - not much to report there....
 
 
 
 

Noel Borthwick [Cakewalk]

MattyBoy
Noel, do you consider the stability issues with having multiple VST with Midi Out a fundamental issue, and will it be addressed in X3c? The release notes for X3b said it had been fixed, but it's till broken... 
 
Stability:

• Resolved a crash when using direct MIDI output with multiple VST Instruments simultaneously, such as multiple instances of JamStix or Catanya (CWBRN-5781, CWBRN-2504, CWBRN-2564, CWBRN-1739)

 

The original crash was definitely addressed - I reproduced and fixed it myself and tested with Jamstix. This is another variant that was not in our system. It probably won't make it into X3C due to time constraints but we'll definitely do our best to address it for the next update since its an important fix. Sorry for the delay but there have been a several lot pressing issues to address before this one.

Thanks for taking the time to respond Noel, it's appreciated, and great news that you'll be looking to address this in the next  update after X3c. I'm sure you've seen the other posts by X3b users that show this is not just restricted to Jamstix / Catanya;  VSTs such as Kirnu Cream, Reaktor etc all cause crashes when Midi out is enabled and there is more than one instance of the VST. Hopefully the fix will address the underlying issue so any VST with Midi Out enabled will work with more than one instance.
 
forum.cakewalk.com/FindPost/2914856
forum.cakewalk.com/FindPost/2912793

hockeyjx
Am I the only that thinks:
 
1)Cake had a good vision for the future, but it took a little longer than customers were ready/patient for?
2)The Roland actually hampered Cake's ability to do business?
 

Keep in mind that the development for X3 took place while Cakewalk was under Roland's watch.
Possibly Cakewalk's reps were quiet because their priorities were set on testing X3?  I don't know.
But I do appreciate how active and responsive they are being now.

These updates are coming pretty fast this time!

MattyBoy

Noel Borthwick [Cakewalk]

MattyBoy
Noel, do you consider the stability issues with having multiple VST with Midi Out a fundamental issue, and will it be addressed in X3c? The release notes for X3b said it had been fixed, but it's till broken... 
 
Stability:

• Resolved a crash when using direct MIDI output with multiple VST Instruments simultaneously, such as multiple instances of JamStix or Catanya (CWBRN-5781, CWBRN-2504, CWBRN-2564, CWBRN-1739)

 

The original crash was definitely addressed - I reproduced and fixed it myself and tested with Jamstix. This is another variant that was not in our system. It probably won't make it into X3C due to time constraints but we'll definitely do our best to address it for the next update since its an important fix. Sorry for the delay but there have been a several lot pressing issues to address before this one.

Thanks for taking the time to respond Noel, it's appreciated, and great news that you'll be looking to address this in the next  update after X3c. I'm sure you've seen the other posts by X3b users that show this is not just restricted to Jamstix / Catanya;  VSTs such as Kirnu Cream, Reaktor etc all cause crashes when Midi out is enabled and there is more than one instance of the VST. Hopefully the fix will address the underlying issue so any VST with Midi Out enabled will work with more than one instance.
 
forum.cakewalk.com/FindPost/2914856
forum.cakewalk.com/FindPost/2912793

This has been a very long standing bug which CW refused to fix for over 4 years. I've reported this back on Feb 24 2009 as CWBRN-1336. Here is the web page I created back then and spent and endless amount of time trying to get CW to address this issue, but they never thought that Sonar being incapable of routing MIDI properly, and crashing when more than one plugin has MIDI Output enabled was important enough to fix.
 
Because of this I've dumped Sonar after just getting fed up with endless empty promises from Noel that it will be fixed in a next release and spending too much of my time and money on this broken functionality that I depended on. And yes, I'm clearly still bitter about this whole issue. I was a loyal customer from the time when the software was still called "CakeWalk" and only had MIDI tracks and no audio tracks. But that bug plus the huge new pile of bugs that came with X1 was just the last straw since I knew CW would need to fix those first so it was just a waste of my time.
 
I just got an email today that CWBRN-1336 has been fixed. Hey it only took 4.5 years! I still have $99 credit with CW so maybe I can use that to try out the latest. I'll only believe that it is fixed if I see it with my own eyes. Then again I don't know if $99 is enough to upgrade from X1 to X3 and if not it's not worth bothering.

You need to fork out another $100 Steven and if you are still running X1 it is a no brainer.

I just got a CWBRN-13970 email today too. This was about a playlist problem that they say was fixed. However I noticed that it was fixed in the first X3 release when I loaded it up. That makes me think that they are behind in getting those emails out. The biggest bummer to me was that I thought it was CWBRN-20634 that they were reporting as fixed. I WAS SO EXCITED! Then I re-read the email and saw it was a much older and already fixed problem.
But since it was old news, maybe they've already fixed the new playlist problem (a MUCH bigger problem) and I just haven't heard about it yet because they are behind on their emails. And maybe they're behind in their emails because they're so busy fixing our requests