• SONAR
  • Now Time Marker Snaps Back to Zero on Play
2016/11/07 11:39:06
rotund
Now time marker snaps back to zero and will not play tracks unless I click outside of Sonar into by desktop. It is not a micro loop issue as I have investigated that. I have also reloaded my audio drivers and reinstalled Sonar Platinum. I have reviewed all now time settings and snap settings. This first happened with a project that had a lot of effects used however the performance load on the cores was negligible and I have set the load balance option. Therefore, I loaded a project with 1 track and the problem still occurred with all FX disabled.  I have run compatibility checks on my 1394 Card with my Saffire Firewire Pro 14. I have also updated drivers to the latest and also tested rollbacks. My other audio software works fine (e.g. Reason, Audacity, Reaper.) What am I missing or is this a bug? Very strange behavior that I can hit the space bar with Sonar active then click outside of the app and the song will play. Any help is appreciated.  
 
Configuration:
Sonar Platinum 2016.10 (22.10.0.19)
Windows 10pro Intel Core i7-2600k CPU @3.4Ghz 8GB Ram AMD Radeon HD 7700 Series Saffire Pro 14 1394 TI Controller 
2016/11/07 12:41:52
robert_e_bone
Is it possible you have both Sonar and Windows accessing your ASIO drivers for the audio interface?
 
Bob Bone
2016/11/07 14:37:09
rotund
They are disabled. Only audio device is the saffire. The problem is in the now time marker snapping back to zero. If a loop is applied the go time marker will snap back and forth between 0 and the first loop marker. The meters go nuts. The only way to make it stop is click on the desktop outside of Sonar or on Reason if it is rewired to Sonar. 
 
2016/11/07 14:47:57
chuckebaby
you didn't mention if this was working fine before and this just started happening or if this is a new problem.
 
possibly a keyboard / mouse issue ?
are you using a wireless mouse or keyboard ?
 
might be worth unplugging them and trying a test (use another mouse/keyboard).
never heard of this happening before. im just taking a wild guess that a wireless/device conflict of sorts may be happening.
 
I had heard : On Windows 10 there is a known issue at this time with Focusrite Saffire devices connected to a computer that has the VIA chipset on the motherboard or firewire card.  If you do not have the VIA chipset you should be able to run Saffire devices on Win 10 with their latest mix control application
2016/11/07 15:19:31
rotund
Yep keyboard issue. Seems there is a keyboard preset that my keyboard was activating. Pretty old wireless keyboard. Works ok but keys are starting to lose their touch. Hence the problem only with Sonar. Turning off the keyboard identified the problem. Great hunch!. Thanks for the help.
 
2016/11/07 16:14:53
chuckebaby
rotund
Yep keyboard issue. Seems there is a keyboard preset that my keyboard was activating. Pretty old wireless keyboard. Works ok but keys are starting to lose their touch. Hence the problem only with Sonar. Turning off the keyboard identified the problem. Great hunch!. Thanks for the help.
 


good deal man. I have to credit another user (BobF) for this idea. He figured this one out awhile back and I thought it was brilliant because I had been searching for a solution to that users problem for days. I Don't see this often but glad to be a service, always helps when to find the source.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account