anyway it’s strange, because I tried on andorid without any problems, even on windows with foobar2000 no problems, but on volumio it seemed to me sound is better than the others
not knowing the details on the ComTrue firmware they developed, it’s impossible to narrow down where the problem is.
With the firmware I developed for the ComTrue CT7601, feeding I2S audio stream to ES9038 DAC, I have absolutely zero problems with bot PCM and DSD playback on Linux, including the PCM ↔ DSD transition.
Of course, thanks for the clarification.
One thing that bothers me, similarly as also noted by @mastri81 the problem is only with Linux, and in Windows it works fine.
If it was a firmware issue, CT7601 and ES9038 communication, shouldn’t it show up on both?
This does not only apply to Volumio, if you use any Linux-based player you will face the problem.
not necessarily, Windows and Linux handle the USB Audio stack in a different way
I don’t know if it can help, but on Windows to avoid “pop” when changing tracks I had to decrease the latency times from 20ms to 5ms.
I checked it out. It did not solve the problem for me.
Maybe I typed something in the wrong place, this is also possible.
It is then how your firmware could be uploaded if it is proven and works perfectly…
what is the standard buffer time used by volumio when changing tracks?
maybe that’s the problem!
No idea 
Have you found what this buffer is?
What I can tell you, I have checked all possible combinations of settings in Volumio.
I’ve made manual changes to the configuration files, I’ve checked the USB Power management, I’ve disabled USB Autosuspend.
I entered Latency and Mute during spl. rate change into
/volumio/app/plugins/music_service/mpd/mpd.conf.tmpl
and it didn’t change anything. Unless I typed something in the wrong place, that should be considered too.
By any chance and out of curiosity, have you tested any other linux distributions including RPi OS with your dac/amp and DSD + FLAC files?
Yes, I have tested MoOde, PiCore and Audirvana Linux coreplayer. I also tested them on different platforms, RPi4, Dell Wysse, 2 two Dell Latitude that I found at home.
In all cases there is the same problem.
Looking at how Volumio behaves, maybe that would be a way around this problem.
By introducing a letancy and mute with a procedure like this:
when pressing ‘Play’ → Mute → Pause → letancy ~50ms → previous track (jump to beginning) → Unmute.
Unfortunately I do not find such options in Volumio.
No idea how to do it. Maybe create some plugin, but that’s beyond my skills.
Hi. At this point and even more so because you’ve found the same behavior on various Linux distributions in X86 and ARM forms; its best to contact and request that the manufacturer performs further multi-platform tests and updates the device firmware accordingly.
Like @darmur mentions here and in the parallel thread, it’s specific to their implementation and perhaps how ALSA behaves or what it expects.
You are correct.
From Emotiva’s perspective the XDA-3 is capable of playing both DoP and “native DSD” when it receives them. However, since those are both “standards” it is up to the source device to provide them if it chooses to do so. (Emotiva provides a driver for Windows… and I believe that some Windows and Apple player programs may support them “internally”, but Emotiva does not provide Linux drivers for either.)
Please note that, in the context of USB audio, “DoP” is DSD audio encapsulated and contained in USB audio packets - so “DSD-over-PCM-over-USB”, and “native DSD” is simply a very slight variation of this. (With “native DSD” the packets are structured to take better advantage of the available USB bandwidth… )
However it is still up to the source player program or operating system to encapsulate the DSD audio stream into the PCM packets to be sent…