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.
regards
maus
Xite-1 Word Clock
Re: Xite-1 Word Clock
"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).
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).
Re: Xite-1 Word Clock
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
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
Re: Xite-1 Word Clock
wordclock in works.
- Bud Weiser
- Posts: 2886
- Joined: Tue Sep 14, 2010 5:29 am
- Location: nowhere land
Re: Xite-1 Word Clock
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.
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
- Posts: 2886
- Joined: Tue Sep 14, 2010 5:29 am
- Location: nowhere land
Re: Xite-1 Word Clock
Does BNC-WC In (XITE = slave) and A16U (slave) connected to XITE via Z-Link work too on your end ?

Bud