Reaper and Fedora 39

[atomlux]

Has anyone tried it?
Currently I'm on Debian 12, it's fantastic, but I'd like to distro hop.
Why not? Fedora has a lot of new stuff, and as a KDE user, I'd like to try GNOME for a change.
They say it's the DE that gets the most money for development.
My biggest worry is Wayland. Second is to get all my synths working, like in Debian.

[mcoyle]

Originally Posted by atomlux

Has anyone tried it?
Currently I'm on Debian 12, it's fantastic, but I'd like to distro hop.
Why not? Fedora has a lot of new stuff, and as a KDE user, I'd like to try GNOME for a change.
They say it's the DE that gets the most money for development.
My biggest worry is Wayland. Second is to get all my synths working, like in Debian.

I'm on Fedora 39/Gnome. It all works great: Reaper, Pipewire, etc.

My default is X11 but I have done limited testing on Wayland and I don't remember any problems. I stick with X11 because I love love using the Plank dock.

[/AND/]

I've been using Fedora for about 1.5 years now, no major issues. In fact, I really like it - stable, polished, fast, supported. First had it with GNOME, then switched to KDE.

Wayland works great and out of the box, PipeWire ditto, a preemptive kernel with great performance.

Ever since I tried Fedora I stopped distrohopping. That should stand for something

Originally Posted by mcoyle

...I stick with X11 because I love love using the Plank dock.

Try Latte Dock

[mcoyle]

Originally Posted by /AND/

Try Latte Dock

Well, then I'd basically have to install KDE and that's a big nope.

[fabio77]

Originally Posted by /AND/

I've been using Fedora for about 1.5 years now, no major issues. In fact, I really like it - stable, polished, fast, supported.

Same for me. Fedora 39 KDE. But since I have some issues with my two screen setup on wayland I'm still on x11.

[atomlux]

I run the Live Fedora 39 GNOME last night without installing.
I'm not sure if I could live in GNOME. There are some details from KDE that I use all the time.
Thanks for the answers, I'll try it again tonight to see what I would be missing from GNOME if I stuck to KDE.

[fabio77]

Originally Posted by atomlux

I'll try it again tonight to see what I would be missing from GNOME if I stuck to KDE.

Let us know, if there is something

I ran Ubuntu with Unity and then Gnome over 10 years, until I tried multiple distros and desktop environments last year, and I really like KDE. I don't remember anything from Gnome that I miss or could miss.

By the way, I configure my KDE still in the way it looked with Untiy. I love the top panel and left application bar and the global menus

[atomlux]

