Date: Thu, 04 Jan 2024 23:40:22 +0000 From: bugzilla-noreply@freebsd.org To: desktop@FreeBSD.org Subject: [Bug 276121] audio/pulseaudio: enable JACK by default Message-ID: <bug-276121-39348@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276121 Bug ID: 276121 Summary: audio/pulseaudio: enable JACK by default Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: desktop@FreeBSD.org Reporter: lexi.freebsd@le-fay.org Assignee: desktop@FreeBSD.org Flags: maintainer-feedback?(desktop@FreeBSD.org) Created attachment 247450 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D247450&action= =3Dedit patch i realise there's always a compromise on what options a port should enable = by default, but in this case, i think there's a significant benefit to enabling JACK by default, because it allows PulseAudio to act as a front-end to JACK= for desktop users. my situation is this: i have an audio interface in OSS, and i use that as t= he JACK input and output device, in realtime, bitperfect mode, with VCHANs disabled. this means i don't want anything else (including pulseaudio) to attempt to open the OSS device. this is so i can use the audio device via = JACK in an audio application like audio/ardour. but i also want to run normal desktop applications, like Firefox, mpv, etc., which already have PulseAudio support. by far the easiest way for me to do this is to run PulseAudio with the JACK sink/source modules, which causes everything to work normally and without any modifications. i believe this = kind of configuration would be fairly common for anyone interesting in doing aud= io production on FreeBSD. enabling JACK by default means i can do all this with the binary packages, instead of having to build pulseaudio from source. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276121-39348>