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 2242 times

RayDat Settings.png (15.67 KiB) Viewed 2242 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.