[PROBLEM] pops and clicks between songs with Tidal Connect

[leonidp]

Hello,

I am enjoying very much the Moode on my setup, using Tidal Connect (installed from Git instructions) . The sound quality is super - probably also thanks to the direct driver mode used, however, causing some issues: pop-ups during the track changes, especially if the track's rate is not the same.
 
Wanted to ask if it possible to add some kind of “muting” option into the HW driver (may be GPIO toggling) to enable me to add the external muting relay circuit…

[Tim Curtis]

The symptom suggest an issue in the Tidal Connect add-in. You could try contacting the maintainer of the Git repo but due to the nature of the code the repo may not accept issues.

[Nutul]

The symptom suggest an issue in the Tidal Connect add-in. You could try contacting the maintainer of the Git repo but due to the nature of the code the repo may not accept issues.

The problem is more likely to be intrinsic in the (some, not all) DAC: when the bitdepth/samplerate changes between tracks, the DAC closes the stream => reconfigures it => opens the stream; and this produces the annoying clicks/pops.

You should experience the same problem if you play local tracks with different bitdepth/samplerate (provided MPD does not do some magic).
Can you try, just to be sure it is, or not, a Tidal-only problem?

For what I have been reading in the forums there are different solutions, like:
1. telling the DAC to keep the stream open (this is done via the driver, in Win environments)
2. muting the DAC when necessary
3. telling the DAC also "what comes next" (again, I think this is driver-related in Win environments)

Since MPD is not involved in the specific process (in this case streaming from Tidal) I believe it would be impossible to determine:
1. when a stream is close to its end
2. what the parameters of the new stream are *before it begins*
3. trigger some action in order to, at least, mute/unmute the DAC

I stand to be corrected, especially about MPD being or not part of the chain; nevertheless, even if it is involved, I doubt it can let us know what it is about to play next.
Assuming it is, we could eventually know when the stream ends, and trigger the MUTE/UNMUTE event unconditionally, but this would, at least. break the gapless playback, IMO (and this would be unacceptable, at least for me).

What DAC is it? Does it offer some configuration? What is this "direct driver mode", something specific to it, or moOde related (yep, I have no clue...)
Have you done some research on the relevant forums, about this issue?

[leonidp]

The symptom suggest an issue in the Tidal Connect add-in. You could try contacting the maintainer of the Git repo but due to the nature of the code the repo may not accept issues.

The problem is more likely to be intrinsic in the (some, not all) DAC: when the bitdepth/samplerate changes between tracks, the DAC closes the stream => reconfigures it => opens the stream; and this produces the annoying clicks/pops.

You should experience the same problem if you play local tracks with different bitdepth/samplerate (provided MPD does not do some magic).
Can you try, just to be sure it is, or not, a Tidal-only problem?

For what I have been reading in the forums there are different solutions, like:
1. telling the DAC to keep the stream open (this is done via the driver, in Win environments)
2. muting the DAC when necessary
3. telling the DAC also "what comes next" (again, I think this is driver-related in Win environments)

Since MPD is not involved in the specific process (in this case streaming from Tidal) I believe it would be impossible to determine:
1. when a stream is close to its end
2. what the parameters of the new stream are *before it begins*
3. trigger some action in order to, at least, mute/unmute the DAC

I stand to be corrected, especially about MPD being or not part of the chain; nevertheless, even if it is involved, I doubt it can let us know what it is about to play next.
Assuming it is, we could eventually know when the stream ends, and trigger the MUTE/UNMUTE event unconditionally, but this would, at least. break the gapless playback, IMO (and this would be unacceptable, at least for me).

What DAC is it? Does it offer some configuration? What is this "direct driver mode", something specific to it, or moOde related (yep, I have no clue...)
Have you done some research on the relevant forums, about this issue?

[leonidp]

The symptom suggest an issue in the Tidal Connect add-in. You could try contacting the maintainer of the Git repo but due to the nature of the code the repo may not accept issues.

Right, thanks! let me try...