I am new to Sonar and using it with a Tascam US-122. When I record or play anything with audio data the cursor starts to move, then stops, either on play or record, and yet the data is recorded OK and plays back OK.
Also, to start or record I have to press the appropriate button or spacebar twice.
When the project contains only midi data there is no problem. The US-122 is working fine and if I use Cubase there is no problem.

Greetings Bill,

Welcome to the forum. One poor question and no replies --- this is so sad I had to bump it.

Regards,
David

What cursor are you referring to? The vertical *now* position that is supposed to move along with playback and recording?

Hello billgjohnson,
Welcome to the forum.

I'm interested in the answer to this problem. It has happened to me a few times as well. I can't seem to cause it on purpose, and it never seems to happen the same way twice.

bounce

Thanks for your replies, guys. Yes, its the vertical "now" cursor. It seems to be some of feedback problem. When you press the spacebar the cursor moves a little, then stops, but the audio plays. When you press the spacebar again it stops. Then when you press the bar again nothing happens at all except that the audio engine briefly runs, then stops. Then when you press the bar again the cursor moves normally and the audio plays. This is roughly what happens, but not necessarily in the same order each time!

If I move the now cursor to, say, bar 4 and press the space bar it either refuses to play or plays from the start.

I have tried re-installing both Sonar and the interface.


Bill Johnson

OK, so it is the now cursor.

My DAW running the last few versions of SONAR has issues with that cursor as well. In my case the now cursor starts to move, and then arbitrarily stops. (no it's NOT the scroll lock key problem) And, as in your case, playback and recording are not impacted. What's really odd in my case is that once it stops moving I can control it using the jog/shuttle wheel on my Radikal SAC-2.2 control surface ... As the song plays back and/or recording is taking place, the entire track view appears disconnnected from the actual playback and the jog/shuttle wheel has full control. This also happens if I power up w/o the control surface, but it just stops moving.

I have also seen the "false start" problem where I have to hi play or record twice, but not in the latest release.

In both cases, I still could make music, so it's only been mildly annoying, not a show stopper. Not too many people have problems like this, so it's got to be related to our system setups.

I'm about to build a new DAW, the first update in about 6 years, and the only part of my old DAW that will move forward is my Dakota/Montana sound card duo, and my DVD writer, so I'm hoping the problem will magically go away.

Sometimes lately when I hit play it's like S5 lags for a little while and then starts to play the tracks but the Now time doesn't move. After a measure, or two it just stops playing anything. I then have to hit stop and the Now time returns to the beginning of the song, even if I started in the middle somewhere. I then hit play again and immediately hit stop and it returns the Now time to the marker at the point it should have stopped at the first time. Then if I hit play it plays normally, but a few times has repeated the problem. It hasn't happened three times in a row though. I hope that makes sense.

Is this similar to what people on this thread have experienced? Does anyone have any idea what is happening, or how to fix it? It isn't crashing SONAR, but it is getting annoying. I have tried several things to troubleshot it and am wondering if it may be a conflict between MIDI devices in SONAR.

I'll venture a guess. When my computer is pushing it's limits it seems like SONAR gives priority to the audio engine and recording and sacrifices screen updates. I had that happen Sunday. The mouse got sluggish and everything looked like it stopped. The AE kept chugging along. When I got finished with the bit, the wavefile appeared. I then checked the Audio options and found that I had lowered the latency to a setting that I know would cause problems. I set it to a higher latency and all returned to normal.

Well, Now that I think of it I am getting these odd spike where the CPU usage jumps. Even with over 30 tracks of MIDI and audio the meter shows less than 20% CPU use, but sometimes it just spikes to 72% for an instant. It could also be related to my mouse... not sure how.. I have a wireless mouse with a rechargable battery that I often forget to put on the charger at night and yesterday it was constantly running out of power when the SONAR problems were happening.

I have 2 computers (DAW and GSampler) sharing one of my monitors through the use of a k/v/m switch that is engaged by pressing the >SCR-Lock> key. Apparently I had occasionally pressed it an odd number of times instead of the double press necessary for changing monitor focus. That was the cause of my now time scroll miss-behavior. Problem solved for me at least.

Thanks Forum!