Motu 828 mk2 adat sync problem over 44.1 kHz
Posted: Tue May 25, 2021 9:59 am
Hey guys,
new member here.
I owned an 828 mk2 for some years now, but hassles with firewire and Windows 10 have finally driven me
to a new interface, despite being satisfied with the 828.
I bought an Audient iD14 mk2, because I realized the 828 with its abundance of I/O was way too much
for my little home studio.
However, I wanted to use my Motu still, if I need 2 more preamps. For that, I connected the Motu to the
Audient via ADAT.
Here's where the problems start. I configure the Audient's clock source as external via ADAT.
As soon as I bump up the sample rate on the MOTU higher than 44.1 kHz, the Audient software
is reporting sync problems. Sound seems to come through fine though.
I already had a similar problem a year ago, as the Motu was used in a recording and it couldn't
sync to a Focusrite Saffire. I think, we solved the problem by connecting the MOTU to the PC
and getting the clock from the Saffire. That's why I don't think it's a problem with the Audient interface.
Has anyone heard/experienced a similar problem?
new member here.
I owned an 828 mk2 for some years now, but hassles with firewire and Windows 10 have finally driven me
to a new interface, despite being satisfied with the 828.
I bought an Audient iD14 mk2, because I realized the 828 with its abundance of I/O was way too much
for my little home studio.
However, I wanted to use my Motu still, if I need 2 more preamps. For that, I connected the Motu to the
Audient via ADAT.
Here's where the problems start. I configure the Audient's clock source as external via ADAT.
As soon as I bump up the sample rate on the MOTU higher than 44.1 kHz, the Audient software
is reporting sync problems. Sound seems to come through fine though.
I already had a similar problem a year ago, as the Motu was used in a recording and it couldn't
sync to a Focusrite Saffire. I think, we solved the problem by connecting the MOTU to the PC
and getting the clock from the Saffire. That's why I don't think it's a problem with the Audient interface.
Has anyone heard/experienced a similar problem?