• SONAR
  • Focusrite Saffire Pro User Mix control 3.4 does not start audio engine by default (p.2)
2014/07/15 15:11:43
Splat
LunaTech
Hi Alex,
 
Question.... Does it do the same thing if the initial track inserted is not a midi or an instrument track? thx



Yes reproducible with an audio track as well... Thanks...
2014/07/15 16:36:05
bitflipper
I use a Saffire Pro 40 (driver version 4.1.4.18046, dated 1/16/2014) and Mix Control 3.41b. I have not seen this behavior.
 
I doubt it has anything to do with the Mix Control application, which does not come into play until you explicitly invoke it. I suspect it could even be uninstalled and the audio interface would still function, just without the convenience of a software UI. It certainly has nothing to do with starting or stopping the audio engine.
 
The engine will shut off automatically if for some reason it can't fill the audio buffers for 250 milliseconds. For example, a background process that won't let go of the audio subsystem or an interrupt handler that won't allow Firewire interrupts to be serviced. That might be an angle to explore.
2014/07/15 17:28:20
Splat
I tried higher firewire latency and ASIO buffer no dice.

Dave I think you are running an old Mix Control 3.4 beta version.
Mine is 3.4 (no other numbers after it) and the firewire driver is 4.1.4.18150. Firmware is 2761.
If you upgrade please let me know :).
 
I'll take note of the points made thanks.
Cheers...
2014/07/15 18:57:22
ptheisen
Hi Alex,
 
My specs related to OS, Sonar, interface, firmware, driver and Mix Control are identical to your signature except that I am on Windows 8.1, not 8.1.1. I tried to reproduce the issue following your steps and could not, it works as expected here. That might not be what you are hoping to hear, but maybe it indicates that the issue is related to a somewhat uncommon combination of factors. Hope you can get it sorted out soon.
2014/07/15 20:07:54
Splat
Thanks...
 
Well this was experienced on my old Windows 7 OS and now on Windows 8.1.1 (recently rebuilt from scratch).
So now I've got to think what was the common factor between both of them, the only think I can think of right now is antivirus which somehow seems unlikely... but I'll check.. Oh and I do have another ASIO card. Cheers...
2014/07/16 10:17:56
Wookiee
Another thought though as David say this may or may not matter are you running the Firewire interface in legacy mode as recommended by Focusrite. 
2014/07/16 10:53:11
Splat
Earlier versions recommended the legacy driver, but Focusrite do not recommend legacy mode with Saffire Mix Control 3.4. I am running a chipset as recommended by Focusrite.
 
Cheers..
2014/07/17 05:24:46
Wookiee
CakeAlexS
Earlier versions recommended the legacy driver, but Focusrite do not recommend legacy mode with Saffire Mix Control 3.4. I am running a chipset as recommended by Focusrite.
 
Cheers..


OK I could not find that on the Focusrite page but will admit that I did not look that hard.
2014/07/17 12:30:03
Splat
Wookiee
CakeAlexS
Earlier versions recommended the legacy driver, but Focusrite do not recommend legacy mode with Saffire Mix Control 3.4. I am running a chipset as recommended by Focusrite.
 
Cheers..


OK I could not find that on the Focusrite page but will admit that I did not look that hard.


Check here:

http://global.focusrite.c...patible-with-windows-7

Ta
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account