Sonosax M2D2 clocking question

[louisebyrd]

Hello!

I'm currently syncing the M2D2 with my Metric Halo ULN-8 IV using AES. The only way to avoid clocking issues is to set the M2D2 as the master. I'm having trouble finding a way to configure the M2D2 as a slave, and I'm curious if anyone else has successfully done this. My current solution for making the Metric Halo a slave works, but I foresee this limitation becoming a problem as my setup evolves. I may need to reconsider the M2D2's role in my system. That said, I truly love the M2D2—it's an amazing piece of equipment!

[pscottm]

The Sonosax AES input uses ASRC so resamples the digital signal coming from another device, so it doesn't 'sync' per se.  Maybe the ULN is looking for a device to sync up with when in MASTER mode, and it isn't receiving the feedback it wants, causing the clock to misbehave?

[louisebyrd]

Quote

The Sonosax AES input uses ASRC so resamples the digital signal coming from another device, so it doesn't 'sync' per se.  Maybe the ULN is looking for a device to sync up with when in MASTER mode, geometry dash scratch, and it isn't receiving the feedback it wants, causing the clock to misbehave?

 

 

Thanks for your suggestion. I got it.

[Fred Salles]

If that can help for non studio future projects: I used the M2D2 on the AES input of Sound Devices recorders (series 6&8) without a single clock issue that I can remember. The recorders never needed to be synch slaved and I there is no setting for AES output clocking in the M2D2, so that probably means it just worked fine from day 1 onward and I never had to question it. I just remember the AES out sample rate can be set different from the system one, but i do not see the use of it nor if I understood properly.