gcolbert

This forum is a great place to help users in handling 95% of these things that are somehow considered to be 'bugs' by users who don't know any better than to call them that.  Look, unless someone else can reproduce what someone thinks is a 'bug' it probably isn't.  If someone else can't make it happen it is probably something that YOU are doing wrong - not Cakewalk.

Not all bugs are reproducable and some are very elusive, e.g. the disappearing Now Time indicator.  This is still a bug though and needs to be fixed.

ugp


 you know, I went over to the Studio One forum and their complaining about how come it's taking so long for a patch to fix their bugs... Go figure

Similar things are posted in the Samplitude forum, as well.  

Not all bugs are reproducable and some are very elusive, e.g. the disappearing Now Time indicator. This is still a bug though and needs to be fixed.

 
No argument here mate.  I'm not claiming that there aren't bugs, just not nearly as many as some of the folks on this forum want to make out. 
 
First, if something is working as it shows in the manual, it is not a bug.  The vast majority of the problems that people post in this forum really do resolve to RTFM (read the friggin manual) issues.  If someone can show that the manual says to do A, B, and C, and the result will be D, and a user follows those steps and does not get to D, then there is a bug.  When a user expects to get E as a result because that is how it worked in version 6, then this is not a bug.
 
The problem with bugs not being reproducible is that no programmer can fix a problem that can not be recreated.  I've been trying to recreate a bug in the Console View that causes a hard crash for several weeks now.  I could not get it to happen on my system.  One day (the planets aligned and the moon was in the right phase) I was able to make it happen dependably on my system.  At least a dozen of the (in my opinion) most knowledgeable users on this forum tried to replicate the problem following my steps and were not able to.
 
I do believe in bugs.
 
Even with this issue, X2a still works for me.  I just have to use the workaround of not displaying the Pro Channel in the Inspector View while I am using the Console View.  I am absolutely confident that once I can show what is causing the problem that 'The Bakers' will fix it.  I have a list of other bugs that I have pinned down that they have fixed.  The Bakers are actually pretty good to work with if you can get them to the cause of a problem.
 
Glen

Kev999

gcolbert

This forum is a great place to help users in handling 95% of these things that are somehow considered to be 'bugs' by users who don't know any better than to call them that.  Look, unless someone else can reproduce what someone thinks is a 'bug' it probably isn't.  If someone else can't make it happen it is probably something that YOU are doing wrong - not Cakewalk.

Not all bugs are reproducable and some are very elusive, e.g. the disappearing Now Time indicator.  This is still a bug though and needs to be fixed.

No not a bug! Not according to some people here and all the other hand full bugs making even "pop up" crash message.
Its embedded new features in X2. 
 
 
You just haven't read the manual hard enough or read it proper.
Or you just thought the "feature" were implemented in other way, not to disappear randomly.
 
 
As and example : Cakewalk has supposed to coded and program the "NOW TIME" indicator to randomly disappears in SONAR X2. It much more fun to guess were you play in the project instead of visible see it. 
 
Also CRTL + Z = undo should give you a crash message during arrangement/ moving large quantities of moved clips. 
According to some here, the crash message and close the program in one go is a "feature" implemented in another way you expected it to be. Don't you get it? CTRL+ Z ---->are not Undo. Its = Crash and then end/close the projects with a error message.
 
Thanks cakewalk for that feature. I can't wait for X3.
 
    

LOL Thanks Freddie H

John


Its called Play List and is used to automatically load projects one after another for playback.

holy swift, ive never even heard of this, I feel like a noob / knob.  :)
 
thanks john

Freddie H


X2 A-Update--> 2012-18-12...2013-05-27 and still no new B update?
There are no excuse that we need to sit and wait for a simple  "fix - problems" update so long. I use SONAR X2 in m daily job, a tool for me making music and productions. X2a okay stable but all other DAWs are that too like Cubase, Logic, Samplitude. I wouldn't expect less from a professional DAW program... or isn't SONAR X2 that? 
 
