Can I use one audio interface with 2 DAW opened at the same time?

[Rockman413]

Hi there,
I know on PC/Windows, we can only use 1 DAW at one time with 1 audio interface.
But it seems on Mac, I can use Pro Tools + another DAWs at the same time, and as long as my sample rate/ settings or project are the same it appears to be working fine. But I want to know what issue this may cause?

[JFreak]

First issue would be CoreAudio driver, in which case if one of your DAW's is PT it requires exclusive access.

[Rockman413]

Originally Posted by JFreak

First issue would be CoreAudio driver, in which case if one of your DAW's is PT it requires exclusive access.

I don't think this is true as well, as I have successfully Run PT and DP at the same time, it seems PT is not requiring exclusive access, unless I'm not understanding you correctly?

[JFreak]

Originally Posted by Rockman413

I don't think this is true as well, as I have successfully Run PT and DP at the same time, it seems PT is not requiring exclusive access, unless I'm not understanding you correctly?

Umm, I only have experience of HD drivers but they do require exclusive access

[Rich Breen]

Originally Posted by JFreak

First issue would be CoreAudio driver, in which case if one of your DAW's is PT it requires exclusive access.

This assumes they're using HD interfaces in which case the CA driver does require exclusive access. If they're not using an HD interface it's not a problem. Personally, I feed a Metric Halo ULN8 for monitor control with AES from the HD interfaces - that gives me CA access into my monitor chain and I can run multiple DAWs/editors simultaneously and do it all the time - aside from the obvious (running RX/etc) alongside Pro Tools, I frequently need to move between Logic and Pro Tools for session prep/interchange - this all works smoothly here assuming sample rates are the same.

[TrackerLe]

HDX and HD Native only works with one DAW or Audio Application. Other Audio Interfaces, who can use multiclients can use more Applications in the same time...

[Eric Lambert]

I understand the concept (and perhaps even the need) for the exclusivity limitation in HD, but this has been such a crutch for us multi-DAW users over the years. Closing PT to open Logic is a relatively quick process, and thankfully Logic plays nicely with Avid hardware making it possible in the first place. However, asynchronous use, when sharing between DAWs is necessary, blocks us from that option. Premium upgrades, like HD, typically unlock functionality -- here it creates limits.

[JFreak]

Yes, but it is not necessarily important to have HD driver to share i/o between PT and LX because you can sync them together and have LX playback your MIDI while PT has all the i/o for itself. How often you record on two DAW at the same time? This is not my usual workflow but have done it couple of times just for the sake of it. MTC is needed and some hassle, but was happy for what I got.

[lesbrunn]

Originally Posted by Rich Breen

This assumes they're using HD interfaces in which case the CA driver does require exclusive access. If they're not using an HD interface it's not a problem. Personally, I feed a Metric Halo ULN8 for monitor control with AES from the HD interfaces - that gives me CA access into my monitor chain and I can run multiple DAWs/editors simultaneously and do it all the time - aside from the obvious (running RX/etc) alongside Pro Tools, I frequently need to move between Logic and Pro Tools for session prep/interchange - this all works smoothly here assuming sample rates are the same.

That's really nice! But I guess Windows users will just have to dream on... I wish an innovative developer would find a workaround for Windows. I know it's possible, in spite of the present limitations. Almost everything is possible if there's enough motivation to make it so.

[deanrichard]

This does not require an innovative developer, it requires Avid to step up. As I mentioned in a previous post, other Windows apps work fine when sharing an audio interface. It shouldn't be hard, nearly everyone else does it. Something about wanting "exclusive access" to the audio device.

Originally Posted by lesbrunn

That's really nice! But I guess Windows users will just have to dream on... I wish an innovative developer would find a workaround for Windows. I know it's possible, in spite of the present limitations. Almost everything is possible if there's enough motivation to make it so.