gcolbert


 

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?

sure... it happens here sometimes and for others too. No real danger, save close restart SONAR and project and it works again.
There are other bugs that are far worse then Time locater.. About RAM I have 16GB + virtual memory give me total 32GB FREE space so I think I'm all set regarding space.
Thanks for your inputs anyway.

chuckebaby

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.

perhaps once or two a week...so not very often. 
In use of SONAR X2 approximately 8-10 hour a day.

Just out of interest, what is the correct definition for a 'bug'?

It seems to me that some of you see a crucial part of such a definition to be that a bug is reproducible.

But I experience a 'bug' with the Now Time Marker that isn't 'reproducible' - even on just my system. It doesn't disappear as some have noted, it just fails to move at all when I hit the transport (in Play and Record); the only way I've found to cure this is to switch to the Console View and back again to the Track View. I can't cause this 'bug' and it happens only intermittently.

So should this be classified as a bug? Or should we maybe refer to it as a 'glitch'?

Or could my system be the cause of the fault? Or maybe I've hit a keyboard shortcut by accident?
 
 
Edit to clarify - when the NTM fails to move, the project still plays or records correctly. And the problem is nothing to do with the Scroll Lock or Pause/Break buttons.

Just out of interest, what is the correct definition for a 'bug'? It seems to me that some of you see a crucial part of such a definition to be that a bug is reproducible.

 
Technically, a bug is something not working as intended.   But to narrow that down even further, that something's root cause is within the application and not as a result of the environment from which the application is run.   (not that making the app more "fault tolerant" is a bad thing)
 
Being able to reproduce an issue is critical, but only that development can reproduce it.  if only one out of a thousand users can reproduce a specific issue, it's sort of irrelevant as long as CW development can too.   Although, that bug may not be real high on the priority list...
 
My views come from 15+ years working for a fairly large software company, where I've heard enough user complaints and descriptions to make that distinction.  However, at the same time if I think a design intent is likely to result in a lot of user complaints, I have no problem reporting that to the development staff (I'm in support).    Yet I know that outright bugs will still come first, with crashes & potential data loss at the top of that list.  Just imagine if everyone had a top three list for CW, yet only the top three of all those lists actually made it through.  What three things would we actually see in the next version?
 
 

Edit: Duplicate post courtesy of IE9.
 

Just out of interest, what is the correct definition for a 'bug'?

A bug is a program response that is different from what the program WAS DESIGNED to do.
 
It does not matter if the design is just simply stupid and the results are insane, if the program was designed to do what it is doing it is not a bug.  For example, if the design is that you click on the track header, then select a clip by typing in the arabic representation for the track name, then typing in the first three letters of the Greek Alphabet it is not a bug when a clip is not selected automatically by simply left clicking on it. 
 

It seems to me that some of you see a crucial part of such a definition to be that a bug is reproducible. But I experience a 'bug' with the Now Time Marker that isn't 'reproducible' - even on just my system.

 
That a 'bug' is not reproducible does not mean that it is not a bug.  It does, however, mean that it can not be fixed by a programmer.  Issues that can not be reproduced can not be corrected.  If a 'bug' of this nature is happening you need to either get used to it or figure out how to reproduce it because it will not go away through any other action.
 

It doesn't disappear as some have noted, it just fails to move at all when I hit the transport (in Play and Record); the only way I've found to cure this is to switch to the Console View and back again to the Track View. I can't cause this 'bug' and it happens only intermittently. So should this be classified as a bug? Or should we maybe refer to it as a 'glitch'?

 
The only time I have observed the NOW TIME marker getting lost was on an underpowered system (Atom 450 notebook) that did not have the graphic horsepower to keep up with the project display.  My hardware meets the "Minimum System Requirements" specified by Cakewalk, which could be the reason I'm not seeing this issue.  On the premise that this is caused by underperforming hardware - would you still consider it a 'bug?'  What if it is running on a system that shares the video IRQ with a 'blue tooth' mouse or a network card that steals the redraw cycles from the graphics processor so that the line is not redrawn?
 

Or could my system be the cause of the fault? Or maybe I've hit a keyboard shortcut by accident?

 
The only way to get to this answer is to determine how to repeat the problem and have others who then follow your steps and encounter the same results.
 

The Now Time Marker...
 
Similar to Freddie H, the frequency which it disappears on me is about a couple of times a week. It's never good to have to stop what I am doing to close down and reopen the project for something like that. Toggling the Inspector (I) seems to restore it for some, but not for me. I reported it to support in January and they knew enough about to ask me to try the "I" trick, and they told me it was being looked at. Based on what I can tell, the likelihood of it happening jumps if you are a PRV user.

I am dealing with other display related issues, and I consider this to be in the same category. All drivers and firmware are up to date (and I have tried previous versions as well), and Sonar X2a is the only application that exhibits this quirky behavior. If anyone has any constructive suggestions I would appreciate you looking at my posts concerning this issue and reply.

Hi Freddy have you done a quick check on the many Cubase's forum???Users are not all very happy I saw it. I'm a pro and my Sonar X2 DAW is very stable and responsive to create my prj and mix and master the client's prjs. For me is the best DAW on the market and my clients begin to choose the Sonar X2 master for it sound more analitic and full,over the other DAW in the studio. Finally, neglecting to mention technical details i think that Cubase is really ugly.It's only my tought.Best

Thanks Steve and Glen for the excellent explanations.
 
 

Timeline: This happened to me all the time before the hot fix. I even reported it. I've not had it happen to me since the hotfix and it has been completely stable since the last update.

Some people complain about it disappearing during editing where your project stops auto-scrolling. Keep in mind that this is by design. Right clicking on your time line will make the project scroll once again. Your project is just pausing here so you can edit without losing your place.

But as far as the TL just disappearing on me completely....not since hot fix. I had a serious problem with this when X2 first came out so I cried like a baby when it was happening to me. Why it still happens to some....I'm not quite sure. But it hasn't happened to me since the initial release thank God.

-Danny