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

[creativecontrol]

You need to change nothing in your DADman monitor profile.

For your setup you should create a 2x INPUT paths in IO Setup which leverage AUX IO from Pro Tools Audio Bridge 32:

Speakers_9 = 7.1.2 path, to accommodate the 9 floor speaker channels + LFE
Speakers_Z = QUAD path, to accommodate the 4 height speaker channels

Outputs - same as above - but feeding out the MTRX / DigiLink outputs (to DADman) channels 1-14.

Yes, you will be able to do Speakers, Dolby Binaural and Apple Spatial all at the same time. Use a 7.1.4 Re-Render as shown in the screen grab to feed into Logic.

DAPS Input = Dolby Audio Bridge
DAPS Output = Pro Tools Audio Bridge 32
PT Output = MTRX / DigiLink
PT Monitor Input = Pro Tools Audio Bridge

Once we get wider busses in Pro Tools you won't need to make 2 paths = floor, ceilings.

Jeff

[nedd]

Originally Posted by creativecontrol

Once we get wider busses in Pro Tools you won't need to make 2 paths = floor, ceilings.

Jeff

Ahhh, now you are talking

Thanx Jeff, as always

[smurfyou]

Originally Posted by creativecontrol

Once we get wider busses in Pro Tools you won't need to make 2 paths = floor, ceilings.

Jeff

Thank you!!

[LukeHoward]

I'm trying a super-simple setup before tackling DAPS, just a two channel PTAB device into Ableton. When the output is a CoreAudio device* that is also clocked by my MTRX, I am hearing the occasional glitch. When the output device is PTAB routed back into PT, seems more solid. But that means having to route everything back through PT for monitoring which I'd rather avoid if possible (but if necessary, so be it).

Early days though, will continue to test!

* MOTU M64, USB to MADI interface

[LukeHoward]

OK, it looks like DAPS doesn't cope so well with DAB or PTAB as input and a (locked) interface as output.

Limiting number of real-time threads in Playback Engine helped slightly, but not really.

I tried both with a MOTU M64 and Dante Virtual Soundcard as output devices.

I guess the alternative, having a bunch of hidden tracks in Pro Tools to route back through HDX is also fine. (Or there a way to patch this directly within I/O setup?)

Renderer logs as follows:

2022-09-30 16:20:29 INFO  RendererExecutive - -------------------------------------------------initializing--------------------------------------
2022-09-30 16:20:29 INFO  Scheduler - Running scheduler with #8 threads
2022-09-30 16:20:30 INFO  RendererExecutive - Total latency in samples: 1058
2022-09-30 16:20:30 INFO  RendererExecutive - Started audio driver with 512 frame size at 48000Hz
2022-09-30 16:20:30 INFO  RendererExecutive - ---------------------------------------------------- DONE -----------------------------------------
2022-09-30 16:20:31 ERROR RendererExecutive - Audio device buffer underrun
2022-09-30 16:20:33 ERROR RendererExecutive - Audio device processor overload
2022-09-30 16:20:33 ERROR RendererExecutive - Audio device buffer overflow
2022-09-30 16:20:35 ERROR RendererExecutive - Audio device processor overload
2022-09-30 16:20:35 ERROR RendererExecutive - Audio device buffer overflow
2022-09-30 16:20:35 ERROR RendererExecutive - Audio device buffer underrun

[originalscottyg]

Originally Posted by creativecontrol

Once we get wider busses in Pro Tools you won't need to make 2 paths = floor, ceilings.

YES!!!!! Thank you, Jeff. Super excited for this!

[nedd]

Originally Posted by creativecontrol

You need to change nothing in your DADman monitor profile.

For your setup you should create a 2x INPUT paths in IO Setup which leverage AUX IO from Pro Tools Audio Bridge 32:

Speakers_9 = 7.1.2 path, to accommodate the 9 floor speaker channels + LFE
Speakers_Z = QUAD path, to accommodate the 4 height speaker channels

Outputs - same as above - but feeding out the MTRX / DigiLink outputs (to DADman) channels 1-14.

Yes, you will be able to do Speakers, Dolby Binaural and Apple Spatial all at the same time. Use a 7.1.4 Re-Render as shown in the screen grab to feed into Logic.

DAPS Input = Dolby Audio Bridge
DAPS Output = Pro Tools Audio Bridge 32
PT Output = MTRX / DigiLink
PT Monitor Input = Pro Tools Audio Bridge

Once we get wider busses in Pro Tools you won't need to make 2 paths = floor, ceilings.

Jeff

Hi Jeff,

I trying to follow your instructions here and there is one thing that bugs me:

Do I need to create Auxiliary tracks in Pro Tools in order to get the routing from PTAB to HDX/Headphones?

If I don't do it, there is no sounds coming from my speakers and headphones!

IF I do it, I need to create separate axes for floor speakers, height speakers and for BIN mix on headphones. Only then I can hear something.

Also when I was making output paths I chose HDX in AUX I/O in order to get some sounds out of the pro tools and into MTRX/HDX.

Also this way there is a big delay from what I see in pro tools and what I hear on speakers and HP's.

Am I doing something wrong here?

[LukeHoward]

Originally Posted by nedd

Hi Jeff,

I trying to follow your instructions here and there is one thing that bugs me:

Do I need to create Auxiliary tracks in Pro Tools in order to get the routing from PTAB to HDX/Headphones?

If I don't do it, there is no sounds coming from my speakers and headphones!

IF I do it, I need to create separate axes for floor speakers, height speakers and for BIN mix on headphones. Only then I can hear something.

Also when I was making output paths I chose HDX in AUX I/O in order to get some sounds out of the pro tools and into MTRX/HDX.

Also this way there is a big delay from what I see in pro tools and what I hear on speakers and HP's.

Am I doing something wrong here?

I think the idea is to make HDX the primary playback engine, and use Aux I/O to route to and from DAPS. As I understand it, you still need to create the auxiliary tracks to monitor the returns from DAPS.

(it would be nice if this could be matrixed in I/O setup, so the monitoring setup is decoupled from the session; maybe it can be and I haven't figured it out yet. This is why I was trying to get DAPS to send straight to the MTRX via another interface such as DVS, but I haven't been able to do that reliably yet.)

[LDS]

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

[LukeHoward]

Originally Posted by LDS

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

None I can think of, except that so far it seems more likely to actually work (based on my limited testing).