FWIW, I am managing to successfully open up older projects in X3 and continuing to develop them, so this is not a common issue.
 
 

lawp
i believe we need what is commonly referred to as a "known issues list"...

ideally, yes, but we'll never get an official up-to-date one (I reckon that's quite adverse for marketing to have something like that online) ...
 
so, here's the place to start the inoffical one ;-)

Use the TSE 808 or any of the LePou amp sim plugins and you'll likely destabilise X3c and it'll stop responding or motorboat like crazy.  Shame, I really like those plugs.
 
Another example would be Image Line's Parametric EQ 2.  This crashes less frequently but it still happens on occasion.  This particular plugin also exhibits a strange 'black GUI' bug; if this bug occurs then it's a guaranteed crash if you try to load another instance in that session. 
 
That's being somewhat specific; in a more general sense the only thing I've seen crash it thus far are plugins which it can't play nicely with.  I am not wise enough to say whether the issue lies with the plugins or with Sonar.

Bristol_Jonesey
FWIW, I am managing to successfully open up older projects in X3 and continuing to develop them, so this is not a common issue.  

Do you use track folders and are their sizes (heights) minimized and saved with a screenset? What happens when you open the project or switch screensets? Do you still see the folder size minimized? My projects created in X2a (with a project template in X2a) show folders in double-row height, while it doesn't happen in a project created in X3.

Jlien X

Bristol_Jonesey
FWIW, I am managing to successfully open up older projects in X3 and continuing to develop them, so this is not a common issue.  

Do you use track folders and are their sizes (heights) minimized and saved with a screenset? What happens when you open the project or switch screensets? Do you still see the folder size minimized? My projects created in X2a (with a project template in X2a) show folders in double-row height, while it doesn't happen in a project created in X3.

Yes, I use minimized Track folders and always in a saved/locked screenset and they open as they should do.
 
I do see some strange graphics weirdness from time to time, so it's not completely bulletproof.

Bristol_Jonesey

Jlien X

Bristol_Jonesey
FWIW, I am managing to successfully open up older projects in X3 and continuing to develop them, so this is not a common issue.  

Do you use track folders and are their sizes (heights) minimized and saved with a screenset? What happens when you open the project or switch screensets? Do you still see the folder size minimized? My projects created in X2a (with a project template in X2a) show folders in double-row height, while it doesn't happen in a project created in X3.

Yes, I use minimized Track folders and always in a saved/locked screenset and they open as they should do.
 
I do see some strange graphics weirdness from time to time, so it's not completely bulletproof.

 
Hmm...strange, it doesn't work properly like that here (even though the screenset is locked with folders minimized). Also, Ctrl+DownArrow key doesn't do the vertical zoom right in some older projects. For example, when the current track is #10, Ctrl+DownArrow is supposed to show #10 (in the maximized size) eventually, but what it actually does is zoom #7 instead. I'm thinking these weird behaviors depend on the project template you use and how you customized it in X2. I only use just one heavily customized template (created with the default "blank" template), and I'm planning to rebuild it from scratch in X3, but after X3d is released (when will we see it?)

SilkTone

CakeAlexS

SilkTone
Don't have more than one VSTi at a time sending MIDI events out with the "Enable MIDI Output" turned on.
 
!!Crash!!

Has this been reported to Sonar with specific steps to reproduce?
http://www.cakewalk.com/s...act/problemreport.aspx
 
Thanks.

Yes, as CWBRN-2504 on 03/22/2010. We are now at CWBRN-22142, so that means there have been almost 20,000 reports since then. And yet to this day Sonar still can't route its way out of a paper bag.

FWIW, the VAST majority of that count are not bugs. Most are things like "where is my serial number?". Someone can also send the same crash through the fault reporter 50 times and bump that count. I wouldn't pay so much attention to the number. It doesn't really tell you much out of context.

Ryan Munnis [Cakewalk]

SilkTone

CakeAlexS

SilkTone
Don't have more than one VSTi at a time sending MIDI events out with the "Enable MIDI Output" turned on.
 
!!Crash!!

Has this been reported to Sonar with specific steps to reproduce?
http://www.cakewalk.com/s...act/problemreport.aspx
 
Thanks.

Yes, as CWBRN-2504 on 03/22/2010. We are now at CWBRN-22142, so that means there have been almost 20,000 reports since then. And yet to this day Sonar still can't route its way out of a paper bag.

FWIW, the VAST majority of that count are not bugs. Most are things like "where is my serial number?". Someone can also send the same crash through the fault reporter 50 times and bump that count. I wouldn't pay so much attention to the number. It doesn't really tell you much out of context.

Says the person that erroneously closed CWBRN-2504 while this bug still isn't fixed. But hey man, whatever excuse works for you guys, as long as it doesn't involve actually fixing the bug.
 
And note I didn't say 20,000 bugs, I said 20,000 reports. No matter how you slice that, it is an embarrassing number when you look at this issue. I'm not sure what excuse CW can use to justify not fixing such a fundamental MIDI routing/crashing bug that has been brought to your attention many many years ago. Well I guess closing the bug reports as "fixed" might just make it go away I suppose.

SilkTone

Ryan Munnis [Cakewalk]

SilkTone

CakeAlexS

SilkTone
Don't have more than one VSTi at a time sending MIDI events out with the "Enable MIDI Output" turned on.
 
!!Crash!!

Has this been reported to Sonar with specific steps to reproduce?
http://www.cakewalk.com/s...act/problemreport.aspx
 
Thanks.

Yes, as CWBRN-2504 on 03/22/2010. We are now at CWBRN-22142, so that means there have been almost 20,000 reports since then. And yet to this day Sonar still can't route its way out of a paper bag.

FWIW, the VAST majority of that count are not bugs. Most are things like "where is my serial number?". Someone can also send the same crash through the fault reporter 50 times and bump that count. I wouldn't pay so much attention to the number. It doesn't really tell you much out of context.

Says the person that erroneously closed CWBRN-2504 while this bug still isn't fixed. But hey man, whatever excuse works for you guys, as long as it doesn't involve actually fixing the bug.
 
And note I didn't say 20,000 bugs, I said 20,000 reports. No matter how you slice that, it is an embarrassing number when you look at this issue. I'm not sure what excuse CW can use to justify not fixing such a fundamental MIDI routing/crashing bug that has been brought to your attention many many years ago. Well I guess closing the bug reports as "fixed" might just make it go away I suppose.

SilkTone, I explained to you in depth multiple times why that report was closed. Continuously calling me out with false information and spreading rumors is just ridiculous. You're ignoring everything I've explained to you in depth. You're misquoting myself and other Cakewalk staff. I personally logged your new CWBRN with internal details yesterday. You are quite literally arguing with the person trying to help you here.
 
Please stop spreading false information.

so have the individual bugs documented on his web page been re-submitted as individual cases/reports by anyone? that would seem to be the best way forward?