Focusrite scarlett solo linux

Hey guys, don’t know where to turn because the issue I’m having is very specific, and I’ve tried to official #ubuntu irc but have gotten no help.

Backstory: I got tired of having constant audio issues with my thunderbolt dock/bluetooth/whatever and I also wanted to get a nice microphone (SM-57) so that people don’t hear my IBM Model M on all the phone calls (especially now that I take 3x as many due to the pandemic). I’m not trying to do any professional audio work, but I do occasionally record instructional videos for my business. I tried qjackctl for a while and went down that rabbit hole but realized I *probably* don’t need that quite yet. So I’m just using pulseaudio.

Thinkpad p52s Lenovo Thunderbolt 3 dock Focusrite SM-57 + Wired Headphones

Side Note: I have tried plugging the Focusrite directly into a USB port on my laptop to try to get rid of one more moving part (the dock) but that introduces a new issue: tons of background static noise, music comes through very clear though. Someone mentioned that this could be related to the USB port not supplying enough power?

Back to the issue at hand though. When the Scarlett is working, everything is great, but suddenly audio output completely goes out on me. I’ve tried watching the syslog via dmesg, and journalctl to see if there is anything related to a usb device disconnecting or some kind of crash, but I have seen absolutely nothing. pulseaudio -k works at resolving this issue, but it creates substantial problems for a number of applications which then need to be restarted. The simplest solution I have found is to unplug and replug the USB cable to the Scarlett which immediately starts working again.

I’m kind of lost at this point about what to look for and was hoping people with more experience with this type of equipment could potentially point me in the right direction.

Источник

LinuxMusicians

Focusrite Scarlett Solo Gen 3 on Ubuntu 20.04

Still new to all of this? Feel free to post in any of the subforums on this site, but in this subforum newbie questions are especially encouraged!

Focusrite Scarlett Solo Gen 3 on Ubuntu 20.04

Post by Torrino » Thu Oct 15, 2020 11:38 am

First of all I greatly apologize if this isn’t the place to ask this or if someone had already asked this (I searched the forums and couldn’t find an answer).

Hi everyone, I’ve been a musician for the past 12 years but a Windows user for a lifetime. and I have finally decided to switch to Linux.
I’ve always wanted to switch to Linux but never got to do so and now that I’ve finally decided to make the switch, I’ve realized that there’s no official driver support for my Focusrite Scarlett Solo 3rd Generation.

My question is this:
How easy or hard is it to setup and use my Scarlett on Ubuntu 20.04 or Kubuntu.
I haven’t decided which one of those Linux distros I’m going with but I definitely don’t want Ubuntu studio for other reasons.

I’m a complete beginner when it comes to anything Linux so its crucial for me to know how hard it will be to make the switch because of my audio interface

Follow up question; what about Ableton Live? What alternatives would you recommend for Ubuntu, especially for plugging in a guitar and playing with virtual amps (think guitar rig pro)

sadko4u Established Member Posts: 948 Joined: Mon Sep 28, 2015 9:03 pm Has thanked: 2 times Been thanked: 263 times

Re: Focusrite Scarlett Solo Gen 3 on Ubuntu 20.04

Post by sadko4u » Thu Oct 15, 2020 12:06 pm

Torrino wrote: ↑ Thu Oct 15, 2020 11:38 am Hi everyone, I’ve been a musician for the past 12 years but a Windows user for a lifetime. and I have finally decided to switch to Linux.

Torrino wrote: ↑ Thu Oct 15, 2020 11:38 am I’ve always wanted to switch to Linux but never got to do so and now that I’ve finally decided to make the switch, I’ve realized that there’s no official driver support for my Focusrite Scarlett Solo 3rd Generation.

Torrino wrote: ↑ Thu Oct 15, 2020 11:38 am How easy or hard is it to setup and use my Scarlett on Ubuntu 20.04 or Kubuntu.
I haven’t decided which one of those Linux distros I’m going with but I definitely don’t want Ubuntu studio for other reasons.

The gen3 device is not supported by the Linux kernel. I’m currently working on enhancing the @geoffrey ‘s driver for the support of Scarlett 18i20 gen3 device and other gen3 devices. To get this driver working, you need to patch and rebuild your linux kernel.

Torrino wrote: ↑ Thu Oct 15, 2020 11:38 am That’s not too hard and I believe I can help you with deploying the driver to your machine if you will help me to inspect your purchased device.

Here’s the related topic of Scarlett gen3 support:
viewtopic.php?f=6&t=20669

Here’s my github project where I’m developing the driver:
https://github.com/sadko4u/scarlett-gen2

Here are the patches (and supplementary reverse-engineering information) that allow to add support of gen3 devices to openSUSE Leap 15.2 kernel:
https://github.com/sadko4u/focusrite-scarlett-backports

The current state related to 18i20 device: almost all controls are supported and working except of saving the input and output routing configuration of the device. That still needs of some reverse engineering and time.

FloeHetling Established Member Posts: 4 Joined: Sun May 10, 2020 2:59 pm Location: Tula, Russian Federation Contact:

Re: Focusrite Scarlett Solo Gen 3 on Ubuntu 20.04

Post by FloeHetling » Thu Oct 22, 2020 7:03 am

Still I have my Scarlett 2i2 hooked to Studio 20 with no problems. However seems like it’s working only as audio interface and not using its potential to the fullest. How do I put it.

On Windows machine when you’re playing FL Studio there’s either a lag or ton of XRUNS when you try to run it on low CPU. But when Scarlett enters the scene you can select its driver in FL and CPU load drops a bunch, so is the latency. I have no knowledge in this topic so I can’t explain why this happens.

So, back to my Studio 20. Seems like no difference if I use embedded audio interface of my motherboard or my Scarlett. Except only a quality (less noisy) but in terms of XRUNS — I have pretty same processor load whether I’m on internals or Scarlett. Is it how it goes or I can have more power by installing some driver for it?

My workstation specs:
Intel Atom CPU D425 @ 1.80GHz 4096m RAM
Ubuntu Studio 20.04 LTS (GNU/Linux 5.4.0-29-lowlatency x86_64)
Focusrite Scarlett 2i2 1st gen
Novation Launch Control 1st gen
M-Audio KeyRig 49
CASIO CTK-481 via Roland UM-ONE interface

Источник

LinuxMusicians

Focusrite Scarlett Solo stopped working on Ubuntu 20.04

Post by nyoshiuchi » Tue Nov 08, 2022 6:03 pm

Hi folks, my Focusrite Scarlett Solo stopped working yesterday, I assume there was some update that caused this issue. I had been using it as a class compliant device with no issues up until this point.

I checked dmesg and saw that the Focusrite Gen 2/3 Driver was disabled. Following the instructions here: https://github.com/geoffreybennett/scar . 2/releases I created /etc/modprode.d/scarlett.conf and rebooted. After a reboot I see the following in dmesg:

$ dmesg | grep -i scarlett [ 7.134207] usb 1-3.1.1: Product: Scarlett Solo USB [ 13.605064] scsi 9:0:0:0: Direct-Access Scarlett Welcome Disk 0.10 PQ: 0 ANSI: 2 [ 177.487940] usb 1-3.1.1: Focusrite Scarlett Gen 2/3 Mixer Driver enabled pid=0x8211

However when I open alsamixer I do not see the device listed. It is not listed in the Ubuntu settings nor in pavucontrol.

I am running Ubuntu 20.04 with Kernel 5.14.0-1054-oem

$ uname -a Linux nyoshiuchi 5.14.0-1054-oem #61-Ubuntu SMP Fri Oct 14 13:05:50 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.5 LTS Release: 20.04 Codename: focal

I am not able to update Ubuntu and I can only used kernels provided by Canonical.

Can anyone help me debug this? Either get the Scarlett drivers working or get the device to work with the standard audio drivers as a class compliant device.

Источник

Interfacing Linux: Focusrite Scarlett Solo (Gen3)

The Scarlett Solo is a budget interface from Focusrite sporting USB connectivity and two preamps capable of delivering 56 dB of gain. Let’s see if it knows how to Linux.

Drivers

Pulseaudio

The Focusrite Scarlett Solo will function like any other sound device in pavucontrol.

Jack

Select the ALSA driver to connect your Focusrite Scarlett Solo to the Jack server.

Round-trip Latency

While many kinds of audio latency metrics exist, one useful and well-understood metric is round-trip latency; the time it takes for an audio signal to enter the input of a device, get processed, and exit the output.

Testing setup

CPU	AMD Ryzen 7 1700
RAM	Corsair Vengeance LPX 16GB
Motherboard	MSI B350 Tomahawk
GPU	Nvidia NVS 300
SSD	Samsung 840
PSU:	EVGA 600 B1
Firewire:	Syba SY-PEX30016
Network:	Intel i350-T4
OS:	Debian Bullseye
Kernel:	5.11-rt-amd64
Desktop:	NA

Focusrite Scarlett Solo: Round-trip latency @44100 Hz

Focusrite Scarlett Solo: Round-trip latency @48000HZ

Focusrite Scarlett Solo: Round-trip latency @96000HZ

Focusrite Scarlett Solo: Round-trip latency @192000HZ

Technical Specifications

Connectivity: USB 2.0
Simultaneous I/O: 2 x 2
Preamps: 1 x mic, 1 x instrument
Gain Range: 56 dB
Phantom Power: Yes
A/D Resolution: Up to 24-bit/192kHz
Analog Inputs: 1 x XLR (mic), 1 x 1/4″ (Hi-Z)
Analog Outputs: 2 x 1/4″ TRS
Headphones: 1 x 1/4″
USB: 1 x Type USB-C
Bus Powered: Yes
Power Supply: USB bus powered

Verdict

The Scarlett Solo does everything it claims on the tin. It’s a perfectly serviceable budget USB interface. It’s only crime is costing more than the Behringer U-Phoria UMC204HD.

Источник

Getting a Focusrite Scarlett Solo to work under Linux – Common Issues

The Focusrite Scarlett Solo is a pretty nifty audio interface that seems to be getting rather popular as of late. I purchased one myself to replace my dying Asus Xonar U7 that had some issues when running on Linux (and on Windows thanks to the drivers, but that’s another topic). For the most part, the Linux experience is actually fairlygood, but there are some pitfalls that you might have to look out for when running one of these with a Linux system. What follows is a list of issues that I’ve come across and how to solve them:

Issue: The sound card works, but cuts out when no input/output is detected. All lights are off when this happens.

Explanation: This usually happens because of USB power saving features that are present in some tools like tlp. These deactivate USB devices automatically if they are not showing any activity. Most distros don’t ship these by default, but some, such as Manjaro, do, even on Desktops.

Solution: If you have tlp installed on your system, you can either disable USB power saving entirely or put your Scarlett onto a blacklist so that it is never suspended. See this page for details on how to do so. If you use a different power-saving utility, check if it has a similar option or just disable it outright.

Issue: Microphone recordings are distorted/contain static/are unbalanced (left channel).

Explanation: This happened to me while I was using my Rode M3 condenser mic at the XLR input of the Scarlett Solo. It seems like the Scarlett reports a stereo mic input, regardless of the actual capabilities of the mic. This can cause a variety of effects, such as a 100% left channel recording, distortion or, in my case, a static noise on the right channel (might have been the 48V phantom power). This also happens on Windows.

Solution: While the solution to this problem is fairly easy under Windows (Sound settings -> change input device to mono-only), the Linux solution is a bit more complicated. As usual, there probably are multiple ways to do this, but I found that creating a remapped pulseaudio input was the most elegant solution. If you need support for ALSA, you can probably do something similar within .asoundrc.

to get a list of available sources on your system. Look for the line that corresponds to your Scarlett, in my case this was:

with your favorite text editor and add the following:

load-module module-remap-source master=alsa_input.usb-Focusrite_Scarlett_Solo_USB-00.analog-stereo source_name=Mic-Mono master_channel_map=left channel_map=mono

#Optional: Select new remap as default

set-default-source Mic-Mono

This tells pulseaudio to create a remapped microphone source that only contains the left channel of the original and is thus a mono source. Make sure to adjust the master option according to the output from pacmd and don’t forget to remove the brackets! The second line is optional and automatically sets the default source to our new redirected source.

That is all for now. If I find any other issues, i’ll update this post accordingly.

Источник