-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash with Pipewire-Jack 0.3.33, here's a workaround! #30
Comments
you are a lifesaver. |
@praashie how did you make To me it fails with messages saying that jackd was unable to acquire the pipewire device. WineASIO works when I stop |
this does not work here
|
those calls are from jackdbus, which is not supported under pipewire. |
so likely the original poster has a jack2 build with jackd/classic mode on but disabled jackdbus. |
@falkTX is that an option during compilation or a command line switch? |
A build option. Debian has both jackd classic and jackdbus enabled on its builds. |
You are right. I had jack2-dbus installed on one of my machines and there it didn't work. I tested on another machine where jack2-dbus wasn't installed and there it worked. The interesting thing is that the first machine is still not working after I uninstalled jack2-dbus |
Steps to reproduce the bug with OSS software (PortAudio) with the record example paex_record.exe (playback with paex_saw.exe works well): On Windows machine:
On Linux machine:
Output:
|
Since upgrading from Pipewire ~0.3.31 to 0.3.33, WineASIO has started to crash immediately when trying to use it with Pipewire's Jack implementation instead of a native Jack server.
More information about the crash: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1495
Workaround for low-latency Wine applications
Use Pipewire for handling your sound cards, and run a Jack2 server with
alsa
backend and usingpipewire
as the device.Pipewire is not able to communicate with native Jack very well, so individual clients can't directly connect between native Jack and Pipewire. You can run an individual Wine application in the native Jack server and connect other Pipewire/PW-Jack clients to the endpoints of the Jack server.
In my case, I'm using FL Studio. I'm not satisfied with using FL Studio ASIO because Wine's own PulseAudio/ALSA drivers use hidden buffers to increase stability, with the penalty of unacceptable (~60 ms) extra latency for playing virtual instruments.
The text was updated successfully, but these errors were encountered: