This is the breakout cable for the 9652 card :

And this is the breakout cable for the RayDat

Not the same cable, I guess this is the reason for your issue.
The RayDat has AES outputs, the other card has not.

Yes the pinout of the 9652 is different. I have 9652 and 9632 and the breakout cables are not interchangeable.

Sorry, my bad, a google search found that answer from another topic.

Re: Pin out for SPDIF cable?
D-sub       Signal
1             SPDIF Out -
2             n.c.
3             ADAT Sync Clk In +
4             ADAT Sync TC In +
5             SPDIF In -
6             SPDIF Out +
7             ADAT Sync Clk In -
8             ADAT Sync TC In -
9             SPDIF In +

I'll try this asap... thanks for your help!

That was fast!
Have fun.
Oh what PCIe to PCI adapter are you using?

Made 2 short videos to show the issue better, that could be more clear :
https://drive.google.com/open?id=1If0zQ … p=drive_fs
https://drive.google.com/open?id=1ImLdp … p=drive_fs

Thanks for your help!

they are synched via wordclock with a bnc cable.
Settings page shows everything synched

Just did a fresh install of the driver downloaded from the website when I had the SPDIF issues yesterday.
(and firmware update)
Device manager shows same drivers for both cards and are active (I mean they show well, they appear in totalmix and show all the I/O in the DAWs)

Driver date : 18.10.2024
Version : 4.4.9.0

On both cards the same

Good call Sir !

There were 3 WDM devices on the Raydat, 0 on the 9652.. and that seems to work.. I need to test a bit further.

Now, I do still need windows sound somehow
But something to explore here for sure... I'll keep testing.

Thanks a lot for your help already !!

I'm still experiencing issues unfortunately with this setup.
It's kinda working but not stable and trustworthy enough for an everyday basis.

I sort of need to play with WDM devices to be turned off to have ASIO working, and I experience serious latency issues when I start to put some external devices (hardware fx) into the mix.
I can't really find the exact logic for it at the moment. But I'd love some help to troubleshot it.

If the mix Rayday + 9652 isn't really a good idea, I guess I should rather go for a double Raydat setup, but I wouldn't go for that yet if that's not going to solve the problem.
I'm keen for any idea here. Thanks

Thanks for the answer and the time taken for this topic.

I'm happy to give full precise details where it's relevant.

I don't think I lack giving useful information in this thread, I'm just trying to find the right thing to spot on at first and figure out where the problem may lay.
Waedi already managed to help me heaps by targeting the WDM devices to be an issue, I had no idea that could be the problem.

I have used more that one WDM device to do some routings for audio streaming, if WDM devices work as they should, they can be very useful to deal with apps like OBS, so if I need more than one, that is so.

Fact is that issues have been quite random and odd with this new double HDSP cards setup. I'll give all details needed when they count.

Main issues :
- WDM device would crash my ASIO, if a deactivate the WDM, ASIO would go well again.
- Latency, in simple test mode. I'm having one VST to just play a sound with my midi keyboard, all great. I add one external HWFX, send or insert, all ok! I add a second HWFX (connected to the second card), I have a latency of almost 1 second between my midi keyboard hit and the sound coming out. It's not here latency that needs to be measured in ms, it's a gap between all is working great and it's all lagging hard.
Both situations experienced in Ableton and Cubase. So I don't think it's DAW related.

I surely want to know my setup, and adding a new HDSP card stacked is a new thing for me for sure.
Just reporting my experience and wanting to find where the problem may lay.

UFX lll may sound like the big upgrade... but all my adat are connected to non-madi RME converters, so it's not only upgrading the main interface, but also the converters connected to it, which would definitely be a budget issue.
If the actual situation wouldn't get solved with another RayDat card, it's already a good info, thanks !

little edit : my answer here was referring to a post that has been deleted, some of this reply here may loose sense.

http://img4.imagetitan.com/img.php?imag … ure919.jpg
http://img4.imagetitan.com/img.php?imag … re2401.jpg
http://img4.imagetitan.com/img.php?imag … pture3.jpg

Here you go, thanks for your time !!

I have a Lavry Blue AD/DA converter that is generating the clock source for everybody.
Raydat is slave receiving the clock from the Lavry by SPDIF.
9652 receiving the clock by wordclock from RayDat (BNC cable)
Rest is connected by ADAT, slave to it's host.

maybe that's not correct and I'm happy to check different settings, but before adding the 9652, all was working great this way

Ideally, all toslink should go to AD/DA converters to use gears.
Dedicating 8 channels worth of analogue connexions just to sync the two cards would be a waste to my liking, wordclock should do the clock thing between the 2 cards, or?

Cool, I'll give it a go, see if changing who is master of the clock makes a difference.
I was never sure how to clock my 6-7 devices cards and gears, who should be the main master of the chain.
Thanks for your time again, so much appreciated, I owe each of you few rounds !

I haven't touched that thing yet... should I?

I'll need more time testing, right now everything works like a charm when WDM isn't interfering, it seems.

half a second latency is not"working like a charm" and it is not midi latency it is software latency, as you change buffer and the latency gets better.
This behavior with the buffer size setting is not normal, on wich card do you make this buffer action ?

And yes I would push the blue termination button.