MTRXst HDN sync issues

[Matt Stephanson]

Hi,

I’m running the MTRXst with OMNI HDN thru DVS.
I’m getting random crackling on playback only - not on record.
Scrubbing through the clip, or playing back, the crackling is random in location and intermittent.

Mac Pro 7,1 with usb-c to ethernet adaptor (1Gb), Catalina, latest DADman and DVS and Dante Controller.

Using Word clock from mtrx to omni.

Anyone heard this crackling or have an idea of the right config for this setup?
Thanks, folks!

[creativecontrol]

Greetings,

I think we need a bit more information. Both MTRX Studio and HD OMNI are DigiLink peripherals.

How are you distributing clock between MTRX Studio and HD Omni?
What is the primary interface?
What are you monitoring through? I'm not clear on what role DVS is playing in this equation. Were the source tracks ingested from the MTRX Studio and then played back out to a Dante Stream? Let us know. Thanks.


Jeff

[Matt Stephanson]

Thanks for helping out again!!

The MTRX is sending WC out to the OMNI’s WC in; OMNI shows EXT lit on front panel.

I thought the MTRX was the Primary, as it’s called Grand Master clock in Dante Controller, but under digilink in DADman, I have the OMNI set to Pri/Pri (maybe that needs to be Pri/Ext?).

Clock is set to Wordclock in DADman, I even tried Wordclock, base.

I was monitoring through DVS as Pro Tools’ main output. I can hear and see everything deflecting on meters in DADman, even select 7.1 to 2.0 fold down using the panel buttons on the MTRX.

I recorded the clip through the MTRX, seeing the Blue input meters deflect during tracking, and seeing the Orange output meters work during playback.

You’re making me think I have the digilink set incorrectly; is it that Pri/Pri would be wrong for this setup (in DADman profile)?

Sorry for my noobishness and thanks again!

[creativecontrol]

Not a problem.

This is the part I'm particularly confused about:
"I was monitoring through DVS as Pro Tools’ main output. "

If you are monitoring Pro Tools - wouldn't you be simply feeding DigiLink out to either MTRX Studio or OMNI and monitor that source?

Are you using an HD Native TB playback engine with the MTRX ST and HD Omni connected to your engine?

Yes - Pri/Pri is perfectly fine assuming you are connecting MTRX ST to one port of your HDNTB and HD OMNI to the 2nd port.


Jeff

[Matt Stephanson]

Hi Jeff,

I’m monitoring from the MTRX analog out 1-8 setup in DADman as a 7.1 monitor path in my profile.

In Pro Tools, I selected DVS as the playback engine.
I’m sending digilink exactly how you described.

Trying to figure out other permutations of this setup.

I do wonder if a dedicated card like the HDN pcie card would help, but I can’t find any for sale now. Will keep trying combinations of settings.

Many thanks for the help!! :)

[creativecontrol]

Ok - starting to get a better picture of what you are doing.

Certainly you can run Pro Tools with DVS - Dante Virtual Soundcard playback engine - but it will always have more latency than a direct DigiLink connection to MTRX Studio.

You can't be using DigiLink if you don't have a DigiLink based engine card including:
HDX PCIe
HDN PCIe
HDN TB

What I don't understand is what you are doing with the HD Omni? Omni is a DigiLink peripheral that is intended to be connected to a HD based engine card.


Jeff

[Matt Stephanson]

I am running HDN TB OMNI, have the digilink cables 1 > TB box, 2 > OMNI.

I'm using the OMNI to spit out 8 channels to the mixing desk for analog mixing (they become desk channels 9-16 on the ASP4816).

I'm using the MTRX's first 8 analog outs to feed the 7.1 mons.
I'm using the MTRX's second 8 analog outs to feed the desk's channels 1-8.

I'm getting the nice DA from the MTRX for monitoring, plus the first 8 of a 16 channel mix onto the desk.

For whatever reason, this morning the thing is running perfectly; no crackling or popping. Beautiful.

---

Further considerations are that I'm running this using DHCP, and am in a university - so maybe it's a network traffic issue. It's running perfectly right now, because it's 8am and nobody is doing anything on the network. Could that be a contributing factor? I'm new to Dante - have a lot to learn!

Since you mentioned that DVS is more latency prone, would the REDnet pcie card be my best option now, considering the HDN pcie card is EOL? I'm thinking that too much latency might cause some samples to arrive late and then it clicks and pops.

[creativecontrol]

Yes, if you are using Dante Virtual Soundcard on a busy network - especially with large file transfers you may get dropouts, pops and clicks on your dante stream.

How are you using HDN TB if you are using Dante Virtual Soundcard as your playback engine?


Jeff

[Matt Stephanson]

Ok, thanks - makes sense about the traffic.

I'm using DVS, as that's all that appears in Pro Tools' Playback Engine dialog.

I'm used to (before we got the MTRXst) seeing HD Native Thunderbolt in the list, but since installing MTRX, it's gone.

So, I'm hearing that it's best to create your own adhoc network and run an actual card to ensure full dedication to the audio streams. With that in mind, I'll try to source out a card and ditch the ethernet to usb-c adaptor.

[creativecontrol]

It's not critical to have a dedicated card (like a Focusrite PCIeR) but it does certainly have significantly lower latency than DVS.

You can create a Dante network (that is distinct from your intranet, file sharing LAN) that used for IP audio with DVS and you won't have any of the dropouts you are experiencing.

Regarding the HDNTB, I would recommend reinstalling the HD Driver (current and version matched to your Pro Tools version). Ensure that you have a DigiLink auth on your iLok and see if the HDNTB shows up on the Thunderbolt bus. Let me know.


Jeff