realtimeconfigquickscan VS jackaudio

git clone https://github.com/raboof/realtimeconfigquickscan cd realtimeconfigquickscan perl ./realTimeConfigQuickScan.pl

Curious to see if it's working, didn't have the courage to try pw yet. You do have rt kernel and checked the config etc? Jack can get annoyed when running rt and not having something set. I usually check with this tool https://github.com/raboof/realtimeconfigquickscan

I've tweaked my Manjaro install to be fit for music production with the help of https://github.com/raboof/realtimeconfigquickscan and the script outputs only "good" lines.

There is also https://github.com/raboof/realtimeconfigquickscan

Package realtime-privileges should be installed for JACK to run optimally. There is also realtimeconfigquickscan script to check system configuration

I used this tool to identify stuff to tweak https://github.com/raboof/realtimeconfigquickscan and I did everything that was suggested.

I use realtimeconfigquickscan to make sure system is configured for realtime scheduling and that is enough for JACK to run without problems

11 is pretty low, try running this script to check your settings: https://github.com/raboof/realtimeconfigquickscan

I don't see why these settings would cause issues like this, if your soundcard supports it. I do agree that 48khz is more then sufficient and probably gives you a better experience overall. But it sounds to me like your OS is not properly configured. You can run a script to get some insights. Please checkout https://github.com/raboof/realtimeconfigquickscan. Also check out the documentation of your distro.

Linux: Good luck! You can use JACK, which provides something similar to ASIO4ALL (as in generic low-latency audio functionality, but with more flexibility). In conjunction with pulseaudio-module-jack, you are able to route ordinary system audio (browser, media players, OBS, etc) to JACK and vice versa. Here's a guide on how to achieve this. Then you can just set JACK as pd's output and as OBS' input. I successfully set this up on a Debian system.

If you search for a solution to connect non-JACK software to JACK maybe you could try running PulseAudio on top of JACK.

They're different implementations, that are almost functionally identical. Because JACK2 is actively maintained, it should be the preferred choice, unless you have a very specific need for JACK1.

NetJACK = https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_NetJack2

jack2 is a rewritten version of jack. It has a backwards compatible ABI -- programs compiled for jack will work with jack2 without needing recompile. See https://github.com/jackaudio/jackaudio.github.com/wiki/Differences-between-jack1-and-jack2 which recommends using jack2 as jack is now bugfix-only (no new features etc)

You could probably use alsa_in to make a jack port for the mic https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_AlsaInOut

Check the official jack/pulseaudio howto for getting that up and running.

https://github.com/jackaudio/jackaudio.github.com/wiki may be helpful, otherwise do the usual sweep here, on Arch Linux, youtube, https://odysee.com/$/search?q=jack%20audio etc.