How do I connect the TC Electronic Finalizer 96k to the Focusrite 18i8?

[AMusicPlayerPlus]

Hello,
I am using a Focusrite 18i8 audio interface.
I’m considering using the TC Electronic Finalizer for mastering:
TC Electronic Finalizer 96k Studio Mastering Processor
or
TC Electronic Wizard Finalizer Plus.

How do I connect the TC Electronic Finalizer 96k to the Focusrite 18i8 so that Cubase processes the resulting track and saves it as MP3/WAV/FLAC, etc.?

[The Elf]

Physically you will connect the outputs of the processor to to a pair of inputs on your interface, and connect a pair of outputs from your interface to the processor's inputs. Using the SPDIF connections would seem the straightforward option.

In Cubase you will create an 'External Effect' and tell Cubase which I/O ports you have it connected to. Now you can allocate your external processor in the same way as a VST effect - you will likely add this to your master output buss, or maybe to a sub-group.

Having said all this... I can't imagine what these external processors are going to provide that isn't already covered by Cubase's bundled VST processors.

[Tomás Mulcahy]

BNC to RCA 75ohm cable also needed for wordclock sync if you are to use any of the digital audio interface options including SPDIF i/o.

[Hugh Robjohns]

No separate word clicking necessary if using the S/PDIF input to the Finaliser as that interface is self-clocking.

So Focurite S/PDIF out to TC S/PDIF in. Set the TC to clock from its digital in.

TC S/PDIF out to Focusrite S/PDIF in. Set Focusrite as clock master (computer).

[OneWorld]

Having said all this... I can't imagine what these external processors are going to provide that isn't already covered by Cubase's bundled VST processors.

I tried and I failed - I put the setup through every option and the VST was equal to the hardware option

[Sam Spoons]

I have an old TC Finalizer Plus and it works for me. I like the little bit of 'fairy dust' it adds. I use (and prefer) my DAW as a posh tape recorder and do most processing using my X32 mixer (which is also my audio interface) so the Finalizer fits in nicely.

[AMusicPlayerPlus]

Hi,
I already have TC Electronic Clarity connected to my Focusrite 18i/8 via SPDIF.
How I can connect TC Electronics Finalizer 96K using IN/OUT TR/XLR cables? Or is there way to split SPDIF?
Please advise.

[Wonks]

Elf has already given you the answer.

And no, you can't split S/PDIF.

[The Elf]

I already have TC Electronic Clarity connected to my Focusrite 18i/8 via SPDIF.

You could connect the TC Clarity via USB. That's how I do it.

[James Perrett]

Or is there way to split SPDIF?

You can split SPDIF using a distribution amplifier.

https://www.sonifex.co.uk/redbox/rbdda6s_ld.shtml

