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

Allow JACK access from inside sandbox #14

Closed
ssssam opened this issue Mar 25, 2020 · 1 comment
Closed

Allow JACK access from inside sandbox #14

ssssam opened this issue Mar 25, 2020 · 1 comment

Comments

@ssssam
Copy link
Collaborator

ssssam commented Mar 25, 2020

Since Flatpak 1.6.1 apps can request access to /dev/shm, which allows them to connect to a JACK daemon outside the sandbox. See flatpak/flatpak#1509 for details.

This nay provide a better experience than the current hack of using padsp and the OSS backend, which can suffer latency due to going via PulseAudio and has a lockup bug too.

The JACK access is totally unsandboxed. We should switch to using Pipewire as soon as that becomes practical.

@ssssam
Copy link
Collaborator Author

ssssam commented May 20, 2020

This is not actually possible, as explained here: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/1001#note_323464727

@ssssam ssssam closed this as completed May 20, 2020
ssssam added a commit that referenced this issue Jul 20, 2020
We were previously accessing pulseaudio via OSS, but this worked very
badly.

By using the 'pulse' audio device we can work against pulseaudio by
default, and direct hardware access is still available for advanced
users who are willing to give Purr Data exclusive soundcard access.

The OSS and JACK backends are now disabled. Direct access to JACK
from inside Flatpak is unsupported and broken (see
#14) while
Pipewire support is not yet ready (see
#11).

Fixes #10
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

1 participant