Hello Takashi,

Have you discovered any news regarding the timing issue in DICE or anything 
else from my previous email? I noticed in your recent commit 
1ceb506d631f512f8e5b04821c21104b80c15dee, you referred to an email with 
details from 2016[1], leading me to do some experimenting.

On Thursday, 7 June 2018 16:40:21 CEST Melvin Vermeeren wrote:
> Do you have a suggestion for anything I could try to either resolve the
> issue or how to provide additional information?

I have ported the "old modules" from my initial email[2], which is commit:

2eb65d67afbf9364b525b657f1475d1a2cbc27de
ALSA: dice: expand timeout to wait for Dice notification

to my current kernel, 4.16.12-rt5-1-rt. Then I did a quick hack to correctly 
identify the Mytek's channel mapping for this old driver. I found that both 
PCM and DSD over DoP now work perfectly, though sometimes it misses the lock 
as described in the initial mail. I have been playing back DSD over DoP for 
over 30 minutes so far with zero drop-outs or other issues. This is not 
possible with current DICE.

I must conclude that the packet sequence quirk described in your email is not 
the same issue that impacts the Mytek, since that this quirk exists since 
kernel 3.13 and in my initial email there were no problems with kernel 4.4. 
Though I must admit I do not know where the current problem comes from.

Please let me know if there is anything I can do to further diagnose the 
problem with current DICE.

[1] [alsa-devel] Dice packet sequence quirk and ALSA firewire stack in Linux
4.6 http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html 
[2] [alsa-devel] DICE Stereo-192-DSD-DAC issues since 2016-02-08 / kernel >= 
~4.6
http://mailman.alsa-project.org/pipermail/alsa-devel/2017-September/
125524.html

Thank you,

Melvin Vermeeren.