MTRX Studio Mic Input via DVS

[Ooptron]

Hey guys,

I have the MTRX Studio configured for Atmos via DVS at the studio. I run Nuendo, so no Digilink or Protools configs. I used the Dante Controller app for setting up the routing between DVS and DADman.

Due to an unforeseen technical failure, I need to use the Mic input on the MTRX Studio to record voiceovers next week. Is it possible to route the Mic inputs to the DAW while using DVS?

In DADman's matrix, I tried mapping the AD to the Dante Main matrix column, but couldn't get any Mic signal to show up in the DA monitor section no matter where I routed it. I only managed to get the Mic input to the Control Room section via the Monitor profile. Couldn't get any signal into the DAW for recording.

Is this a routing error, or is this not possible using DVS? What could I be missing? Do I need to map something in the Dante Controller app? Any help is appreciated. Thanks!

[Darryl Ramm]

Only issue I can think you should run into would be DVS channel count issues at high sample rates, ... and you don't say what the sample rate is (and I'd assume you get those chopped off the upper channels anyhow).

Does the Inst/Mic AD should show up in the routing matrix, and always showing signals in DADman on those two inputs? Everything look correct? If stuff there is not making sense maybe post screenshots (on a photo sharing site and post the link here to avoid it being uselessly downsampled by DUC).

Personally I would ditch DVS in a hearbeat and get the lovely Thunderbolt option card.

[Ooptron]

I'm running at 48kHz, so not a very high sample rate.

Yes, both Mic/Inst show up in the routing matrix with active signal. I'll grab screenshots when I'm in the studio next and post them here. It could be just a routing issue.

Yep, would love to upgrade to the TB option card, although I read it takes ages for it to ship. However, I work a lot with recording and use UA Apollos for it and end up utilizing the MTRX Studio only for surround/Atmos mixes. I do prefer the sound of the MTRX Studio, especially with my room calibration.

[creativecontrol]

Certainly agree with Darryl that you will have much better workflow and latency with the TB3 option once you get it.

Regarding DVS, this should also work as IO in a pinch.
A/D = Source/Input -> Dante = Destination/Output in the DADman patchbay.
Then, in Dante Controller, Source = MTRX ST (top), Destination = DVS (bottom left, your workstation name)

That will complete the conduit from a mic, line, or DI input to patch to the IP Audio network. To Monitor, it sounds like you have that sorted - with a Source in your Monitor Profile coming from Dante. This would have have been patched in a reverse manner in Dante Controller:
Source = DVS (your workstation, top) to Destination = MTRX ST.

Happy to help if you want to illuminate further with some images.


best,


Jeff

[Ooptron]

Thanks, Jeff!

I think it's the Dante Controller bit which always gets me. I find the UI too damn confusing, haha.

I'll try this out later in the studio today and grab some screenshots if I'm unsuccessful.

[Ooptron]

Originally Posted by creativecontrol

Certainly agree with Darryl that you will have much better workflow and latency with the TB3 option once you get it.

Regarding DVS, this should also work as IO in a pinch.
A/D = Source/Input -> Dante = Destination/Output in the DADman patchbay.
Then, in Dante Controller, Source = MTRX ST (top), Destination = DVS (bottom left, your workstation name)

That will complete the conduit from a mic, line, or DI input to patch to the IP Audio network. To Monitor, it sounds like you have that sorted - with a Source in your Monitor Profile coming from Dante. This would have have been patched in a reverse manner in Dante Controller:
Source = DVS (your workstation, top) to Destination = MTRX ST.

Happy to help if you want to illuminate further with some images.


best,


Jeff

Thanks a ton Jeff! It was the Dante Controller patching in which was the problem. Working great now.

[creativecontrol]

Glad to hear it!



Jeff