with 6 inputs crackles at higher sample rates

[jksuperstar]

If you make contact with him, be sure to post back any suggestions or fixes for others here!

[garyb]

this shouldn't be so hard. we just need to make sure that it works correctly, to begin with.

[Ambient Source]

feel free to write to support. i can arrange an RMA for testing.

At the moment the Xite is my main audio interface and I'm really busy with some projects.
so there' no way i can RMA it at the moment.

but hopefully someone will figure out whats wrong

[garyb]

there is NOTHING wrong with the XITE-1 and the A16 Mk2, in general. both work together fine. i have PCI cards, an XITE-1 and a couple of A16 Mk2s. no problems...

[Ambient Source]

I have the Xite 1D and the A16 ae.

I'm not saying there is any defect with the Xite or the A16.

I just can't connect the 2 together, if the Xite is master no lock, If the Xite is slave I get a spinning cursor and crackles from adat ports,
but everything works fine with the Scope PCI system in between the 2,same cables used, ports clean, correct setup.

It's just really confusing

[jksuperstar]

(posted about using z-link, but you have an A16 mkII, so that won't help...)

[garyb]

i believe that you have encountered a problem, but there aren't any fundamental problems between those two units. none.

[garyb]

yes, it was perfect here.

that's very troubling...

[t_tangent]

Not sure if this helps you but thought it was worth mentioning. I have my older Scope PCI cards connected via ADAT to my XITE-1. When I have both Scope PCI OS and Scope XITE OS running and then connect ADAT Modules from XITE to PCI I sometimes get crackling on one of the ADAT ports, sometimes even on both. I usually have Scope PCI set as ADAT master (samplerate 48KHz) and XITE as ADAT slave. But I found that if I change Scope PCI to ADAT Slave and Scope XITE to ADAT master and then wait a few seconds, then even if I switch back, the crackling has gone. This works for me.

I figure its worth a try just in case. Hope that helps. Also check the XITE PCIe card is correctly seated in the motherboard

[garyb]

wow, that really upsets me(i'm sure it upsets you more!)!
i don't know what to say. your XITE handled ADAT exactly as it should here...

[garyb]

bnc should be better than lightpipe, but both should be click-free.
also interesting that it works with other ADAT devices...

[garyb]

yeah, i never saw that behavior.
i think we need to exchange some emails.

[ronnie]

Have you tried increasing the latency in ULLI settings? Sounds like an audio latency issue, not a sync issue. BNC works because there's no audio sharing the pipe? Just a wild hunch. Jus' sayin'.... Sync issues would be really jitter and timing but crackles would more likely be latency or IRQ ot IO type stuff related like network, USB, video hardware, software and/or drivers. Not to knock DSP in the least but CPU power would also figure into the latency soup. Have you run Latency Mon to see what's sucking your CPU cycles? Could be something basic or weirdly unique to your PC like hardware or drivers from chipset, network, video or other audio etc. I only say these things because I don't see this obvious stuff being addressed. Likely you've checked and adjusted them. Clue is issue seems related to CPU being busy as you say. Real time shit like audio and sync and video suffers competing for cycles limiting your low end latency numbers. Bump up the milliseconds to increase the audio buffers. Can't hurt. Again, you've probably done all this so I'll put my ears down, eyes up and tail between my legs. Rolled over and out. Sigh.

[ronnie]

Ouch! I've had my share of inexplicable ADAT sync issues between different boxes. I generally avoid it if possible or put on different pipes than audio but even so..........pfft

[53E7]

I had this problem with my XITE-1. Try to connect out AES/EBU from A16 to the input of the XITE-1 and select AES/EBU to sync to. If that doesn't work reverse. Audio will still go through ADAT. Syncing via AES/EBU worked for me.

[53E7]

I looked at a picture of the A16 MKII and noticed it has wordclock. The XITE-1 has wordclock as well. I (embarrassingly) don't know very much about wordclock, but if I understand correctly, it is for syncing, and I think your problem stems from bad syncing. I'd get 2 BNC cables and try that. I'll bet that will give you rock solid stability and completely eliminate the crackles and dropouts.

[53E7]

Sorry, I came late to the party. I didn't read the whole thread.

[ronnie]

Hmmmm.... re-install Scope drivers? Check for duplicate Scope files? Don't see this being done in the thread.

[garyb]

that happens consistently?

ADAT A or ADAT B means absolutely nothing to Windows. period.

if it were a problem with scopexite.sys everyone would have that problem.
there must be a reason for this...

[garyb]

ADAT A and B are just representations in the gui. nothing that they do takes place in Windows. Windows does not know which are connected or not connected. not at all. the driver isn't concerned with the ADAT i/o in any way. i can't think of anything else other than clock issues, but i don't understand why LatyencyMon would respond that way. maybe clock errors set off alarms in LatencyMon. do you have all 4 lightpipe cables connected at all times? sometimes clock is better transmitted on one or the other ADAT port. i've had this issue with the PCI cards in the past. if all 4 cables aren't connected, it's not possible to try the other ADAT port for clock. the clock signal doesn't have to be on the same cable as the audio data.

if you are using 8 channels from the A16 and 8 channels from another piece of hardware, then you should be using an external wordclock generator/distributor.

i realize that i'm probably giving advice that you have already experimented with, but i guess it the best i can do. in any case, it's pretty much impossible for you using one ADAT port or the other to do anything in Windows, even if that's what you are seeing. there's something else happening.