LinuxMusicians

A related question I've been meaning to ask for ages: is threadirqs kernel parameter needed for a low-latency kernel with PREEMPT eg. Liquorix? I need to look this up, I know PREEMPT_RT implies threadirqs (see https://wiki.linuxfoundation.org/realtime/documentation/technical_details/threadirq) but ...

Good question, I was already experimenting with white noise too.

There is an autotune https://x42-plugins.com/x42/x42-autotune but it's not quite the same as you're describing. You can come a long way with it, it can detect separate notes and you can pitch those to the notes you'd like. With some automation you can really transform complete melodies or create ne...

No problem! And if things still don't start up at login don't hesitate to post! Also, with a real-time kernel you don't need the threadirqs option.

It was a great challenge! Thanks @Sahaathyva for organizing and thanks @WeirdConstructor for the great plugin! Had a fun time and maybe I'll join next time too because I really dig Nekobi.

The following should do the trick:

Fwiw, I always create a separate partition for doing audio. That way I am sure the things I need for my day to day computer use do not interfere with the audio part. It also allows me to further finetune the audio partition which in turn could have affected my day to day use, i.e. running a real-tim...

Boorhin Sorry for hijacking your thread a bit :shock: But it partly applies to your situation too so I'm allowed hopefully :roll: On IRQ threading, the guide says: If it returns CONFIG_IRQ_FORCED_THREADING=y and CONFIG_PREEMPT_RT=y then your kernel is using IRQ threading and you don't have to proce...

Kernel: 4.15.0-136-lowlatency $ cat /etc/default/grub.conf ... GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash threadirqs" GRUB_CMDLINE_LINUX="" ... mitigations=off...

JamesPeters wrote: ↑Mon Mar 01, 2021 2:19 am I had the same issue with the same interface. Stopping "USB autosuspend" fixed it.

I had a hunch too in that direction and the fact that we're dealing with EHCI (USB2) and rate matching hubs only strengthens that suspicion. But let's see first what the logs give us.

Okay, sorry, what exactly are the steps I need to take to give you the info you desire? Plug in your Focusrite, start tailing the logs with tail -f /var/log/{kern.,sys}log and post the output of the logs at the moment the Focusrite fails. It's also possible to look back in the logs but while tailin...

I ran your command right after it went silent again Could you run it before you start working with your Focusrite? Now we don't see the full error message while it does look like something is going wrong. We want to see what happens when the Focusrite stops working. Also the timestamps of both logs...

Thanks for the feedback! USB is not sharing its interrupts so that's good. Would it be possible to run the following command in a terminal while you're Focusrite is plugged in? Maybe we can catch a log entry that correlates with the Focusrite failing. sudo tail -f /var/log/{kern.,sys}log And you mig...

Does it also happen with Alsa? I would test another cable to at least exclude this as the problem. +1, try with a better cable. If you can get your hands on Klotz cables I'd get those, not super expensive but very good quality. And you could try disabling autosuspend for your USB devices: https://w...

+-------------------+------------------------+-------+ | Artist | Track | Score | +-------------------+------------------------+-------+ | Largos | Bleakuary | 3 | +-------------------+------------------------+-------+ | sg75 | Kickmessiness | 3 | +-------------------+------------------------+-----...