From: Melvin Vermeeren <mail@mel.vin>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: dice: add stream format parameters for Mytek devices
Date: Tue, 19 Jun 2018 20:23:24 +0200 [thread overview]
Message-ID: <2029377.pJKpRF2PWc@melvin-pc> (raw)
In-Reply-To: <3387264.iPd986TAIQ@melvin-pc>
[-- Attachment #1.1: Type: text/plain, Size: 1819 bytes --]
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.
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-06-19 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 19:00 [PATCH] ALSA: dice: add stream format parameters for Mytek devices Melvin Vermeeren
2018-05-18 2:54 ` Takashi Sakamoto
2018-05-18 20:01 ` Melvin Vermeeren
2018-05-19 8:23 ` Takashi Sakamoto
2018-05-21 15:09 ` Melvin Vermeeren
2018-06-07 14:40 ` Melvin Vermeeren
2018-06-19 18:23 ` Melvin Vermeeren [this message]
2018-05-18 6:56 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2029377.pJKpRF2PWc@melvin-pc \
--to=mail@mel.vin \
--cc=alsa-devel@alsa-project.org \
--cc=o-takashi@sakamocchi.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.