Topic: [Solved] Pops / Snaps with RADAR 24, DIGIFACE USB, CUBASE 13, WIN 10

Hi all,

Recently I've had consistent pops / snaps during recording sessions that has become increasingly frustrating to track down.

Windows 10,  i7-9700K CPU running Cubase 13 PRO.

I'm running RADAR 24 as my converter.

RADAR ADAT out x3 ---> DIGFACE USB --> Cubase 13 PRO
DIGIFACE 1,2 out --- > BEHRINGER POWERPLAY 16
DIGIFACE 4 out --> TC ELECTRONIC BMC-2 Monitor Controller

DIGIFACE buffer 128
Cubase is set to EXTERNALLY CLOCKED
Sample rates all 48
Drives are up to date

I read that the DIGIFACE CLOCK SOURCE should always be set to INTERNAL. When I do that the snaps will be embedded in the recorded audio. If I switch the CLOCK SOURCE to INPUT 1, 2 or 3 the snaps will occur when playing back audio, when the DAW is idle, but almost never when recording.

Either way the amount of snaps will occur closer together and more frequently as the day goes on.

When CLOCK SOURCE is INTERNAL the input status flashes between "Sync" and "Lock"
When CLOCK SOURCE is set to INPUT 1, 2 or 3 the input status says "Sync".

During mixing (with the RADAR turned off) I set CLOCK SOURCE to INTERNAL and experience no snaps or pops in the day. Buffer usually stays at 128 unless the mix session demands a higher buffer size.

Latency Monitor gives the all clear, I think. Gotta figure out how to attach an image here.

Any help will be much appreciated!

2 (edited by waedi 2024-08-24 23:54:20)

Re: [Solved] Pops / Snaps with RADAR 24, DIGIFACE USB, CUBASE 13, WIN 10

Lots of indicators for not in sync.

Did you follow this ?

Let the Digiface clock be internal and connect 2 toslink cables to the Radar in and out.

https://i.ibb.co/zGVNTCH/Bildschirmfoto-2024-08-25-um-00-51-08.png

M1-Sequoia, Madiface Pro, Digiface USB, Babyface silver and blue

3 (edited by ramses 2024-08-25 06:13:40)

Re: [Solved] Pops / Snaps with RADAR 24, DIGIFACE USB, CUBASE 13, WIN 10

Hi Jordan.

Welcome to the RME user forum. Thanks for the information, a few comments:

Jordan wrote:

RADAR ADAT out x3 ---> DIGFACE USB --> Cubase 13 PRO
DIGIFACE 1,2 out --- > BEHRINGER POWERPLAY 16
DIGIFACE 4 out --> TC ELECTRONIC BMC-2 Monitor Controller

Sorry, but your little ASCII drawing is missing some overview wink
You should give it a little more structure and that the type of digital connections and inputs and outputs are easier to see.
Especially if you have a clock synchronization issue.

Look here for examples, they vary a bit depening what the topic is:
https://forum.rme-audio.de/viewtopic.ph … 18#p223318
https://forum.rme-audio.de/viewtopic.ph … 91#p216891
https://forum.rme-audio.de/viewtopic.ph … 39#p189939

I am also missing links to the products that you are connecting. Why?
It was difficult to get information about the RADAR 24 and the Behringer, which seems to be missing a digital port at all, at least the model that I found. So I would appreciate it if you could provide links to the products so that it is clear what exactly you are connecting.

Jordan wrote:

I read that the DIGIFACE CLOCK SOURCE should always be set to INTERNAL.

You can't say that like that.

To get an understanding of clock synchronization, see my blog:
https://www.tonstudio-forum.de/blog/ent … ios-en-de/

In short:

Operationally, it is more convenient if the main interface (whose driver you load in the DAW) is clock master (clock source = “internal”).

The sample rate of your DAW project is then automatically passed on to the interface via the driver. The other digitally connected devices, which must all be slaves (there can only be one clock master), then automatically follow the clock of the master.

The clock is passed on either via digital connections (ADAT, SPDIF, AES, MADI) or via word clock (WC).

Now it depends on how the individual connected devices are equipped. Not all devices have a digital input, so it is not possible to learn the clock from another master or slave (e.g., some preamps). If WC is also not available, the device cannot be synchronized as a slave clock.

In this case, you would have to make this device the master. If you have several such devices, then you have a problem because there can only be one master in a setup.

First assume that the Digiface USB is the master and then check whether all devices can become slaves via a digital input or WC. If it doesn't work for one device, then make it the master. Then you will have to operate the Digiface USB as a slave, but this is not an issue either, as RME devices are perfect clock slaves thanks to SteadyClock or SteadyClock FS.

In my blog article you also find further information and references about RME SteadyClock [FS].

BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub14

Re: [Solved] Pops / Snaps with RADAR 24, DIGIFACE USB, CUBASE 13, WIN 10

Cubase should be internally clocked

Babyface Pro Fs, Behringer ADA8200, win 10/11 PCs, Cubase/Wavelab, Adam A7X monitors.

Re: [Solved] Pops / Snaps with RADAR 24, DIGIFACE USB, CUBASE 13, WIN 10

mkok wrote:

Cubase should be internally clocked

That's right, this setting can't work. Cubase needs the “internal” synchronization with the main interface. At best, this could be needed in the video area, if picture and sound have to be synchronized via video cards (just a guess). In my opinion, this makes no sense at all in an audio setup. For video, there are also cards such as the RayDAT with an optional TCO add-on module for synching with LTC and Video.

BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub14

Re: [Solved] Pops / Snaps with RADAR 24, DIGIFACE USB, CUBASE 13, WIN 10

Thanks everyone.
I did have another cable already connected from DIGIFACE OUT to RADAR IN - RADAR ADAT SYNC.
I unchecked EXTERNALLY CLOCKED in Cubase and haven't had an issue since. Possible that I or someone checked this and became the default setting.
Thanks again!