| 9 Nov 2025 |
backtail | How do I find that? | 21:38:57 |
@bandithedoge:matrix.org | wpctl inspect | 21:39:05 |
@bandithedoge:matrix.org | you can get your device's id from wpctl status | 21:39:22 |
backtail | alsa.id is "USB Audio", interesting | 21:42:07 |
backtail | the same as in your config that didn't work for me | 21:42:31 |
@bandithedoge:matrix.org | yeah, i guess matching that is enough if you don't juggle between usb audio interfaces | 21:42:46 |
@bandithedoge:matrix.org | alsa.card_name maybe? | 21:43:27 |
backtail | alsa.long_card_name = "Roland TR-8 at usb-0000:16:00.0-4, high speed"
| 21:44:25 |
backtail | only long exists | 21:44:36 |
backtail | Ah no, sorry | 21:44:53 |
backtail | also.card_name = "TR-8" | 21:45:08 |
backtail | lol | 21:45:10 |
backtail | Do I need to change anything about some priority maybe? | 21:47:46 |
@bandithedoge:matrix.org | no, that's an unrelated hack in my config | 21:48:06 |
backtail | Still isn't switching profile replugging | 21:48:12 |
backtail | when* | 21:48:18 |
@bandithedoge:matrix.org | silly question but did you restart pipewire? | 21:48:33 |
backtail | when nixos-rebuild switching, should do it automatically, right? | 21:49:10 |
@bandithedoge:matrix.org | i'm pretty sure it doesn't restart on wireplumber config changes | 21:49:35 |
backtail | well, restarted the systemd service for pipewire and wireplumber, still the same | 21:50:28 |
backtail | I guess something for complicated is going on, so I might come back to it at some later point. Thanks for the help bandithedoge though! | 21:52:13 |
backtail | * I guess something more complicated is going on, so I might come back to it at some later point. Thanks for the help bandithedoge though! | 21:52:26 |
| 12 Nov 2025 |
| Inayet changed their display name from inayet to Inayet. | 12:39:04 |
| 18 Nov 2025 |
| jopejoe1 changed their display name from jopejoe1 to jopejoe1 (4094@39c3). | 20:19:49 |
| 19 Nov 2025 |
| crop joined the room. | 11:04:08 |
crop | i am wondering if i have configured pipewire correctly. the thread controlled by jack gets the priority -84 but i think it could benefit from getting realtime priority on a roundrobin scheduler.
i thought i could get this by using this pipewire config:
services.pipewire = {
enable = true;
alsa = {
enable = true;
support32Bit = true;
};
jack.enable = true;
pulse.enable = true;
wireplumber.enable = true;
extraConfig = {
pipewire."10-rt.conf" = {
"context.modules" = [
{
name = "libpipewire-module-rt";
args = {
"rt.prio" = 99;
};
flags = [ "ifexists" "nofail" ];
}
];
};
};
};
i also activated before all the lines from the example conf: https://docs.pipewire.org/page_module_rt.html
i don't understand where the -84 priority comes from | 11:10:18 |
| 20 Nov 2025 |
| John joined the room. | 07:09:19 |
| 30 Nov 2025 |
| Masen Joumaah joined the room. | 20:47:46 |
| 1 Dec 2025 |
| matthewcroughan changed their profile picture. | 14:59:05 |
| 4 Dec 2025 |
| Ido Samuelson joined the room. | 01:46:20 |