Ok. I did try GNOME for a few hours, and as we say in my country, "no me veo en la foto" (I don't see myself in the photo) haha
I've just realized that I'm a KDE "power user" lol
Anyway, GNOME fanboys can tell me here what I might be missing.
And about Fedora, I picked that one because it's said that it has the best GNOME implementation.

[SmajjL]

Installing/trying.. KDE edition right now as it hit 39 and i am not only using my computer for music (please note) and, i consider myself as an EX.. - distrohopper back to Kubuntu if something gives me a migrane or summit for my biased'ness to work.

Will do my Best to help it work though (and i don't surrender easy) may the force be with me, wish me luck

[fabio77]

Originally Posted by atomlux

And about Fedora, I picked that one because it's said that it has the best GNOME implementation.

Main Fedora sticks with Gnome yes, but the KDE Version is great.

[mindlessgenius]

I'm just trying out Fedora 39 on my laptop. You have to be prepared to put in a little more work than on Debian systems, especially hunting packages. For example, the KXStudio repos are not available as .rpms.

I had Gnome for years on a laptop with 12,5" screen and for this purpose it was great, as screen real estate was precious. The paradigm of running every program in fullscreen suited the machine well. On my new Framework I'm less sure about this. Without the fractional scaling introduced in Fedora 39, I'd have ditched Gnome immediately.

On desktop monitors I think KDE is the better option, as it has more options for customisation, you don't need touch compatibility and there is enough space to not limit yourself to the oversimplified Gnome design paradigms. This is the Reaper forum after all, we're tinkerers

Speaking of which: Reaper runs rock stable in F39. The only gripes I have are that media explorer does not show my "volumes" and that JS plugins do not recognise tap-to-click on my laptop. But I didn't double-check yet if these are exclusive to Fedora or if this just an issue with the laptop drivers.

[SmajjL]

Originally Posted by mindlessgenius

I had Gnome for years on a laptop with 12,5" screen and for this purpose it was great, as screen real estate was precious. The paradigm of running every program in fullscreen suited the machine well. On my new Framework I'm less sure about this. Without the fractional scaling introduced in Fedora 39, I'd have ditched Gnome immediately.

I think i've seen Nobara having a FS-patch for GNOME, not tried it myself though, no smileys guaranteed!
https://nobaraproject.org/

Next day edit: Fedora is great, but i will stick with Kubuntu until they force a reason opon me or sumething not to (hopefully never) i live on the EU-side of the planet, and Google/Tube might not like some of our LAWs overhere, i think

Fedora allows for flatpak-start from var/lib if we feel like it or need that for some reason. (not sure how-to on non-Fedora)
X-Plane 12 works, yabba dabba doo!
We can have firewalld Active with two physical netcards and simply share IPv4 to another device (can ofc install that on other distros)
Discover on Fedora allows to un-install stuff faster without the need for a password every time.
OBS (flatpak)/ FFmpeg VAAPI HEVC / CQP works fine with recording competitive gameing.
Fedora update speed i have missed but at the same time, i like a more calmed down Ubuntu speed, specially if KDE Plasma 6 is around the corner and i still have a need for x11 for some games (on KDE), maby slow things down a tad is good depending who we ask..
Fedora sure is good though

[atomlux]

I went with Xubuntu in the end lol

[SmajjL]

Originally Posted by atomlux

I went with Xubuntu in the end lol

Congrats if you found your happyplace, i'll be shocked! if you found a bug at your place.

[atomlux]

Originally Posted by SmajjL

i'll be shocked! if you found a bug at your place.

I have already, back to Debian 12 KDE!

[SmajjL]

Originally Posted by atomlux

I have already, back to Debian 12 KDE!

Really? WoWza'h , welcome to KDE then
A little surprised actually but, hey, don't mess with atomlux

[atomlux]

Originally Posted by SmajjL

Really? WoWza'h , welcome to KDE then
A little surprised actually but, hey, don't mess with atomlux

I always come back to KDE, it's pointless to try others at this stage, I never learn lol
And Debian 12 is good for my poor internet connection, because of the very few updates.
This time I haven't even installed flatpak support,

[SmajjL]

Originally Posted by atomlux

I always come back to KDE, it's pointless to try others at this stage, I never learn lol
And Debian 12 is good for my poor internet connection, because of the very few updates.
This time I haven't even installed flatpak support,

Ahh, there is One reason i was curious why so many leave out the top secret reasons we all have when chosing something and yet, *this distro is da best!* ugh
I think Starlink is bound to get cheaper or, less expensive if that would be an option?
Also, at the beginning, i was going totally crazy bonkers with distrohopping and i have mixed feelings about it, because i kinda enjoyed trying stuff but hello! my time on earth is limited...

[fabio77]

Originally Posted by atomlux

I have already, back to Debian 12 KDE!

Does Debian come with pipewire out of the box?

[atomlux]

Originally Posted by fabio77

Does Debian come with pipewire out of the box?

Yes, I've just installed pipewire-jack and pipewire-alsa to make it work.
Run Reaper with:

pw-jack reaper

[fabio77]

Originally Posted by atomlux

Yes, I've just installed pipewire-jack and pipewire-alsa to make it work.

Ok. I'm just considering options, if Fedora 40 drops KDE with x11 and there would be still issues

[SmajjL]

Originally Posted by SmajjL

specially if KDE Plasma 6 is around the corner and i still have a need for x11 for some games (on KDE), maby slow things down a tad is good depending who we ask..
Fedora sure is good though

May i ask how you can test Fedora KDE and not even actually trying gameing on Wayland? you forgot didn't you?
Is the mousesensitivity the same now using RAW-input or, not? find out for me please
Also, just filled up your coffee-stash, you gonna need it and, there is something (top secret) you need to try in COPR..

Slap!

[IRVNG]

Guys how do you get Fedora 39 working for music production? I've followed this guide:
https://copr.fedorainfracloud.org/co...ickl/wine-tkg/

And the developer and creator of it also has personally helped me through discord but still I get really poor performance. (Xruns, high dsp usage and stuttering even with just one plugin open)

It's not an issue with my PC since on Windows it works great. Just tried Ubuntu and it also gets way better performance when producing music, but Fedora works amazing for me in every other aspect so I would like to find a solution for it.

Any advice is appreciated!

[fabio77]

First question, do you use X11 or wayland. I use X11.

I don't know this git you mention, so I just can tell you what I do after a fresh install.

# limits.conf
sudo nano /etc/security/limits.conf
@audio - rtprio 98
@audio - nice -10
@audio - memlock unlimited

# sysctl.conf
sudo nano /etc/sysctl.conf
vm.swappiness=10
fs.inotify.max_user_watches=524288
vm.max_map_count=2147483642

sudo sysctl --system

# adding user to audio group
sudo usermod -aG audio $USER

# adding repo and installing wine-staging
sudo dnf config-manager --add-repo https://dl.winehq.org/wine-builds/fedora/39/winehq.repo
sudo dnf install winehq-staging

# adding this to the grub_cmdline (ADDING NOT DELETING OTHER STUFF)
sudo nano /etc/default/grub
GRUB_CMDLINE_LINUX="preempt=full threadirqs"

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

Then I install yabridge from the git https://github.com/robbert-vdh/yabridge/releases
Just unpack the tar.gz to .local/share and set it up as documented on the git page.

And installing reaper.

I think that's all.

[audiojunkie]

Originally Posted by SmajjL

Ahh, there is One reason i was curious why so many leave out the top secret reasons we all have when chosing something and yet, *this distro is da best!* ugh
I think Starlink is bound to get cheaper or, less expensive if that would be an option?
Also, at the beginning, i was going totally crazy bonkers with distrohopping and i have mixed feelings about it, because i kinda enjoyed trying stuff but hello! my time on earth is limited...

I searched for over a year before I chose to stick with Fedora. I had developed quite a large criteria for what I wanted in a distro. Debian is my second place choice. Here's my criteria:

* The most software (including 3rd party repositories)
* Independent—free of corporate influence
* Huge support community
* Excellent documentation
* Very flexible—can be minimal or full featured
* Numerous Desktop Environment choices
* Supports multiple chip architectures
* Between stable & bleeding edge (similar to #debiantesting)
* Dependable & requires little manual intervention (unlike #archlinux)

[audiojunkie]

Originally Posted by fabio77

Ok. I'm just considering options, if Fedora 40 drops KDE with x11 and there would be still issues

Fedora won't drop KDE. It is, however, likely that they will drop X11. But that should be of very little concern, because xwayland is essentially the entirety of x11 run through Wayland. It keeps the Wayland security, while keeping the x11 compatibility. I've been using Wayland for years without any problem at all. You'll almost certainly be fine, unless you have some edge case issue that most will never run into. And even with that, xwayland is still continuously getting updates that further improve x11 support and stability while working under Wayland.

I don't think there is much need to worry about Wayland at this point.

[audiojunkie]

Originally Posted by IRVNG

Guys how do you get Fedora 39 working for music production? I've followed this guide:
https://copr.fedorainfracloud.org/co...ickl/wine-tkg/

And the developer and creator of it also has personally helped me through discord but still I get really poor performance. (Xruns, high dsp usage and stuttering even with just one plugin open)

It's not an issue with my PC since on Windows it works great. Just tried Ubuntu and it also gets way better performance when producing music, but Fedora works amazing for me in every other aspect so I would like to find a solution for it.

Any advice is appreciated!

You are currently using a Pipewire beta version. I advise you to try again with Pipewire 1.0.. When you do, be sure that Pipewire is in ProAudio mode--the IRQ scheduling won't work if you don't. Don't forget to add yourself to the Pipewire group, and update your rtprio and memlock settings. I'm willing to be that the above mentioned things will improve your experience.

[fabio77]

Originally Posted by audiojunkie

Fedora won't drop KDE. It is, however, likely that they will drop X11.

This is my concern

Originally Posted by audiojunkie

You'll almost certainly be fine, unless you have some edge case issue that most will never run into.

...

I don't think there is much need to worry about Wayland at this point.

I have the problem, that after I suspend my PC I get no video signal at any of my two displays.

And even in this forum I read about some trouble with plugins regarding wayland. So I'm still not convinced.

But I hope for better support at least in fedora 41. That would be the time when fedora 39 gets no longer support.

Originally Posted by audiojunkie

When you do, be sure that Pipewire is in ProAudio mode--the IRQ scheduling won't work if you don't.

I never tried this. But thanks for the recommendation. I have to try it.

Originally Posted by audiojunkie

Don't forget to add yourself to the Pipewire group ...

Is it not sufficient to add the user to the audio group?

[audiojunkie]

Originally Posted by fabio77

This is my concern



I have the problem, that after I suspend my PC I get no video signal at any of my two displays.

And even in this forum I read about some trouble with plugins regarding wayland. So I'm still not convinced.

But I hope for better support at least in fedora 41. That would be the time when fedora 39 gets no longer support.



I never tried this. But thanks for the recommendation. I have to try it.



Is it not sufficient to add the user to the audio group?

Indeed, things will improve with each subsequent version of the software. Hopefully that monitor issue you are experiencing will be fixed by Fedora 41.

It depends on which group is configured with your rtprio and memlock settings. You do that configuration yourself, so it will be likely up to you. However, Fedora by default has the Pipewire group added for this particular purpose, so I see very little reason to duplicate things with an audio group. You could call your group "banana" if you wanted to, as long as you create and edit a banana config file with the right settings. The Pipewire wiki recommends the following:

https://gitlab.freedesktop.org/pipew...ormance-tuning

RLIMITs

Real-time priority limits are usually stored in /etc/security/limits.conf and /etc/security/limits.d/. The best option is to add a new file 95-pipewire.conf in /etc/security/limits.d/ with this content:

# Default limits for users of pipewire
@pipewire - rtprio 95
@pipewire - nice -19
@pipewire - memlock 4194304


Then add your user to the PipeWire group so that you can use these priorities.


As for making sure your Pipewire is using Pro Audio mode, that is where the latency improvement and reduced xruns will come from (between the above pipewire settings listed above and this). Pipewire was using an insufficient scheduler, and several of us contacted the developer and discussed the issue with him. After a bit, we convinced him that more improvement was needed, so he added a pro audio mode that's using IRQ scheduling like JACK does, to get the equivalent performance. Our journey and experiences (as well as the explanations on everything) are pretty well documented here:

https://linuxmusicians.com/viewtopic.php?t=25804

Warning, it's a long read, but it is very enlightening regarding how Pipewire is working now with the 1.0 version. I highly recommend it for getting a better understanding.

I hope this is helpful!

Edit: I also forgot that to best benefit from a standard generic kernel, you'll want to use GRUB and add the following kernel boot parameters: /preempt=full /irqthreads

[fabio77]

Thank you for this explanation and the link. Now I understand. I will probably change this from @audio to @pipewire.

[IRVNG]

Originally Posted by fabio77

First question, do you use X11 or wayland. I use X11.

I don't know this git you mention, so I just can tell you what I do after a fresh install.

# limits.conf
sudo nano /etc/security/limits.conf
@audio - rtprio 98
@audio - nice -10
@audio - memlock unlimited

# sysctl.conf
sudo nano /etc/sysctl.conf
vm.swappiness=10
fs.inotify.max_user_watches=524288
vm.max_map_count=2147483642

sudo sysctl --system

# adding user to audio group
sudo usermod -aG audio $USER

# adding repo and installing wine-staging
sudo dnf config-manager --add-repo https://dl.winehq.org/wine-builds/fedora/39/winehq.repo
sudo dnf install winehq-staging

# adding this to the grub_cmdline (ADDING NOT DELETING OTHER STUFF)
sudo nano /etc/default/grub
GRUB_CMDLINE_LINUX="preempt=full threadirqs"

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

Then I install yabridge from the git https://github.com/robbert-vdh/yabridge/releases
Just unpack the tar.gz to .local/share and set it up as documented on the git page.

And installing reaper.

I think that's all.

Thank you Fabio! I tried it and it gave me great performance. That's exactly what I needed. I use Wayland and it still worked perfectly.

[IRVNG]

Originally Posted by audiojunkie

Indeed, things will improve with each subsequent version of the software. Hopefully that monitor issue you are experiencing will be fixed by Fedora 41.

It depends on which group is configured with your rtprio and memlock settings. You do that configuration yourself, so it will be likely up to you. However, Fedora by default has the Pipewire group added for this particular purpose, so I see very little reason to duplicate things with an audio group. You could call your group "banana" if you wanted to, as long as you create and edit a banana config file with the right settings. The Pipewire wiki recommends the following:

https://gitlab.freedesktop.org/pipew...ormance-tuning

RLIMITs

Real-time priority limits are usually stored in /etc/security/limits.conf and /etc/security/limits.d/. The best option is to add a new file 95-pipewire.conf in /etc/security/limits.d/ with this content:

# Default limits for users of pipewire
@pipewire - rtprio 95
@pipewire - nice -19
@pipewire - memlock 4194304


Then add your user to the PipeWire group so that you can use these priorities.


As for making sure your Pipewire is using Pro Audio mode, that is where the latency improvement and reduced xruns will come from (between the above pipewire settings listed above and this). Pipewire was using an insufficient scheduler, and several of us contacted the developer and discussed the issue with him. After a bit, we convinced him that more improvement was needed, so he added a pro audio mode that's using IRQ scheduling like JACK does, to get the equivalent performance. Our journey and experiences (as well as the explanations on everything) are pretty well documented here:

https://linuxmusicians.com/viewtopic.php?t=25804

Warning, it's a long read, but it is very enlightening regarding how Pipewire is working now with the 1.0 version. I highly recommend it for getting a better understanding.

I hope this is helpful!

Edit: I also forgot that to best benefit from a standard generic kernel, you'll want to use GRUB and add the following kernel boot parameters: /preempt=full /irqthreads

Ok I read the thread on Linux Musicians. I was kinda disappointed by the Pipewire dev (or devs?) having zero idea about pro audio needs, but you did a great job making them understand what we need! Thank you for that. I read the Fedora interview with the Pipewire creator and they talked about pro audio a lot, so it seems like I can definitely switch from Windows to Linux for my work as a producer and artist!

But now I'm confused about what I need to do to configure my Fedora 39 installation for low latency and no xruns. Where do I find that Pipewire Pro Audio Mode and how do I activate it? Can you write a guide like Fabio did or improve upon it?

I’m using Fedora Workstation 39 (GNOME desktop) btw.

Thanks in advance!

[fabio77]

Originally Posted by IRVNG

Thank you Fabio! I tried it and it gave me great performance. That's exactly what I needed. I use Wayland and it still worked perfectly.

That's great

Apropos performance... You can use this commands to detect the active cpu governor mode and set it on performance.

# read the status
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

# set it to performance
echo -n performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

In the same way you can put it back on the mode you detected first.

Originally Posted by IRVNG

Where do I find that Pipewire Pro Audio Mode and how do I activate it?

If I understand it right, then you maybe find it at your system panel at the volume drop down?

On KDE when I click on the volume symbol in the panel, I can click on the three lines for the drop down menu. In there is the option for "Pro Audio".

I didn't test it, because I was too lazy to turn on my audio card and make a test but I think this is it.

I think other Desktop Environments should have a similar option. And I hope I will find out how to manage this via terminal for DE independent usage.


But I want to add, I'm not 100% sure about that. So I hope @audiojunkie will confirm or correct me.

[/AND/]

Originally Posted by fabio77

...

Apropos performance... You can use this commands to detect the active cpu governor mode and set it on performance.

# read the status
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

# set it to performance
echo -n performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
...

Is this persistent across reboots? BTW I only have powersave and performance (available from cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_governors

[fabio77]

Originally Posted by /AND/

Is this persistent across reboots?

I'm not sure. Let me know if you try (I assume it does not persist a reboot)

I wrote a script that I use to switch states while music production and back when finished.

And maybe a tip. There is a software called tlp and tlp-gui that can manage this for you. It is a powermanagement software. I don't use it because I don't know if it could collide with some powermanagement tools installed by fedora as a default. But I know that @glennbo mentioned and uses it.

Originally Posted by /AND/

BTW I only have powersave and performance (available from cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_governors

The same for me, at least this is what the output says.

I just need powersave and performance for now. But if you research further, I'm pretty sure also the states "ondemand" and "schedutil" should be supported.

[/AND/]

Originally Posted by fabio77

I'm not sure. Let me know if you try (I assume it does not persist a reboot)

Well, I just rebooted and it seems to persist. I use tlp/tlp-gui as well, but didn't seem to affect this CPU setting at all. Maybe I should use a simple bash script like you to change the states whenever I need it.

Originally Posted by fabio77

The same for me, at least this is what the output says.

I just need powersave and performance for now. But if you research further, I'm pretty sure also the states "ondemand" and "schedutil" should be supported.

I think they can be accessed through amd_pstate, but don't know exactly how yet. If I find anything I'll reply back.

[fabio77]

Originally Posted by /AND/

Well, I just rebooted and it seems to persist. I use tlp/tlp-gui as well, but didn't seem to affect this CPU setting at all. Maybe I should use a simple bash script like you to change the states whenever I need it.

Ok, I didn't expect it would persist a reboot.

And tlp not affecting the cpu governor is suprising me also. If you're interested in getting it working you maybe could find a hint on the developers site https://linrunner.de/tlp/faq/processor.html

And for the bash script, here is mine, if you want to take it as a base:

#!/bin/bash
# cpu-governor switch to performance and back to powersave

count=$(cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor | wc -l)
result=$(cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor)
if [[ $result != "performance" ]]
then
	echo "CPU is running on powersave.";
	echo "To switch to performance root-privileges are required."
	echo -n performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor;
	echo " will be set on all $count cpu-cores.";
	cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor;
else
	echo "CPU is running on performance.";
	echo "To switch to powersave root-privileges are required."
	echo -n powersave | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor;
	echo " will be set on all $count cpu-cores.";
	cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor;
fi
exit

You can shorten it, if you wish. I like to have a little output to see what it is doing.

You maybe have to make it executable with:
sudo chmod 755 name_of_the_script.sh

And you might want to export its path to your bashrc/zshrc as you probably do with yabridge also:

export PATH="$PATH:$HOME/.local/bin/name_of_the_script.sh:$HOME/.local/share/yabridge"

Originally Posted by /AND/

I think they can be accessed through amd_pstate, but don't know exactly how yet. If I find anything I'll reply back.

Ok. I tested with the above command, but without success. But don't be bothered, if you're fine with powersave and performance

[IRVNG]

Originally Posted by fabio77

If I understand it right, then you maybe find it at your system panel at the volume drop down?

On KDE when I click on the volume symbol in the panel, I can click on the three lines for the drop down menu. In there is the option for "Pro Audio".

I didn't test it, because I was too lazy to turn on my audio card and make a test but I think this is it.

I think other Desktop Environments should have a similar option. And I hope I will find out how to manage this via terminal for DE independent usage.


But I want to add, I'm not 100% sure about that. So I hope @audiojunkie will confirm or correct me.

I managed to put my audio interface in the Pro audio profile following this tutorial.

After following it my Scarlett 2i4 shows this when entering one of the commands specified in there:

alsa.card_name = "Scarlett 2i4 USB"
            alsa.long_card_name = "Focusrite Scarlett 2i4 USB at usb-0000:00:14.0-3.3.3, high speed"
            alsa.driver_name = "snd_usb_audio"
            clock.name = "api.alsa.1"
            device.profile.pro = "true"
            device.profile.name = "pro-input-0"
            device.profile.description = "Pro"
            card.profile.device = "1"

Sharing it here in case it's useful to you guys.

Edit: I had to follow that tutorial because I found no way to do that in GNOME settings.

[fabio77]

Originally Posted by IRVNG

I managed to put my audio interface in the Pro audio profile following this tutorial.

After following it my Scarlett 2i4 shows this when entering one of the commands specified in there:

alsa.card_name = "Scarlett 2i4 USB"
            alsa.long_card_name = "Focusrite Scarlett 2i4 USB at usb-0000:00:14.0-3.3.3, high speed"
            alsa.driver_name = "snd_usb_audio"
            clock.name = "api.alsa.1"
            device.profile.pro = "true"
            device.profile.name = "pro-input-0"
            device.profile.description = "Pro"
            card.profile.device = "1"

Sharing it here in case it's useful to you guys.

Edit: I had to follow that tutorial because I found no way to do that in GNOME settings.

Thank you!

[audiojunkie]

Originally Posted by IRVNG

I managed to put my audio interface in the Pro audio profile following this tutorial.

After following it my Scarlett 2i4 shows this when entering one of the commands specified in there:

alsa.card_name = "Scarlett 2i4 USB"
            alsa.long_card_name = "Focusrite Scarlett 2i4 USB at usb-0000:00:14.0-3.3.3, high speed"
            alsa.driver_name = "snd_usb_audio"
            clock.name = "api.alsa.1"
            device.profile.pro = "true"
            device.profile.name = "pro-input-0"
            device.profile.description = "Pro"
            card.profile.device = "1"

Sharing it here in case it's useful to you guys.

Edit: I had to follow that tutorial because I found no way to do that in GNOME settings.

Sorry for responding late. Glad you got things working. I seem to recall that the easy way to switch to Pro Audio mode is through the gui app pavucontrol. I haven't tried this yet, because I haven't had time to work on my hobby lately. But suppsedly, you can select Pro Audio mode from a drop down box in this app.