This typically happens in complex setups with PipeWire, where a bridge between different devices, such as the wireless mic and the internal headphone jack, is created.
There's two ways this can play out. In botch cases, the sound is not affected, so I assume the scheduling threads are not affected.
1.) The editor freezes completely, the cursor doesn't move, the window doesn't update.
2.) The editor is accepting input, but executing code doesn't have any effect ...
This typically happens in complex setups with PipeWire, where a bridge between different devices, such as the wireless mic and the internal headphone jack, is created.
There's two ways this can play out. In botch cases, the sound is not affected, so I assume the scheduling threads are not affected.
1.) The editor freezes completely, the cursor doesn't move, the window doesn't update. 2.) The editor is accepting input, but executing code doesn't have any effect ...