From: Melvin Vermeeren <mail@mel.vin>
To: Pascal Bomel <bomelp@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Dice firewire support
Date: Fri, 22 May 2020 13:36:13 +0200 [thread overview]
Message-ID: <4243350.MNUmLrt7UK@verm-r4e> (raw)
In-Reply-To: <CALic0i3=qUMQxK_E1oFA_=K0+ABk0LJwF3hGZumA0nU8PQV4tw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2206 bytes --]
Hi all,
On Friday, 22 May 2020 11:07:06 CEST Pascal Bomel wrote:
> Thank you so much Takashi.
> Actually i have a debian 4.9.12 "stretch" release with 4.9.211 kernel
> version (uname -v)
> This kernel has snd-dice module inside isn't it ?
> I am not very familiar with linux, that's why i appreciate your help.
You can either upgrade to Debian buster, which has 4.19, or install a kernel
from stretch-backports, which is also 4.19. Assuming you have amd64 hardware
that would be https://packages.debian.org/stretch-backports/linux-image-amd64.
See also https://backports.debian.org/Instructions/ for more instructions.
Some background information below, from how I remember things. Do note that
there were many details and I may be mistaken about some of them.
At the time of 4.18 there was some issue with the timing that caused non-bit-
perfect playback, resulting in audio artefacts that were hard to detect as it
was near perfect. DSD over PCM (DoP) mode however made it very obvious this
issue existed, as it would not work reliably at all. It was also noticeable
when listening to a fixed Hz tone, it wasn't perfectly smooth.
I believe there was some significant refactoring going on with snd_dice at the
cause, which caused some previously working things to stop working as snd_dice
became more compliant with device's listed features and protocols.
Older versions "just sent a new stream" when frequency changed (iirc), which
actually caused the DAC to sometimes not catch the signal and made it silent.
You then had to restart jack (or ALSA stream) a few times. The new version
used proper lock mechanism (AMDTP?) meaning it worked 100% of the time, except
for the non-bit-perfect issue.
Since those days of experimenting I have been running snd_dice and
snd_firewire_lib from sound-4.4-rc7-692-g2eb65d67afbf out of tree, with minor
patches to make them compatible with modern kernels and overrides for the DAC.
Thanks for the mention Takashi, I appreciate it. Since I am running 5.5.17
(buster-backports) kernel right now I will do some testing later today to see
if there are still any issues in this version, the Mytek is still used daily.
Cheers,
--
Melvin Vermeeren
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-25 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <276893435.728967.1590133905081.JavaMail.administrator@n7.nabble.com>
2020-05-22 8:10 ` Dice firewire support Takashi Sakamoto
2020-05-22 9:07 ` Pascal Bomel
2020-05-22 11:36 ` Melvin Vermeeren [this message]
2020-05-24 0:24 ` Melvin Vermeeren
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=4243350.MNUmLrt7UK@verm-r4e \
--to=mail@mel.vin \
--cc=alsa-devel@alsa-project.org \
--cc=bomelp@gmail.com \
/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.