S/Mux crackle ONLY in the recording

[Throttler]

Hi all,

I am using the Scope as a slave via adat and sending 96kHz via s/mux.

The sound is great and no problems at all when monitoring.

BUT : when listening to the recorded result it's full of crackle.

p.s. I recorded in every possible combination, straight from the s/mux in, via direct console out, the mix, all channels, 1 channel at the time etc.

Any ideas?

Thanx in advance

[astroman]

which machine is recording ? Scope or the 'other' one you're slaved to...
what kind of sync-master is used on that ?
are TOSLink cables ok ? connection boxes clean ?

according to your description I'd rather guess a buffer problem than TOSLink sync
otherwise you'd hear it on the monitors...

cheers, Tom

[Throttler]

which machine is recording ? Scope or the 'other' one you're slaved to...
what kind of sync-master is used on that ?
are TOSLink cables ok ? connection boxes clean ?

according to your description I'd rather guess a buffer problem than TOSLink sync
otherwise you'd hear it on the monitors...

cheers, Tom

Hi Tom, thanx for the reply.
Scope is recording, slaved to Lynx Aurora clock via s/mux.
Cables are brand new.

Buffer problem?

[astroman]

well kind of... most modern boards have a terribly bad PCI bus integration
with many ASIO channels you can get into trouble
with (additional) Scope reverbs you almost certainly will

cheers, Tom

[garyb]

sounds like a sync issue. it could be a simple as a dusty optical connector. are you sure you're synced properly?

[Throttler]

sounds like a sync issue. it could be a simple as a dusty optical connector. are you sure you're synced properly?

Good day Gary,

The cables are brand new, and when using the ADAT A or B source device, the recordings are flawless.
Moreover, when monitoring in either ADAT or S/MUX, the sound is crystal.

The issue is only there when you listen to the s/mux recorded material. When recording the ADAT A or B source device everything is perfect.

[garyb]

what are you recording to? what app or sequencer? which driver? what latency?

if all kinds of playback are clear but the recordings have clicks, it's probably a setup issue, but it might be a buffer setting in the recording app. just throwing out guesses, but every resource in the computer is used doubly at 96k. 1 or 2ms latency is possible, but you may run out of resources.

[Throttler]

Thank you for the prompt reply.
I'm running Scope 5.1.2709x64
ULLI is at max, ie 12ms @ 96kHz.
Using the ASIO2 Flt Source 64

I thought about that too, so I tested it at both Cubase 8 x64 and 7.5.3 x64, same result. I tried the ASIO guard, no difference.
If it were a recording app issue, wouldn't that be also the case in ADAT source ?

[garyb]

EIST or Cool n Quiet still enabled in the bios?

if you monitor the sound from the modules and it's click-free, the recording of that sound should also be click-free. normally, Cubase runs with above average priority. if that's changed(the default priority can be changed), then that might be a reason.