Still I have found "bugs" /problems still no one seem to care to fix them at Cakewalk? Cakewalk use to be fast on sending out update not slooooooooooowwwwwww as today. I really like that. Also they use to add new things, listing on the customers. I will soon leave this boat if this pattern continue.
 
 
 
Best regards
Freddie
 

NO! I will not buy X3 I have had it.


I'm looking and thinking of going back to Cubase 7 that has features like stability, VST3 + audio features, fantastic new mixer view use of large project, ICONS, METER, FREE COLOR of TASTE of the program GUI, Control Room, batch, Score notation, video-engine, and support of professional hardware control like EUCON, SSL, Yamaha right out of the box.


I love SONAR GUI and Pro channel but the last year its not the same Cakewalk anymore. No color option, no VST3, no listen on customer, fire key members of Cakewalk organization, it seem more less Cakewalk ending their business? 
 
 
Perhaps they aiming to make programs to beginners / toys and "first time" amature segment obviously not the professional user. 
They seem more interested of putting all effort making Music creator 6, download with Steam when you download your other games... instead of making a update patch B for the professional users..

 

As and example : Cakewalk has supposed to coded and program the "NOW TIME" indicator to randomly disappears in SONAR X2. It much more fun to guess were you play in the project instead of visible see it.

 
Freddie, I have never had my NOW TIME indicator randomly disappear.  If you can show me how to make that happen (and it is documented in the user manual that it should not be hidden as a result of some user action) I am more than willing to key in a bug report for the problem.  Fact is, it just does not happen with my setup.  Now it may just be that you are accidentally hitting the scroll lock or some other keyboard short-cut that makes it go away.  If this is the case the bug is on the other side of the keyboard. 
 

Also CRTL + Z = undo should give you a crash message during arrangement/ moving large quantities of moved clips. According to some here, the crash message and close the program in one go is a "feature" implemented in another way you expected it to be. Don't you get it? CTRL+ Z ---->are not Undo. Its = Crash and then end/close the projects with a error message. Thanks cakewalk for that feature. I can't wait for X3.

 
As to control-Z causing a crash, I would bet that if you were to look at your system event logger you just might find that you ran out of memory trying to execute the undo.  Cakewalk is not responsible for how much memory you have in your system.  Running out of memory is not a feature but it is more like running out of gas in your car.  Probably not a design flaw at Ford.  Would it make your situation any better if you got a pop-up that said "buy more memory" before X2 crashed on you?

rcklln


LOL Thanks Freddie H

Yes LOL...  sad but true..

Freddie H

Kev999

gcolbert

This forum is a great place to help users in handling 95% of these things that are somehow considered to be 'bugs' by users who don't know any better than to call them that.  Look, unless someone else can reproduce what someone thinks is a 'bug' it probably isn't.  If someone else can't make it happen it is probably something that YOU are doing wrong - not Cakewalk.

Not all bugs are reproducable and some are very elusive, e.g. the disappearing Now Time indicator.  This is still a bug though and needs to be fixed.

No not a bug! Not according to some people here and all the other hand full bugs making even "pop up" crash message.
Its embedded new features in X2. 
 
 
You just haven't read the manual hard enough or read it proper.
Or you just thought the "feature" were implemented in other way, not to disappear randomly.
 
 
As and example : Cakewalk has supposed to coded and program the "NOW TIME" indicator to randomly disappears in SONAR X2. It much more fun to guess were you play in the project instead of visible see it. 
 
Also CRTL + Z = undo should give you a crash message during arrangement/ moving large quantities of moved clips. 
According to some here, the crash message and close the program in one go is a "feature" implemented in another way you expected it to be. Don't you get it? CTRL+ Z ---->are not Undo. Its = Crash and then end/close the projects with a error message.
 
Thanks cakewalk for that feature. I can't wait for X3.
 
    

its strange, I have never had my nowtime disappear.
ive heard a couple people here say it has, but its not happen to me.
how often does that happen ?
does cont+z happen a lot as well ?
 
no disrespect in anyway freddy, just curious buddy.