From: wwp <subscript@free.fr>
Cc: alsa-devel@alsa-project.org
Subject: [alsa-devel] Focusrite Scarlett 18i8 3rd Gen audio interface
Date: Sun, 13 Oct 2019 10:20:30 +0200 [thread overview]
Message-ID: <20191013102030.50d7c8d0@ladybug> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1035 bytes --]
Hello,
I've recently bought a Focusrite Scarlett 18i8 3rd Gen audio interface,
great device, but in CentOS 7, with either the available 3.x or 4.x
kernels, the device just appears in the available Alsa devices, but no
mixer is available, the device direct hardware monitor output is also
not working (it is, by default, and works well in Windows, but I
presume that w/ no mixer support in Alsa, it's expected that nothing
works). I'm able to bound I/O ports in QJackCtl but nothing goes out of
the device.
Of course, adding the 0x1235:8214 USB ID to the quirks just doesn't
work. I presume there's more work like the patch submitted here (I saw
the archives) in the "[PATCH RFC V2] ALSA: usb-audio: Scarlett Gen 2
mixer interface" mail thread?
Do you it is worth trying applying that 2nd Gen patch to one of the v4
kernel available for CentOS 7, adding the 3rd Gen quirks and see how it
behaves? Or is there already progress on supporting the 3rd Gen one too?
Regards,
--
wwp
https://useplaintext.email/
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2019-10-13 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 8:20 wwp [this message]
2019-10-14 13:40 ` [alsa-devel] Focusrite Scarlett 18i8 3rd Gen audio interface Geoffrey D. Bennett
2019-10-15 18:13 ` wwp
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=20191013102030.50d7c8d0@ladybug \
--to=subscript@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox