Xite-1 Word Clock

[mausmuso]

Hi There,
I am running XITE-1 on a stand-alone Wind 11 PC and slaving to a RME RayDAT (c/w RME Word Clock Module) card on the main DAW.
I also have an A16 slaved by Word Clock to the RME RayDAT (no issues here, see below ADAT 3 & 4 duly synced).

Sync is generally fine, with the following caveats:
- ADAT A out (SCOPE) is connected to the RayDAT ADAT 1 In. This configuration gives me continual static on 'ADAT 1 In' channels ( I take 'ADAT 1 In' out of the equation by setting AEB/TEB to 'ADAT 1 In' on the RayDAT),
- The RayDAT reports the 'Clock Source' as coming from 'ADAT 2', even though it is set to 'Sync In'?

Whilst this configuration works, I am not sure the RayDAT is actually slaved via the word clock as it reports the sync coming from ADAT 2 (via SCOPE ADAT B out)?
Whilst I can live without 'ADAT 1 In', I am interested if others have a similar issue?

Pics shows my current workable sync configuration, with ADAT 1 effectively not used.

Samplerate Settings.png (17.83 KiB) Viewed 4237 times

RayDat Settings.png (15.67 KiB) Viewed 4237 times

regards
maus

[valis]

"Sync In" is at the bottom of the "Input Status" area and shows no lock. BNC/wordclock is an issue with Xite under 64bit/Scope 7, documented here on the forums and I believe on ScopeRise. Set your "Clock Source" to "ADAT 2". You can easily do lower buffer than 512 too, I'm sure (on the RayDAT).

On the Xite panel, the selection/radio button shouldn't matter if Xite is *master*, it will only matter for slave.

Check your ADAT 1 connection (bad cable, not fully seated, dirty port(s) etc).

[mausmuso]

Thanks Valis,
I missed the BNC/wordclock posts also I will check ScopeRise.
I feared it was an known issue with Xite and Scope 7.
Not a biggy given it works with ADAT 2 though,
I will check (again) the ADAT 1 TOS cable. Actually on occasions it has worked, so that does point to a poor connection.
Thanks again,
Regards
maus

[garyb]

wordclock in works.

[Bud Weiser]

Using RME RayDat and XITE-1 (Scope v7 latest build),- I prefer using AES/EBU as sync source/destination,- regardless which is master or slave.
It works for both: RME = master/ XITE-1= slave or vice versa.
Then,- I use Z-Link for A16U (= slave always).
When Z-Link doesn´t work properly w/ XITE-1 and A16U, both as slaves w/ RME as master,- there´s ADAT for the A16U.
I didn´t try running A16U as Z-Link slave w/ XITE-1 as slave too.
Instead I´m using a master clock w/ XITE-1(slave) synced to AES/EBU and A16U (slave) connected via Z-Link.
XITE-1 and A16U both sync perfect.

[Bud Weiser]

wordclock in works.

Does BNC-WC In (XITE = slave) and A16U (slave) connected to XITE via Z-Link work too on your end ?



Bud

[mausmuso]

Hay Bud,
AES/EBU sync was the answer!
I have it working with the RayDAT as master and XITE as slave.
I am also slaving the A16 to RayDAT via BNC seems very stable now.
This setup also cured my issue with ADAT A crackling its brains out.
Thanks a lot for your input, I had not thought of using AES/EBU before.
regards
maus

[Bud Weiser]

Great to see it works for you and your setup !



Bud

[garyb]

my system is still based around PCI cards, since i have so many projects that use them. my XITE is clocked via ADAT from an A16mk2 which uses wordclock. it is true that the XITE clock in(slave) is faulty, there was a file that allowed wordclock slave, at the expense of wordclock master. i have not used that for some time. there is also an A16 Ultra cxonnected to the XITE, which is clocked via Z-Link.

clock is 100% stable on my system.

[mausmuso]

It is true that the XITE clock in(slave) is faulty.

Yes, I was able to get a stable clock via ADAT B as long as XITE-1 was the master.
For some reason ADAT A crackled constantly with this setup.
It was completely unstable with XITE-1 as slave.

The ADAT A issue has resolved itself now I have AES/EBU as the clock source and RayDAT as the master.
maus

[garyb]

i have found ADAT to be just fine, when it works. some devices just seem to be picky. i used to have a couple of Frontier AD/DAs, and one of them only worked as ADAT slave with my old PCI cards. the same AD/DA worked just fine with other devices slave or master. the other AD/DA worked as slave or master with all devices. i have seen this kind of thing several times. i usually configure to whatever is happiest.

[Bud Weiser]

i usually configure to whatever is happiest.

THIS !

I occasionally use all together:

Laptop #1 (Win10 Pro x64) w/ RME Babyface and native VST
Laptop #2 (Win10 Pro x64) for S|C SCOPE/XITE (64Bit) and A16U connected to XITE-1 as slave via Z-Link
HP server w/ SCOPE PCI (32Bit) and A16U connected as slave via Z-Link
Creamware Noah EX
Main DAW rackmount w/ RME Raydat w/ WC-module

In fact, everything except masterclock is slave.

Rosendahl Nanosyncs masterclock runs BNC wordclock "startype" to RME Raydat´s WC-module, SCOPE PCI w/ Syncplate and Noah EX.
In addition it runs AES/EBU Out to XITE-1 AES/EBU In (and it seems, there´s no need to load a AES/EBU source module in a project for perfect sync since I recognized it makes no difference if it´s present in a project or not).
No BNC T-connectors.

All the ADAT ports on PCI cards, XITE, Noah EX and Babyface are still free for audio interconnectivity across the systems.

Laptops, Noah EX and keyboards are in a different room, Main DAW/Raydat and HP server/SCOPE PCI are in the other room.
To interconnect rooms, I use 2 19"/1HU Appsys ADAT extenders (16 ports each) and freely configurable as ins or outs w/ dip-switches.
Both offer BNC connectors too and transmit wordclock and ADAT over 2 Cat5e cables running thru the wall,- which works for 100 meters max..

So,- masterclock runs BNC wordclock TO the ADAT extender #1 WC-In and from "in the other room" ADAT extender #2 WC-Out to whatever it needs (p.ex. 2nd SCOPE PCI 32Bit system,- WHEN I can find and get a 2nd syncplate).

The only device being synced via ADAT is RME Babyface on laptop #1 (see above).

Main advantage is usage of (relatively) short BNC and ADAT cables to and from ADAT extenders to end-devices.

MIDI over IP via network switch and rtpMIDI driver (and/or mac IAC) ...
I´m experimenting with to sort out which (ancient) MIDI interfaces nd acessories can go into the sales and which not.

Anyway,- for me, th sync stuff works as long nothing is broken.



Bud

[astroman]

... In fact, everything except masterclock is slave.

Rosendahl Nanosyncs masterclock runs BNC wordclock "startype" to RME Raydat´s WC-module, SCOPE PCI w/ Syncplate and Noah EX.
In addition it runs AES/EBU Out to XITE-1 AES/EBU In (and it seems, there´s no need to load a AES/EBU source module in a project for perfect sync since I recognized it makes no difference if it´s present in a project or not).
No BNC T-connectors.

Same here, but with Mutec MC-7 because Pro Tools 5 TDM needs „Superclock“ (x256)
Scope 7 w Syncplate, MPC4000, MacMini M1 (Motu 828MKII/USB), Alesis BRC, PT5 (Adat Bridge + Digi 888/24 and 882).
Before the Mutec the Mini M1 drove me nuts when simply Adat slaved

[Bud Weiser]

For "superclock" (x256) I kept the Nuendo Timelock Pro, which is also a very good "tape synchronizer" when a reel-to-reel tape recorder is master and a/the audio card is slave.
It also spits out MIDI timecode and variable sample rate related to tape wow and flutter etc..
In the past, I used w/ Fostex R-8 reel-to-reel and DAW (RME Hammerfall Digi9652), Cubase SX3,- later Presonus Studio One Pro.
Combining the Rosendahl Nanosync w/ Nuendo Timelock Pro is perfect since Timelock Pro in fact is a Rosendahl device too.
Will say: In addition to what´s described in my post above, integration of a tape recorder is possible too.
I still own the Fostex R-8, but rarely use nowadays.