All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Allan Klinbail <aklinbail@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: A&H Zed R16 not completely working (DICE Jr)
Date: Thu, 21 Apr 2016 11:11:12 +0900	[thread overview]
Message-ID: <571836C0.40605@sakamocchi.jp> (raw)
In-Reply-To: <CA+aoAJeOKtxGQXVKPLRYLO5KHMY7fDUZ4YKYHUUVyki_Sh3PBA@mail.gmail.com>

Hi,

On Apr 21 2016 09:14, Allan Klinbail wrote:
> Thanks Takashi ,
>
> It was my understanding that FFADO would eventually be deprecated,  so am
> trying to provide test feedback for my device.  I thought comparable
> performance would be a goal.

Your misunderstanding.

ALSA firewire stack is not an alternative of FFADO implementation. 
Against understanding of most of FFADO users, the implementation of this 
stack doesn't come from FFADO implementation, therefore they're based on 
quite different designs and code bases.

(It's your misfortune that FFADO project has already lost 
well-established developers who can explain about it.)

And you should realize that the decrease of size of PCM buffer is an 
ancient technique to reduce communication latency in a past decade. JACK 
developers still adhere on it, against their aim, unfortunately.  To 
understand this aspect, please read Alexander Patrakov's paper proposed 
in LAC 2015.
http://lac.linuxaudio.org/2015/papers/10.pdf

It's a bit difficult to you. But when thinking about the 'latency' 
severely, at least, users and developers should understand what in the 
article, at least. About the communication latency, I'm willing to use 
my time for this direction, but not for the others.

> Using ALSA is desirable as I have a large number of MIDI devices (2*AMT 8)
> and 3 other control devices..  Using ALSA provides better connectivity than
> a2jmidi..

What's the 'AMT'?

> I will try alsa in,  plug.. I am concerned though this is not an ideal
> solution due to trying to sync multiple devices which in reality share a
> clock..  Adding even more latency..

Even if using FFADO implementation, you can't achieve it. It pretends as 
what you say. Of cource, the size of PCM buffer is accumulated to the 
communication latency.

> I will continue using FFADO for production work,  but am happy to keep
> testing if you believe improvements can be made.

I haven no plan of my development for the direction about which you 
mentioned, sorry. There're more crutial issues than them.


Regards

Takashi Sakamoto

  reply	other threads:[~2016-04-21  2:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 14:31 A&H Zed R16 not completely working (DICE Jr) Allan Klinbail
2016-04-20 15:21 ` Takashi Sakamoto
2016-04-20 16:03   ` Allan Klinbail
2016-04-20 16:09     ` Allan Klinbail
2016-04-21  0:01     ` Takashi Sakamoto
2016-04-21  0:14       ` Allan Klinbail
2016-04-21  2:11         ` Takashi Sakamoto [this message]
2016-04-21  2:52           ` Allan Klinbail
2016-04-21  4:59             ` Takashi Sakamoto
2016-04-21  5:38               ` Allan Klinbail
2016-04-21  9:49                 ` Takashi Sakamoto
2016-04-21 21:16                   ` Allan Klinbail

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=571836C0.40605@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=aklinbail@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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.