Couldn't start audio engine
-
- KVRAF
- 2140 posts since 16 Jan, 2013 from USA
Does anyone else get this message consistently on startup? I get it every time with 5.3.16, but no other DAW has the issue. I can start the audio engine once I'm in MuLab, but sometimes only after several tries. Formerly, this was only when another program was open, but now, even when Mulab is the only program in the foreground. Jo says he hasn't heard any reports on this.
If you have seen this, how did you solve it?
Jon
If you have seen this, how did you solve it?
Jon
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Not seen it here. Have you checked in Task Manager to see if anything has crashed and still has the sound subsystem held open?
-
- KVRian
- 855 posts since 3 Mar, 2009
It's not happening here!
Does this happen when you open a New session or with specific sessions?
Did you copy the App folder from M5.3.14 correctly over the previous version?
Did you copy the Mulab.exe and the Mulab.ID files when istalling M5.3.16?
Does this happen when you open a New session or with specific sessions?
Did you copy the App folder from M5.3.14 correctly over the previous version?
Did you copy the Mulab.exe and the Mulab.ID files when istalling M5.3.16?
-
- KVRAF
- Topic Starter
- 2140 posts since 16 Jan, 2013 from USA
This has been a re-occuring issue over time. As far as I know I copied it correctly. I should mention that I have the. Oh... I see. I have the audio in Mulab set to 96kHz and in Windows it was set to 44.1kHz. Darn it, I've seen that before. Still, it should change this the first time when nothing else is open.
Jon
Jon
-
- KVRAF
- Topic Starter
- 2140 posts since 16 Jan, 2013 from USA
"Recurring". I can of course eliminate the problem by setting the Windows default on my Focusrite 2*4 to 96kHz, but just tried Sonar, Pro Tools, and Studio One with 96kHz projects with the Windows default at 44.1kHz and they all switch smoothly.
Can you guys try the same scenario and let me know if it's just something on my system. Set Windows to 44.1, and Mulab to 96.
Can you guys try the same scenario and let me know if it's just something on my system. Set Windows to 44.1, and Mulab to 96.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I did this:
I set MuLab to 96kHz and exited.
I ran MPC-HC and played a 44.1kHz MP3 - my AudioFire4 FireWire console indicated that the sample rate was 44.1kHz
I ran MuLab, opening an existing project and hit play - my FireWire console indicated that the sample rate was 96kHz
Seemed okay - MPC-HC made a nasty "click" though when it switched sample rate
I set MuLab to 96kHz and exited.
I ran MPC-HC and played a 44.1kHz MP3 - my AudioFire4 FireWire console indicated that the sample rate was 44.1kHz
I ran MuLab, opening an existing project and hit play - my FireWire console indicated that the sample rate was 96kHz
Seemed okay - MPC-HC made a nasty "click" though when it switched sample rate
-
- KVRAF
- Topic Starter
- 2140 posts since 16 Jan, 2013 from USA
Did you have the AudioFire set to default to 44.1 in the Device Manager/Sound?
~Jon
~Jon
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
In Control Panel, Sound - yes, it's set to 44.1kHz. That's also what it boots up as in its FireWire console.
(Note that it is not my default system soundcard -- I use the on-board sound card for system sounds to avoid any applications unexpectedly holding the soundcard open.)
(Note that it is not my default system soundcard -- I use the on-board sound card for system sounds to avoid any applications unexpectedly holding the soundcard open.)
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Heh... so then I start Reaper. I have Reaper set not to request a change to sample rate. It's reporting 96kHz in its status bar, though I have no idea why: FireWire Console still says 44.1kHz. Playback in Reaper then sounds... well, imagine... 
-
- KVRAF
- Topic Starter
- 2140 posts since 16 Jan, 2013 from USA
Ah, in a perfect world. I certainly don't mind keeping stuff at 96. No reason not to in my case. Generally speaking. Thanks for the help.
-
- KVRian
- 855 posts since 3 Mar, 2009
Interesting.
Here Win7 64 bit, RME Fireface UC set to 88.2kHz, Mulab to 88kHz, Win Mediaplayer and MPC-HC play wav files with 44kHz without problem.
All is running through the RME. Seems like the driver is doing all the work.
Here Win7 64 bit, RME Fireface UC set to 88.2kHz, Mulab to 88kHz, Win Mediaplayer and MPC-HC play wav files with 44kHz without problem.
All is running through the RME. Seems like the driver is doing all the work.
-
- KVRAF
- Topic Starter
- 2140 posts since 16 Jan, 2013 from USA
Well, perhaps its something unique about the Focusrite 2*4 driver. No other program has the issue or I'd have started there.
Jon
Jon
