driver 4.0.6.0
TM FX 1.08
On win7

It might sound old
Will see what updates are available now and post feedbacks

The HDSP9632 does not have the latest mixer engine like our newest interfaces where this 'zipper noise' is suppressed much more. Note that this noise is program dependent. You seem to listen to that kind of stuff where it gets easy to notice (strings, flutes, synth pads...). Others usually don't notice it at all.

Nothing to do, because the FPGA does not allow us to update the 9632's mixer engine for such an improvement, sorry.

That was one option I considered, but after some reading it appeared that digital attenuation seemed to sound better to many users. I'm not saying, just reporting my result of some researches.
I made a single knob with the right MIDI CC sent via arduino, for the same purpose as your passive potentiometer. Very handy for sure to have a pot next to your hand at any time.
It's all fine, just those crackles that I was wondering if it was possible to get rid of.

It does. I was already wondering...the 9632 is not that bad with zipper noise, as it has only a few channels. The 'old' HDSP 9652 has lots of channels, and  therefore can't render the smoothing efficiently.

Hello.

I've recently upgraded my system to a brand new computer and RME Raydat.
I'm still having clicking issues, not the exact same as before though.
Still a bit of clics when moving the master fader up and down (and as said earlier, depending on the material being played), but it's little.. no biggie here.
However when the I turn down the master fader all the way down rapidly, it generates a strong clic (only on my left side here) and it seems to occur only on the spdif out. I have other monitors connected via ADAT+ADI8 converters, and nothing to report there.
On totalmix, the clic appears and it varies between -15 and -5db.
Latest driver and firmware installed... winXP pro.

Any clue how to get rid of this ?
Thanks

Thanks for your answer.
Yeah, that could be a clock issue.. however everything seems super stable while using the setup, except those clics in this specific case (turning spdif out all the way down).. and yeah, they are loud !

Here is my setup :

Raydat SPDIF -> Trinnov ST -> Lavry Blue -> Speakers
Raydat SPDIF <- Lavry Blue <- AN Input
Raydat ADAT 1/8 -> RME Fireface (used as DA)
Raydat ADAT 1/8 <- RME Fireface (used as AD)
Raydat ADAT 9/16 -> ADI-8 DS
Raydat ADAT 9/16 <- ADI-8 DS
Raydat ADAT 17/24 -> ADI-8 DS
Raydat ADAT 17/24 <- ADI-8 DS

The Trinnov ST is an old version, that as actually an RME 9632 in it (or 9652, not sure).
The Lavry converter is M-DA 824

I can change pretty much any setting available on the Lavry, doesn't make any difference.
I tried to change the master clock device, to the Trinnov or the Raydat.. No difference with my issue.
I just didn't try to put the ADI-8 as master.. which wouldn't make sense to me.

If it was a clocking issue.. wouldn't it be more unstable locking / syncing ?

https://ibb.co/RySqh7w

Yeah, all clocks are showing "sync" without changing to lock. (I know that situation where two device were on internal clock)
2 WDM devices used. The thing that I have noticed with testing that, is that I must have audio content to play.. if there is no sound going to the output, there no clics.
Also double checked that it only happens on the SPDIF... no such thing on the adat outs.

I made a video to show...
https://drive.google.com/file/d/1vFLLvG … sp=sharing

Thanks for your help

Hey,
So, yeah it does the issue the same way with all WDM deactivated and only playing ASIO audio from Cubase.
Windows sample rate is set the same as the rest, 44.1kHz, 24bit.

Thanks for those inputs.. I'll check all this.. I'm just away for a little bit at the moment.
Cheers for your help on this, much appreciated.

Hi, lebarde!
You 're welcome!! Hope you had a good time!!

Some ideas came to mind!

