alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Allan Klinbail <aklinbail@gmail.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>, alsa-devel@alsa-project.org
Subject: Re: A&H Zed R16 not completely working (DICE Jr)
Date: Thu, 21 Apr 2016 00:14:44 +0000	[thread overview]
Message-ID: <CA+aoAJeOKtxGQXVKPLRYLO5KHMY7fDUZ4YKYHUUVyki_Sh3PBA@mail.gmail.com> (raw)
In-Reply-To: <57181862.6060501@sakamocchi.jp>

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.

It was late last night when I was testing so I apologise if I sounded
ungrateful.

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..

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..

I will continue using FFADO for production work,  but am happy to keep
testing if you believe improvements can be made
On Thu, 21 Apr 2016 10:01 am Takashi Sakamoto <o-takashi@sakamocchi.jp>
wrote:

> Hi,
>
> On Apr 21 2016 01:03, Allan Klinbail wrote:
> > It provides this as separate devices so I cannot access all channels at
> > the same time in jack as in FFADO.
> >
> > Although I don't typically use the ADAT ports other might, however I am
> > always using a combination of channels 1-16 and channels 17 & 18
> > combined, sometimes all of them.
> > The device is a hardware mixing desk and all ports are designed to be
> > used simultaneously..
>
> Use 'alsa_in' and 'alsa_out' as JACK clients, to use several ALSA PCM
> character devices in one JACK session. See:
> http://jackaudio.org/faq/multiple_devices.html
>
>
> > Latency performance is also much worse. FFADO will allow a buffer size
> > of 64, ALSA will not start below 256.
> > I prefer to work at 128 or lower.
>
> If you think that FFADO implementation is suitable to your usage, and
> you believe that it's really proper for IEC 61883-1/6, please use it.
> ALSA firewire stack is just one of your available options in Linux-based
> system.
>
>
> > root@kxdaw:/home/allan/Downloads#  cat /proc/asound/card1/dice
> > sections:
> >   global: offset 10, size 95
> > ...
> > global:
> > ...
> >   version: 1.0.11.0
>
> Hm. The global register has 95 quadlets. It has extra 5 quadlets as what
> we know. What information is in the extra fields, I don't know exactly,
> but I can confirm it in my Focusrite Saffire Pro 26 (interface version
> 1.0.12.0).
>
> On Saffire Pro 26:
> $ cat /proc/asound/card1/dice
> sections:
>   global: offset 10, size 95
> ...
> global:
> ...
>   version: 1.0.12.0
>
> $ ./firewire-request /dev/fw1 read 0xffffe0000190 14
> result: 000: 00 00 00 07 00 00 00 02 00 00 00 00 00 00 00 00
> result: 010: 00 00 00 00
>
> In short:
> 0x'ffff'e000'0190: 0x00000007
> 0x'ffff'e000'0194: 0x00000002
> 0x'ffff'e000'0198: 0x00000000
> 0x'ffff'e000'019c: 0x00000000
> 0x'ffff'e000'01a0: 0x00000000
>
> If you can't have enough consideration about this kind of work, I'd like
> you to use FFADO, by blacklisting snd-dice, please.
>
>
> Regards
>
> Takashi Sakamoto
>

  reply	other threads:[~2016-04-21  0:14 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 [this message]
2016-04-21  2:11         ` Takashi Sakamoto
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=CA+aoAJeOKtxGQXVKPLRYLO5KHMY7fDUZ4YKYHUUVyki_Sh3PBA@mail.gmail.com \
    --to=aklinbail@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).