-
Notifications
You must be signed in to change notification settings - Fork 12
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
Fails to start while JackD is running #2
Comments
can you compile with debug turned on and provide a trace? |
Output and trace log attached |
I don't see any evidence of trying to use ALSA. PortAudio queries all the available devices, which finds the alsa devices as well as jack. Then it looks like it tries to use jack and gets killed. Are you using pipewire? |
It's not getting killed, the process is alive, the GUI simply does not show up. Upstream version (0.5) does not have this issue. |
I saw the signal at the end of the trace, but that was you manually killing tg when it was hung? tg 0.5 only supports using whatever device PortAudio decides is the default. I added device selection support. So it should be possible to select a specific direct alsa device, or use portaudio's virtual device, or use jack and select between them at run time. But it looks like trying to start PortAudio on Jack is hanging and so the GUI never comes up to select another device. I think trying to query the supported sample rates of the jack device is hanging. |
Yes, ctrl+c (SIGINT). |
This fork (master branch and package from fedora copr) fails to start while
jackd is running. The upstream version (0.5) has no issue with jack and connects
without problems.
Additionally it seems that this implementation is trying to gain exclusive access to the
selected alsa device so workarounds like alsa bridge are unusable.
This is on Fedora 36.
The text was updated successfully, but these errors were encountered: