[alsa-devel] Focusrite Scarlett 18i8 3rd Gen audio interface
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,
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.
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.
Regards, Geoffrey.
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,
participants (2)
-
Geoffrey D. Bennett -
wwp