Taskset prevents Yabridge loading some plugins #458
Description
Thanks for giving yabridge a shot!
- I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there
Problem description
Hi,
tldr; plugins work fine without taskset but hang with it.
When I run Bitwig (6b6 and earlier) using 'taskset --cpu-list 0-15 bitwig-studio' some plugins fail to load. There is no useful output from yabridge debugging at level 2. The yabridge process just spins out of control and quickly takes up half of the CPU cores allotted.
I need to run with tasket because without it Bitwig and plugins end up on the E cores of my i9 and performance is terrible. They don't then switch to the P cores when necessary. I'm on kernel (6.17.9-x64v3-xanmod1).
I've had problems with a few plugins in the past that I need to recheck but right now, this effects 3 Spitfire plugins: Solar, Abbey Road Two and AIR Studios Reverb.
To my knowledge this doesn't affect native plugins. I know taskset is used to run wine in other situations (Civ V etc.) but I don't know whether it's a problem with yabridge or wine.
This isn't DAW dependent, I've checked in Reaper and it's the same story.
What did you expect to happen?
Working plugins
What actually happened?
Hang
Operating system
Debian Trixie
How did you install yabridge?
release page
yabridge version
5.1.1
yabridgectl version
5.1.1
Wine version
wine-9.21.r1.g32abf9fc ( TkG Staging Esync Fsync )
Plugin
Solar, Abbey Road Two and AIR Studios Reverb
Plugin type
VST3
Plugin architecture
64-bit
Host
Bitwig 6b6
Desktop environment or WM
Gnome Wayland
GPU model
AMD Radeon RX 6600
GPU drivers and kernel
mesa, 6.17.9-x64v3-xanmod1
Debug log
Anything else?
I'd be interested if anyone else starting their DAW with taskset has problems with plugin loading.