• SONAR
  • Getting a bit "hacked off" with the Foxboro update. (p.2)
2015/07/30 09:21:04
PJH
Yes, everything is up to date.
This problem occurs without using any VSTs.
 
As I said, it's only happened since Foxboro.
2015/07/30 09:23:59
Doktor Avalanche
Still do a VST reset after next uodate. Ta.
2015/07/30 09:24:18
Bristol_Jonesey
When you say the tempo doubles, are you saying that you see Tempo Changes written in Tempo View or does what's already recorded simply speed up?
2015/07/30 09:32:38
PJH
The tempo that's already been recorded speeds up.
 
The tempo indicator on the control bar stays the same.
 
Cheers.
2015/07/30 10:09:23
Beagle
are your outputs connected to the 1010 also?  you're not trying to use a different soundcard for output in sonar are you?  if so, you will have mismatch between clocks and that will cause problems like you're describing.
2015/07/30 10:19:55
scook
Consider confirming this is an issue with Foxboro (shark week edition) by rolling back to Everett (or whatever version of new SONAR was running correctly). Rollback is pretty quick if you have the installers cached.
2015/07/30 10:21:09
PJH
No, my setup hasn't changed at all. I'm using the same sound card etc.

The only change that's been made was to upgrade to Foxboro.
2015/07/30 10:22:41
PJH
scook
Consider confirming this is an issue with Foxboro (shark week edition) by rolling back to Everett. Rollback is pretty quick if you have the installers cached.


I'm first going to wait for the new update. If that doesn't work then I'll roll back.

Cheers
2015/07/30 10:28:14
Willy Jones [Cakewalk]
In Edit -> Preferences, under Audio -> Playback and Recording
 
Do you have 'Share Drivers With Other Programs' checked? If so, uncheck it, restart SONAR and try testing again. Your description sounds suspiciously like another application is opening the audio device at a different sample rate.
 
Short of that I'd reach out to support so they can get more information, driver mode setup etc and isolate the issue. We have just about every M-Audio device and tons of hardware synths we could test with as well if they had the lowdown on your configuration.
2015/07/30 11:03:41
John
PJH
Hi John,
 
It's something that I've done a million times. It's nothing new but I've never had this kind of error before.
 
My sequence is basically:
 
1. Solo the midi track
2. Set the inputs on my Delta 1010 for a stereo input.
3. Play the outputs of the JV2080 into the inputs of the 1010.
 
I've been doing this for the past 15 years. Never had a problem until now. It also seems to be an isolated case as I'm not able to reproduce it.
 
I'm not that concerned about the midi problem.
 
The problem of tempos doubling in time is one that does concern me as it's only raised it's head in the Foxboro update and it's something that I can reproduce fairly often. I'm not doing anything different. It's the way I record drums using twelve tracks and the drummer playing to a click.
 
When I playback the tracks, at some point in the song the tempo will just double in time for no apparent reason. When you're paying session musicians for their time it's extremely frustrating to try and troubleshoot the problem.
 
I'm going to wait for the next update to see if it's fixed. If not I'll have to rollback to the previous update.
 
I'm sure that this is connected to the "fast bounce" and the tempo problem that others have discovered.
 
The stupid message was just the last straw for me on a very frustrating session.
 
Cheers,
 
Peter.


Thank you for the complete information. You are doing things the way I would. I will do my best to figure out what is going on but for now I have no quick answer. 
 
Willy Jones is on the case and I would defer to him. 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account