DADman 5.6.9 Now Available

[creativecontrol]

I believe that is something that NTP engineering would like to realize but is not currently possible.

best,


Jeff

Originally Posted by uptheoctave

Will Dadlink work with MTRX (1) as well as 2?

[creativecontrol]

No firmware update is required for DADman v5.6.9.x. Make sure your MTRX Studio Main Board is running 1.1.1.5 or greater.

best,


Jeff

Originally Posted by IrelandM

Hi everyone,

Is there a firmware update required for use with the MTRX Studio and DADMan 5.6.9.1.
Also could Avid include a release date / time within user's accounts.

Regards

[uptheoctave]

Originally Posted by creativecontrol

I believe that is something that NTP engineering would like to realize but is not currently possible.

best,

Jeff

Thanks for the info Jeff.

[BScout]

Originally Posted by creativecontrol

I believe that is something that NTP engineering would like to realize but is not currently possible.

best,


Jeff

Isn't "DADlink" just "NTP Hotlink"? The Penta 720 (which by all appearances is just the AX32) has this feature. The AX32 shows the option for NTP hotlink too (from the beginnings of that unit) for optical MADI. And of course, AX32 and MTRX I are sister products. Would love more insight (possibly from NTP/Jan?) We have a DAD Core256 coming to bolster a completely maxed MTRX I and this would add some more flexibility.

[ntp-jl]

Originally Posted by BScout

Isn't "DADlink" just "NTP Hotlink"? The Penta 720 (which by all appearances is just the AX32) has this feature. The AX32 shows the option for NTP hotlink too (from the beginnings of that unit) for optical MADI. And of course, AX32 and MTRX I are sister products. Would love more insight (possibly from NTP/Jan?) We have a DAD Core256 coming to bolster a completely maxed MTRX I and this would add some more flexibility.

HotLink only supports 48k sample rate. DADlink supports all sample rates from 44.1 to 384 kHz (with channel count dependant on sample rate).

DADlink also includes timestamps so the outputs from the router in each device can be time-aligned, i.e. the latency in the router is the same no matter whether a channel passes through just one device or through multiple devices (that are linked via DADlink). This means that if you distribute a channel across multiple devices, the output from each device will be aligned (assuming the output is the same type on all devices). This is btw. one of the reasons why DADlink and HotLink are not compatible.

Implementing DADlink on AX32/MTRX I is challenging because the FPGA that would do DADlink is completely full, so our engineers are looking at various possibilities for optimizing it. We will have to wait and see if they succeed with it.

[uptheoctave]

Thanks Jan, that is all very helpful to know.

Originally Posted by ntp-jl

HotLink only supports 48k sample rate. DADlink supports all sample rates from 44.1 to 384 kHz (with channel count dependant on sample rate).

DADlink also includes timestamps so the outputs from the router in each device can be time-aligned, i.e. the latency in the router is the same no matter whether a channel passes through just one device or through multiple devices (that are linked via DADlink). This means that if you distribute a channel across multiple devices, the output from each device will be aligned (assuming the output is the same type on all devices). This is btw. one of the reasons why DADlink and HotLink are not compatible.

Implementing DADlink on AX32/MTRX I is challenging because the FPGA that would do DADlink is completely full, so our engineers are looking at various possibilities for optimizing it. We will have to wait and see if they succeed with it.

[BScout]

Originally Posted by ntp-jl

HotLink only supports 48k sample rate. DADlink supports all sample rates from 44.1 to 384 kHz (with channel count dependant on sample rate).

DADlink also includes timestamps so the outputs from the router in each device can be time-aligned, i.e. the latency in the router is the same no matter whether a channel passes through just one device or through multiple devices (that are linked via DADlink). This means that if you distribute a channel across multiple devices, the output from each device will be aligned (assuming the output is the same type on all devices). This is btw. one of the reasons why DADlink and HotLink are not compatible.

Implementing DADlink on AX32/MTRX I is challenging because the FPGA that would do DADlink is completely full, so our engineers are looking at various possibilities for optimizing it. We will have to wait and see if they succeed with it.

This is great to hear. It would help with adding the newer equipment to established DAD/MTRX setups.
(And, as a side note, even if the full channel compliment wasn't possible on the AX32/MTRX, I'd take 1/2 the channels rather than none at all.)
Most of our stuff is 48k (post production) so higher sample rates are less of a worry but that time-alignment/stamping would be really useful for distributed units connected via fibre.

[uptheoctave]

Originally Posted by BScout

This is great to hear. It would help with adding the newer equipment to established DAD/MTRX setups.
(And, as a side note, even if the full channel compliment wasn't possible on the AX32/MTRX, I'd take 1/2 the channels rather than none at all.)
Most of our stuff is 48k (post production) so higher sample rates are less of a worry but that time-alignment/stamping would be really useful for distributed units connected via fibre.

+1 to this.
I've got 2x 1st gen boxes and I'd rather not sell them if I do not have to.
Really my need is simply serving up the analogue IO to the main interface (MTRX II).

I've tried Dadlink in the last few days and it hasn't gone well, so far.
I might be doing something dumb but it works fine when setting the optical ports to MADI.
When I set them to DADlink the AX64 (which is following the MTRX II) drops sync every3-4 seconds if I use Dadlink as the sync method.
If I use workclock or Dante to sync then the audio is ok but I get the channels flashing yellow red in Dadman.

I've got a support call in so hopefully will get to the bottom of it.

Here is a video showing the issue.

https://www.youtube.com/watch?v=lyuFVjXFZEw

[creativecontrol]

Just to close the loop on this one, I suspect during this trial you were not using the required Gigabit optical SFPs - which would explain the flashing channels.

One of the 850nm options that works well is the Avago compatible SFP from ProLabs: AFBR-5701PZ.

For more information on DADLink:
https://resources.avid.com/SupportFi...ADI_module.pdf


best,


Jeff

[uptheoctave]

Originally Posted by creativecontrol

Just to close the loop on this one, I suspect during this trial you were not using the required Gigabit optical SFPs - which would explain the flashing channels.

One of the 850nm options that works well is the Avago compatible SFP from ProLabs: AFBR-5701PZ.

For more information on DADLink:
https://resources.avid.com/SupportFi...ADI_module.pdf


best,


Jeff

Hi Jeff,

Yes sorry, I covered this off a long time ago.
I should have updated the thread, but I wrote an article about DADlink where I discussed the issue.

https://www.production-expert.com/pr...-count-systems

Yep, it was using the MADI compatible SFP's that I was using previously: Broadcom HFBR-57E0LZ
They won't work with DADlink.

I had some Ubiquiti UF-MM-10G SFP’s lying around so I used a couple of those and they are fine.
I've had no issues.
Given they are rated for 10G they are overkill but, as I said, I had them to hand.