Can HDX & HD Native coexist?

[LDS]

Obviously they don't work as one single system, but is it possible to have a HDX and HD native thunderbolt interface attached/installed in the same computer without the whole thing flipping out?

[mixgate]

yep but you can only have ONE driver assigned at a time to pro tools and you would need to have DIFFERENT interfaces connected to BOTH

[LDS]

Originally Posted by mixgate

yep but you can only have ONE driver assigned at a time to pro tools and you would need to have DIFFERENT interfaces connected to BOTH

Turns out to be a bit of a dud for what I was hoping to use it for - running HDX in Pro Tools and using HD Native for core audio applications. Both HDX and HD Native appear as hardware options in Pro Tools, but the core audio aspect of the HD driver must only allow one of them to exist as an audio interface under OSX.

[LukeHoward]

Originally Posted by LDS

Turns out to be a bit of a dud for what I was hoping to use it for - running HDX in Pro Tools and using HD Native for core audio applications. Both HDX and HD Native appear as hardware options in Pro Tools, but the core audio aspect of the HD driver must only allow one of them to exist as an audio interface under OSX.

Man, you must be reading my mind – I had exactly this thought today, as I have a spare HD Native interface hanging around and I was thinking, it could be nice to use it for CoreAudio (notwithstanding the fact that it's probably equally problematic with Ableton as HDX is, and it'd mean giving up a port on the MTRX).

Still, I'm impressed the system actually boots with both connected

[LDS]

It seemed like a good idea in theory! The more I dig into though, the more it just isn't working. Even in Pro Tools, having both installed is proving to be problematic. Switching between HDX and HDN causes Pro Tools crash, more often than not.

It's a bit frustrating. There is no real intermediate solution for what I want to do. The current implementation of the Dolby Atmos production suite and Pro Tools means I either need to throw HDX aside entirely... or spend thousands upon thousands of dollars adding Madi or Dante connectivity simply to get audio from one software application into another.

Makes me wonder if there isn't a market for a simple mini-Digilink to USB3 or TB3 coreaudio interface. No frills. No digital or analogue I/O. It just appears as something like a HD Madi interface in Pro Tools at one end, and bridges it to a solid 64channel core audio interface at the other. Done, and probably for a fraction of the cost of what Dante and Madi solutions do it for.

[LukeHoward]

Originally Posted by LDS

It seemed like a good idea in theory! The more I dig into though, the more it just isn't working. Even in Pro Tools, having both installed is proving to be problematic. Switching between HDX and HDN causes Pro Tools crash, more often than not.

Well, I can make Pro Tools crash without doing that

It's a bit frustrating. There is no real intermediate solution for what I want to do. The current implementation of the Dolby Atmos production suite and Pro Tools means I either need to throw HDX aside entirely... or spend thousands upon thousands of dollars adding Madi or Dante connectivity simply to get audio from one software application into another.

I don't know much about Atmos, but isn't there an alternative plugin based workflow (albeit one that has delay compensation issues)?

Makes me wonder if there isn't a market for a simple mini-Digilink to USB3 or TB3 coreaudio interface. No frills. No digital or analogue I/O. It just appears as something like a HD Madi interface in Pro Tools at one end, and bridges it to a solid 64channel core audio interface at the other. Done, and probably for a fraction of the cost of what Dante and Madi solutions do it for.

Yeah, I was thinking that. Or (this probably doesn't help you), a TB card for the MTRX. The cheapest approach for me would be to get a USB to MADI interface (MOTU M64 appears to be the cheapest). Given what MTRX cards are priced at even if there were a TB card for the MTRX, it would still probably be the better option!

[LDS]

Originally Posted by LukeHoward

Well, I can make Pro Tools crash without doing that

I don't know much about Atmos, but isn't there an alternative plugin based workflow (albeit one that has delay compensation issues)?

Yeah, I was thinking that. Or (this probably doesn't help you), a TB card for the MTRX. The cheapest approach for me would be to get a USB to MADI interface (MOTU M64 appears to be the cheapest). Given what MTRX cards are priced at even if there were a TB card for the MTRX, it would still probably be the better option!

The plugin based workflow is a bit of a nightmare to use, and it busts ADC too. At least with the Dolby Atmos audio bridge it is possible to print a variety of standard 2.0, 5.1 and 7.1 masters using the production suite. It just sucks up the juice on in my system, hence wanting to use HDX for the additional DSP.

[LukeHoward]

Originally Posted by LDS

The plugin based workflow is a bit of a nightmare to use, and it busts ADC too. At least with the Dolby Atmos audio bridge it is possible to print a variety of standard 2.0, 5.1 and 7.1 masters using the production suite. It just sucks up the juice on in my system, hence wanting to use HDX for the additional DSP.

Completely outside my area but very interesting. What's the solution, a MADI interface for Pro Tools into another MADI CoreAudio interface that Dolby talks to?


(By solution, I mean something that would solve it today, not an ideal one that doesn't exist yet)

[LDS]

Yeah, I think MADI is probably one of the easier options. Though interestingly, I think something like an Antelope Orion 32 HD can pipe 64 channels between digilink and USB without much fuss. It really rolls everything into one unit... if the drivers work.

[LukeHoward]

Originally Posted by LDS

Yeah, I think MADI is probably one of the easier options. Though interestingly, I think something like an Antelope Orion 32 HD can pipe 64 channels between digilink and USB without much fuss. It really rolls everything into one unit... if the drivers work.

I just found a MOTU M64 on eBay (USB to MADI, AVB) for US$375. That's gonna be your cheapest solution! RME better, obviously, but at a cost.