About the encoder, I asked you because there are two types of functionality(that I 'm aware of).
If the communication with the encoder is bi-directional, one type is the "jump" to the value and the other is the "catch" the value.

The "jump" setting means that when you have the fader set to -30dB, for example, and the encoder is set to -40, when you touch the encoder the fader will jump to the -40 position, and then change to the new value.

The "catch" setting(in the same example) means that when you touch the encoder, no change will happen untill it reaches the -30dB value and after that it will change to the new value.

From the video, it looks to me that when you move the fader, quickly, TMFX is sending the new value(s) to the encoder and untill that calculation happens, the fader tries to jump to the encoder's previous value!
Of course all this takes place in milliseconds, but it 's enough time to create pops.

Can you try with the encoder disconnected?

The other idea is that maybe there is some conflict between TMFX and the Trinnov Control App, if they are using the same port for communicating with the encoder! If you are using OSC, that is!

So if you are using OSC, please post a screenshot of the OSC Settings of TMFX and the Trinnov Control App.
If it 's a Usb MIDI controller, post a screenshot of the MIDI settings!

And a link for the encoder, so we can check further!!

Quote from manual, page 55:

Can you un-check this option?

Even if it 's not the encoder, I think that there is a midi mis-communication, somewhere..!
It does the pops by moving the fader, but did you try moving the fader with the encoder disconnected?

Hi, lebarde!

This option is enabled in your midi settings, under "Mackie Control Options".
And since the SPDIF Output is Stereo, I thought that by disabling it, it might fix those pops!

Hmm, if it 's not midi related, we 'll have to look elsewhere! Thanks for checking!
At least, we can rule out midi settings!

I 'll think some more about it, and come back for more testing suggestions, untill we find out what 's happening!

Hi, lebarde!

You 're welcome!!
I haven 't forgotten about your thread!
I 've been extremely busy all this time and I couldn't find some time to actually sit and think about this!

When things ease out a bit, I 'll post back!!

Hey man,

I missed the notification of your last message..
I was much expecting that it would help... but still not.
Additionally, I figured out that it does the issue only on the left side.
If I put the master pan pot fully to the right, I don't have any problem there. Really just on the left side.
Isn't that weird ?!

I hope I can get that fixed sometime soon.. it starts to bother me more.. and I get a bit scared that it affects my tweeters.

https://ibb.co/7X0dJL7

Totally no funny routing going on.. no loopback nor MS processing here.
SPDIF is via the breakout cable, going by coax cable to the trinnov unit.

I just tested again to have the trinnov as master clock and the raydat as slave, and vice versa... same problem on both settings.
I could try via wordclock maybe...

Hi MC,

Yes that is still the topic. But at the start it was with the hdsp9652, now it's with a recently purchased raydat.
With the 9652 it was small crackles when moving the fader, now it's a seriously hard click when turning the master fader all the way down.

Here is a video showing the issue
https://drive.google.com/file/d/1P3Nstb … sp=sharing

Happens only on spdif left out. I have another set of monitors connect via ADAT to a ADI8, and nothing happens there.
I does happen only when there is audio played. (either from a basic media player or from a DAW)
I can't seem to see any DC signal that would cause that. I guess a DC signal would be present also if I don't play any sound.

Hi, lebarde!

I 'm sorry, but I 'm out of ideas..
Perhaps, you could use DigiCheck and its "Bit Statistic & Noise" function, to check if there is any DC Signal on the Output.

Does the noise appear with all types of music? Did you try with classical recordings or single instruments(like classical guitar)?

No, I don' t think this is normal! Poorly mastered material, usually, have DC offsets. But I 'm no expert on EDM, so I could be wrong, here..!

Here's a recent thread on the ADI 2 section of the forum:  https://forum.rme-audio.de/viewtopic.php?id=34265
Have a read on KaiS' post #2!

> I just did a test playing a track with a low cut EQ at 1500kHz, the DC value shown by digicheck here is 150dB.. clicking still occurs very loudly.

If you total reset TM FX, so only default routings and no FX at all, is that click then identical to that of the 1.5 kHz low cut test?

So let's try to get to the bottom of this. I have a RayDAT here under Windows, current firmware 207 and driver 4.38. I play back a music track (on the first two channels, ADAT 1/2) at 44.1 kHz, internal clock, nothing else connected to the card, and route the signal to the SPDIF output. I connected an ADI-2 Pro to receive the SPDIF coaxial signal and monitor it this way.

Now I move the fader in the third row for SPDIF to the bottom - no click. No matter if SPDIF is in the left or right Control room pane.

Your video shows SPDIF input signal, an active fader group and that the click is even shown on the level meters. That's why I asked for a Total Reset which would equal more my simple test case.

So what's still different in your test setup? And please reproduce mine.

You can easily reproduce the test. The Trinnov can be used as DA, just make sure it is not connected to send a signal to the card. This way a click that is even visible on the output level meters can not come from the Trinnov.

BTW, does it also do the same click when using the output fader's Mute button whith the fader at 0 dB?

I've tried the following :

Connecting the Raydat to the Lavry in SPDIF, completely removing the trinnov from the chain => Same issue
Connecting the Raydat to the Trinnov in SPDIF, completely removing the Lavry from the chain => Same issue
Both situations with each device as master or slave for the clock

Edit, after rethinking my test setup and putting everything back together, I redid a test by simply disconnecting the SPDIF input from the raydat and making the raydat as the master clock.. so the raydat surely doesn't get a signal from the other device.
Still confirming the problem..

That could be cool to try for sure..
I'd have another option to test on this computer :
- I have my old 9652 card that I could plug with a PCI to PCIe adapter and see what it's like.
(if that makes sense, rather than replacing the card + shipping ..etc)

But, also, I'm off now for a tour in Mexico.. I'll have to continue this investigation in february...
Will come back to this topic then.. thanks for your help so far.
Happy new year !