A gut feeling tells me that the DAW _should not_ release the drivers when the application is in the background (at least that's the way it would work in Nuendo or Cubase).
HTH,
/Dietz - Vienna Symphonic Library
194,281 users have contributed to 42,914 threads and 257,948 posts.
In the past 24 hours, we have 2 new thread(s), 18 new post(s) and 90 new user(s).
@cgernaey said:
Well darn that will suck because then I can't do any realtime changing my stage around while my project is playing. Essentially I won't be able to mix and apply eq's etc in realtime then?
Maestro2be
Hmmm ... obviously I miss something essential. Why should this be the case? [:^)]
I am using LoopBe1 between Studio One and MIR.
You didn't miss anything Dietz hehe, you had said in an earlier post that the DAW shouldn't release the drivers in the background and for some reason at the time I read it I interpreted it as "The DAW shouldn't keep playing while in the background" (so was my reading skills letting me down at the moment lol). Which would in fact make mixing in real time impossible :). Now I can see that wasn't what you were saying. So hopefully I can resolve this with Presonus because currently when I click over to MIR, Studio One completely stops playing (more like pauses) and the moment I click it into the foreground it starts playing again.
Maestro2be
Well I got it all working now. Presonus support called me back and told me that logically you would think the option to "release the driver in the background" would be the way to accomplish this but in reality it actually causes the opposite effect. So once I unchecked it everything worked perfectly. They said they are going to rename that option in a future patch to it more clear as they themselves thought that checking it would have been what I wanted to do.
Thanks again for all the help. I can now send/recieve in and out of MIR and Studio One and also mix in real-time in MIR while playing my projects in Studio One.
Maestro2be