From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Mathias Buhr <napcode@apparatus.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: snd_dice: Clicking artifacts with TC StudioKonnekt 48
Date: Mon, 24 Feb 2020 09:20:32 +0900 [thread overview]
Message-ID: <20200224002031.GA10405@laptop> (raw)
In-Reply-To: <e29617da-9d34-c99f-f425-5d2aef59b623@apparatus.de>
Hi,
On Sat, Feb 22, 2020 at 05:49:29PM +0100, Mathias Buhr wrote:
> Thanks for your reply Takashi! It clarifies the situation. I'lll stick
> with ffado then.
>
> Regards,
>
> Mathias
Both of libffado2 and ALSA dice driver have problems for each, but it's
a convenient option for users of Dice-based devices to use the former,
at present. I've been improved ALSA dice driver for years with the other
drivers, but it doesn't bring so hasty changes since it's a kind of
reverse-engineering; no one knows the actual design and few ones can
make discussion based on the fact.
Well, I also own TC Electronic Sudio Konnekt 48 and I've investigated
its protocol to configure I/O routings on internal DSP. After my
vacation, I'll send information about it for your convenience
(maybe next week).
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2020-02-24 0:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 20:34 snd_dice: Clicking artifacts with TC StudioKonnekt 48 Mathias Buhr
2020-02-22 1:25 ` Takashi Sakamoto
2020-02-22 16:49 ` Mathias Buhr
2020-02-24 0:20 ` Takashi Sakamoto [this message]
2020-02-26 12:51 ` Mathias Buhr
2020-03-18 6:22 ` Takashi Sakamoto
2020-05-06 15:56 ` Scott Bahling
2020-05-07 13:38 ` Takashi Sakamoto
2020-05-07 14:41 ` Missing frames on Tascam FW-1884 (was Re: snd_dice: Clicking artifacts with TC StudioKonnekt 48) Scott Bahling
2020-05-10 13:58 ` Takashi Sakamoto
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=20200224002031.GA10405@laptop \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=napcode@apparatus.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox