Beepster

ampfixer
Come on Beeps, it's Christmas. Why not give the benefit of the doubt. Willy does come up with actual issues when doing his work and should bring those issues into the light. We may all benefit from his discoveries one day. 

I do not deny he does stumble across some legit issues in his travels. I've confirmed a few of them myself. I just think his approach is rather supect, combative and dishonest.
 
This is why I consider him a "dredger". He scours the program for any tiny little thing that COULD be construed as undesirable behavior then blows it up to be a massive, work impeding "b*g".
 
Often times he simply is making mistakes in procedure or logic or not understanding how the program works.
 
When he DOES discover an actual bug trying to get reproduceable steps from him or even a proper description of the issue is like pulling teeth. He then refuses to report it (usually), slags Sonar (usually) and forum members (often times) and acts like he's "helping".
 
I have however rarely seen him extend a helping hand to another user and the few times it seems like he is it is usually attached to some kind of dig at Sonar or other users.
 
It should also be noted that although I am not a Xtian and don't really observe Xmas I am not a heartless scrooge so Happy Christmas ya'll... even Willie...
 
but it's only the 19th.... lulz.
 
Peace.

Getting really old now beeps. Why don't you learn to leave it alone.

Paul P
I (really) appreciate your independance towards Cakewalk, but if something is possible, some poor soul will stumble upon it and spend a weekend wondering what the heck is going on.  So whether or not a situation is unlikely or dumb, a producer must strive to eliminate the possibility.  And really, no action performed by a user can be considered dumb since you have to be experienced to know if it was dumb or not.

 
Well, I think that my using SONAR without having it hooked into an interface was pretty dumb...I just can't imagine someone wanting to work in SONAR and not expect to hear what's going on. So I assume someone's first concern if they're not hearing any audio would be "why am I not hearing audio?" Once that was solved, the issue of a groove clip that renders incorrectly when SONAR doesn't see an audio interface would no longer exist.
 
Which brings up the question of why I even encountered this issue...I use my laptop with an ASIO interface at the office, but often answer forum questions away from my studio or the office, so it's just the internal sound card. I'll boot up SONAR to answer a question and take a screen shot or whatever, but don't bother to reset the preferences.
 
That said, Noel did consider it a bug, but I would hope that it lives waaaaaaaaay down in the list of priorities. I don't think a common use of SONAR is to take screen shots from a program that can't function in order to answer forum questions.  However, who knows...maybe it's a data point that will come in handy when fixing some other bug that does matter, which is why I reported it. But in general, I think "bugs" due to pilot error should take a back seat to bugs due to program errors.

williamcopper
A simple observation --- in an ordinary, but full, project, an accidental assignment of now time way past the end of the project cause odd behaviour --- a good long time (many seconds) to recover normal behaviour.     Yes, pushing play will go back to the beginning, yes, so will using the rewind shortcut, but neither work as expected and as normal playback had been working before the accidental now time assignment.  
 
Please don't try to criticize it, misdirect it, or minimize it.  Just let it stand as a user's observation, for what it's worth.

I still don't understand what happens ...

I saw a very slight delay - maybe 2-3 seconds at the most - before the project rewound and started playback. Possibly the delay gets longer with greater project complexity or other factors.