is one example (and there's one currently on Ebay).

[Tomás Mulcahy]

No separate word clicking necessary if using the S/PDIF input to the Finaliser as that interface is self-clocking.

So Focurite S/PDIF out to TC S/PDIF in. Set the TC to clock from its digital in.

TC S/PDIF out to Focusrite S/PDIF in. Set Focusrite as clock master (computer).

That's a neat feature. Would that every S/Pdif device did that!

[James Perrett]

That's a neat feature. Would that every S/Pdif device did that!

I'm having a hard time trying to think of an S/PDIF device that can't be clocked like that - unless it is a device that only has an S/PDIF output.

[Aled Hughes]

No separate word clicking necessary if using the S/PDIF input to the Finaliser as that interface is self-clocking.

So Focurite S/PDIF out to TC S/PDIF in. Set the TC to clock from its digital in.

TC S/PDIF out to Focusrite S/PDIF in. Set Focusrite as clock master (computer).

That's a neat feature. Would that every S/Pdif device did that!

I’m pretty sure that every device I’ve ever owned or used that had an S/PDIF input could be clocked this way!

[Sam Spoons]

No separate word clicking necessary if using the S/PDIF input to the Finaliser as that interface is self-clocking.

So Focurite S/PDIF out to TC S/PDIF in. Set the TC to clock from its digital in.

TC S/PDIF out to Focusrite S/PDIF in. Set Focusrite as clock master (computer).

That's a neat feature. Would that every S/Pdif device did that!

I thought they did, word clock is embedded in S/PDIF as a part of the protocol.

Wiki says "The receiver does not control the data rate, so it must avoid bit slip by synchronizing its reception with the source clock."

[Tomás Mulcahy]

Maybe I am confused... but only one device can be the master clock, right? My understanding is you normally can't have digital in and out simultaneously with spdif. I think what Hugh is describing is a feature of the TC, that it can get a clock from spdif while still outputting an externally clocked signal over spdif. Normally, you need to set the external device to external clock and clock it via wordclock from the audio interface which is the master. No?

[Hugh Robjohns]

That's a neat feature. Would that every S/Pdif device did that!

I can't think of a device with an S/PDIF input that won't clock from it too.

What devices are you thinking of?

[Hugh Robjohns]

Maybe I am confused...

I think that's a good bet

...only one device can be the master clock, right?

Correct.

My understanding is you normally can't have digital in and out simultaneously with spdif.

No. Thats bonkers. I have lots of devices with digital S/PDIF ins and outs, with both working simultaneously. The TC Finalyser will do exactly that, in fact.

I think what Hugh is describing is a feature of the TC, that it can get a clock from spdif while still outputting an externally clocked signal over spdif.

Not at all. If the input to the box is S/PDIF the box must synchronise to the S/PDIF signal (unless it has a sample rate converter on the S/PDIF input)... in which case the S/PDIF source becomes the clock master.

And the box's digital output will also be synchronised to the S/PDIF source master.

Normally, you need to set the external device to external clock and clock it via wordclock from the audio interface which is the master. No?

If the S/PDIF signal us coming from the interface you could click the device externally via w/c from the interface... but why go to all that trouble (assuming the interface even has a w/c output) when the S/PDIF signal contains an embedded wordclock anyway? Just select S/PDIF In as the device's clock source. Job done.

The device will be synchronised to the interface (which is the master) and the devices output will be synchronised to the interface and accepted without any problem.

[Tomás Mulcahy]

Ok. Is it ADAT that has to have WC to be bidirectional?

[Aled Hughes]

Ok. Is it ADAT that has to have WC to be bidirectional?

Nope, ADAT works the same way. At least everything I have does - I have quite a few bits connected at home and at the studio using S/PDIF, ADAT, MADI and AES, and I don't think I'm using a single dedicated WC connection (apart from maybe in the converter rack in the main studio which has four different RME units, can't remember how that's configured off the top my head) - it's all clocked via the digital connections.

[Wonks]

With two units bi-directionally connected by S/PDIF, one unit (A) is set to work from its internal clock, the other unit (B) is set to work from an external (S/PDIF) clock.

Unit B receives the clock signals from unit A, and unit B's outgoing S/PDIF is clocked to the incoming S/PDIF clock, and so it uses the same clock signal as unit A, so synchronises without any issues.

[merlyn]

If you've ever used S/PDIF as a clock you will have noticed that it syncs even when there is no signal, i.e. when the data is a stream of zeros. When an 'embedded clock' is talked about, it's not like there are two separate data and clock signals. The data is the clock.

To do this, the data is coded. The obvious way to think about digital audio is that a 0 is low and a 1 is high. Or in an optical connection 0 is dark and 1 is light. That's one way to do it and is the simplest coding scheme. There are other ways of coding 0s and 1s and S/PDIF uses bi-phase mark. On every bit there is a transition. One transition represents a 0, and two transitions represents a 1. This way the data is always at least half the speed of the clock and the clock can be extracted.

[Tomás Mulcahy]

That clears that up then This forum is great, look at all the good quality information I got. Thank you all!

[merlyn]

Bi-phase mark is bang up to date, originating in 1949. AES3 also uses bi-phase mark. The down side is that it doubles the bandwidth, which isn't a problem for two channels of digital audio.

ADAT doesn't use bi-phase mark as bandwidth is more of a consideration. With ADAT synchronisation is done at the frame level, not at the bit level.

In computer land kHz is slow.

• kHz <=> ms
• MHz <=> us
• GHz <=> ns
• THz <=> ps
• PHz <=> fs

There are errors involved in recovering a clock, and audiophiles would probably get their knickers in a knot about that. The 'FS' in RME's Babyface Pro FS stands for femtosecond, which is what RME want to get the error down to.