MTRX Studio Mic In's / Dolby Audio Bridge...

[nedd]

Originally Posted by LDS

What is the benefit of having the monitors returning into Pro Tools rather than just returning them to DADman?

My point too, Jeff mention I don't need to change anything in Dadman so I looked at the options within Pro Tools but would be much more convenient if the return from DAPS goes, just like HDX, directly to my speakers and HP's.

It does works nicely and was able to monitor thru speakers, BIN Dolby Renderer and Logic with Apple renderer (and dolby renderer) on AirPods. Also listening from Assembler thru Logic works the same way. But without Pro Tools, only on AirPods or 7.1.4 from logic thru DVS on speakers.

[Dizaineris]

Originally Posted by creativecontrol

AUX IO in Pro Tools 2022.9 - in combination with DAPS, Bridge and HDX:

https://youtu.be/ZdM3HsHuozQ



Jeff

Hi Jeff,

I'm using this exact setup on my system.

https://youtu.be/ZdM3HsHuozQ


I'm working in Post.
Sync feels a little soft with picture.

Is this the delay compensation that can't be avoided by using the Pro Tools Audio Bridge.


Also, I use the numeric keypad in shuttle mode
Slight lag from scrub to actual playback of audio.



If I go back to old way,

PT playback engine set to Dolby Audio Bridge
DAPS output set to HDX

Playback is tight again. Scrub tight as well.


Would be interesting if Pro Tools Audio Bridge could be accessed directly from MTRX Studio- Monitor Profile.
Instead of having to bring it back in to PT.



Mac Studio Ultra 128RAM, HDX Thunderbolt, PT2022.9, MTRX Studio, DVS

[creativecontrol]

Just like Dolby Audio Bridge, Pro Tools Audio Bridge is a Virtual Coreaudio Device. The Monitor Profile of MTRX or MTRX Studio can only leverage the populated IO that is available to the crosspoint matrix - and (if you have multiple MTRX devices) the unit assigned to ProMon.


Jeff

[Dizaineris]

Originally Posted by creativecontrol

Just like Dolby Audio Bridge, Pro Tools Audio Bridge is a Virtual Coreaudio Device. The Monitor Profile of MTRX or MTRX Studio can only leverage the populated IO that is available to the crosspoint matrix - and (if you have multiple MTRX devices) the unit assigned to ProMon.


Jeff

I guess I was hoping it could be like Dante Virtual Sound Card.
But makes sense.

Thanks for answering

[originalscottyg]

Originally Posted by Dizaineris

Sync feels a little soft with picture.
...
If I go back to old way,

PT playback engine set to Dolby Audio Bridge
DAPS output set to HDX

Playback is tight again.

In the very limited testing I've done so far, I feel the same way about sync to picture.

[Reckless Erik]

Tested the setup suggested without returning re-renders into ProTools. Routed the output of the Dolby Atmos renderer to Dante instead and found that there is a sizeable delay between the output of the HD Native Thunderbolt/MTRX Studio and Dante. Is this due to the inherent delay in Dante or something else?

[LukeHoward]

Originally Posted by Reckless Erik

Tested the setup suggested without returning re-renders into ProTools. Routed the output of the Dolby Atmos renderer to Dante instead and found that there is a sizeable delay between the output of the HD Native Thunderbolt/MTRX Studio and Dante. Is this due to the inherent delay in Dante or something else?

I'm impressed you got this to work at all, it didn't work for me. Are you using DVS? That has a fair bit of latency, even at the lowest settings.

[Reckless Erik]

Hi Luke,
Yes DVS. Actually worked from the get go!
If you want my setup just drop me a line.

[LDS]

Originally Posted by LukeHoward

I'm impressed you got this to work at all, it didn't work for me. Are you using DVS? That has a fair bit of latency, even at the lowest settings.

It is working fine here too. The renderer just required some liberal restarting when messing with I/O settings to kick it back into life.


Loopback tests seem relatively easy now that Pro Tools has Aux I/O. At 1024 sample buffers and 48kHz, I am getting the following:

HDN + RME Madi - 56.3ms
HDN + DVS - 62.6ms
HDN + RME Madi + PTAB return to Pro Tools - 72.4ms
DAB + MADI -> HDN - 80ms
HDN + DVS -> PTAB return to Pro Tools - 87.8ms
DAB + DVS -> HDN - 99.5ms
DAB + PTAB return to Pro Tools - 119.8ms

Adding DVS to a previous DAB in/HDN out renderer setup will add a little bit of latency, but it is very little compared to DAB or PTAB are bring to the party.

[Dizaineris]

Originally Posted by LDS

It is working fine here too. The renderer just required some liberal restarting when messing with I/O settings to kick it back into life.


Loopback tests seem relatively easy now that Pro Tools has Aux I/O. At 1024 sample buffers and 48kHz, I am getting the following:

HDN + RME Madi - 56.3ms
HDN + DVS - 62.6ms
HDN + RME Madi + PTAB return to Pro Tools - 72.4ms
DAB + MADI -> HDN - 80ms
HDN + DVS -> PTAB return to Pro Tools - 87.8ms
DAB + DVS -> HDN - 99.5ms
DAB + PTAB return to Pro Tools - 119.8ms

Adding DVS to a previous DAB in/HDN out renderer setup will add a little bit of latency, but it is very little compared to DAB or PTAB are bring to the party.

Thanks for posting these results.
Very helpful!