All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Gareus <robin@gareus.org>
To: alsa-devel@alsa-project.org
Subject: Focusrite Scarlett 18i6 mixer
Date: Fri, 18 Jan 2013 05:05:15 +0100	[thread overview]
Message-ID: <50F8C9FB.3010200@gareus.org> (raw)

Hi,

I've started to reverse engineer the 18i6 mixer protocol and came up
with a proof-of-concept test script which includes documentation:

  https://github.com/x42/scarlettmixer

Except for a few fixed controls and switches, the 18i6's mixer and
router is [likely] too complex to be exposed via ALSA's mixer interface.
AFAICT it'll require a dedicated control application - like hdspmixer -
in order to make full use of it.

The current proof-of-concept uses pyUSB to send URB control messages and
therefore requires root access. It will also not work while the device
is in use (by snd-usb-audio). A dedicated ioctl interface - similar to
SNDRV_HDSP_ - should be added to ALSA. However, it is yet unclear to me
how much of the protocol should be moved to kernel-space.

Anyway, the script can be used to configure the device, save settings to
it and subsequently use those settings with snd-usb-audio and Martin's
patch.

Thoughts, comments?
robin

PS. the same protocol may apply to other Focusrite Scalett USB2 devices
such as the 8i6 - some of the factory-reset traces hint at that, but I
would not know.

             reply	other threads:[~2013-01-18  4:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18  4:05 Robin Gareus [this message]
2013-01-20 19:25 ` [patch] 18i6 mixer implementation -- was Focusrite Scarlett 18i6 mixer Robin Gareus

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=50F8C9FB.3010200@gareus.org \
    --to=robin@gareus.org \
    --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.