All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: roberto lopez torres <lotojr@live.com.mx>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Duet Firewire
Date: Mon, 17 Feb 2020 07:58:53 +0900	[thread overview]
Message-ID: <20200216225852.GA3783@workstation> (raw)
In-Reply-To: <BYAPR10MB36861118D3D6AF53A14C801E98170@BYAPR10MB3686.namprd10.prod.outlook.com>

Hi,
(C.C.ed to alsa-devel)

On Sun, Feb 16, 2020 at 03:52:27AM +0000, roberto lopez torres wrote:
> Hi, i just got a Duet Firewire, and i'm trying to make it work with 5.3.0-29-gen
> eric #31-Ubuntu
> 
>    I have inputs and outputs from the interface but can't config anything
>    at the moment, and i got a noise every 16 seconds on headphones
>    monitoring.
> 
>    I'm pretty new using linux.

The ALSA support for Apogee Duet FireWire starts at Linux kernel v4.21.
As you can see, the support is just for packet streaming, thus it's just
possible to transmit/receive PCM frames and MIDI messages. However, the
device is designed to run just depending on its internal clock (e.g.
47994 frames/sec), thus at present it generates periodical noise since
the ALSA driver is designed to transmit just the same number of PCM
frames as sampling rate (e.g. 48000 frames/sec).

The support of any control is expected to be implemented in userspace
application. This is the reason that you can see no elements in ALSA
control application (e.g. alsamixer). However, the protocol to control
the device is not clear yet. As long as I know, it's complicated and
requires the batch of codes for the application. This is the reason
that ALSA in-kernel driver doesn't have the code.


Regards

Takashi Sakamoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

           reply	other threads:[~2020-02-16 22:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <BYAPR10MB36861118D3D6AF53A14C801E98170@BYAPR10MB3686.namprd10.prod.outlook.com>]

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=20200216225852.GA3783@workstation \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=lotojr@live.com.mx \
    /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.