From: wwp <subscript@free.fr>
To: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Focusrite Scarlett 18i8 3rd Gen audio interface
Date: Tue, 15 Oct 2019 20:13:35 +0200 [thread overview]
Message-ID: <20191015201335.0927bc87@ladybug> (raw)
In-Reply-To: <20191014134028.GA11018@b4.vu>
[-- Attachment #1.1: Type: text/plain, Size: 2310 bytes --]
Hello Geoffrey,
On Tue, 15 Oct 2019 00:10:28 +1030 "Geoffrey D. Bennett" <g@b4.vu> wrote:
> Hi wwp,
>
> On Sun, Oct 13, 2019 at 10:20:30AM +0200, wwp wrote:
> > 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.
>
> Is any of the class-compliant functionality (play/record) working at
> all in CentOS 7? I would expect that out of the box you should be able
> to get standard ALSA/PulseAudio apps working for I/O.
I tried, nothing, maybe not tried right or enough.
> > 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?
>
> Yes, there would definitely be more work to do along those lines. If
> we're lucky, the protocol is basically the same as 2nd gen and just
> extended for the additional features in the 3rd gen. FWIW, I haven't
> heard of anyone starting that work.
>
> > 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?
>
> I doubt that it would do much useful beyond letting you know if it
> accepts the same initialisation sequence as the 2nd gen devices. If
> you want to send me (off-list) a wireshark USB capture from 1) the
> Windows driver initialising your device and 2) you adjusting settings
> in Focusrite Control, I can have a look at it and let you know if it
> looks similar to the 2nd gen devices.
I tried -> broken pipe. IOW, it doesn't work, not as simple as doing as
if the 3rd gen was a 2nd gen.
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
prev parent reply other threads:[~2019-10-15 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 8:20 [alsa-devel] Focusrite Scarlett 18i8 3rd Gen audio interface wwp
2019-10-14 13:40 ` Geoffrey D. Bennett
2019-10-15 18:13 ` wwp [this message]
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=20191015201335.0927bc87@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