Skip to content
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

Not every linux system has jack_lsp #508

Closed
plexus opened this issue Nov 10, 2023 · 2 comments
Closed

Not every linux system has jack_lsp #508

plexus opened this issue Nov 10, 2023 · 2 comments

Comments

@plexus
Copy link
Contributor

plexus commented Nov 10, 2023

Overtone currently shells out to a command line tool to make the jack connections. These are often packaged separately, so they are not available on every system, see also comments in #467 .

This will become even more so with Pipewire becoming the default.

We should at least fail gracefully with a warning message to manually connect your outputs. We could also use JNA jack to do the connections.

@hlolli
Copy link
Member

hlolli commented Nov 10, 2023

Supercollider is usually run with jack on linux, but I don't see why alsa shouldn't also work, even if it doesn't have the same realtime capabilities. If it works on upstream Supercollider, it could be used as fallback if neither jack nor pipewire exists.

@plexus
Copy link
Contributor Author

plexus commented Jan 6, 2024

We now use casa.squid.jack, based on JNA Jack, to make the connections. This also has the benefit that we can ask jack which the physical output ports are, rather than coming up with increasingly intricate regexps to help us guess. So auto-connect should work once again on all linux system, for both PipeWire and Jackd setups, with or without jack_lsp / jack_connect present.

@plexus plexus closed this as completed Jan 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants