Pulse Audio releases Vivid Strings series Violins 2 for Kontakt https://rekkerd.org/pulse-audio-releases-vivid-strings-series-violins-2-for-kontakt/
@itsfoss 1 correction though: You claim “you can't rely on ALSA as it will take control of the entire sound device, so you can only use it to handle one application at a time. So no hardware multiplexing.”
That’s false. I remember my main advantage switching from OSS to ALSA was being to play 2 apps at the same time. I still feel like #PulseAudio is the new kid on the block—now I feel old
https://en.wikipedia.org/wiki/Advanced_Linux_Sound_Architecture explicitly lists “Hardware mixing of multiple channels.” as a feature.
Does anyone of a #linux / #ubuntu bent out there know how to connect to chromecast audio devices in this Brave New World of #pipewire?
It was really easy with #pulseaudio and #dlna to reroute the output of specific apps to chromecast devices, but I can't figure it out at all with pipewire.
I just want to play music from #cider on my hifi
Save 40% on Virhamonic’s Bohemian series virtual instruments https://rekkerd.org/virhamonic-bohemian-series-virtual-instruments-sale/
Regarding the #postmarketos 24.06 release (congrats and thanks to all contributors!) I wanted to add a detail that I think wasn't really mentioned in the posts I saw so far: this release come with #libcamera + #pipewire support by default - even if #pulseaudio is used for audio.
That means that screensharing on #wayland should work OOTB and - more crucially - that a camera stack is in place that allows a much greater number of apps to use cameras - including sandboxed ones.
Do you use #pipewire, #pulseaudio, #jack or #alsa with your #daw? Personally, I use PipeWire with WirePlumber and I am pretty satisfied with it. #linuxaudio #linux #musicproduction
FreeBSD Project-packaged Chromium 125.0.6422.76 will default to PulseAudio, if PulseAudio is enabled.
Please test 125.0.6422.76 or greater with FreeBSD 14.1-BETA3 or a release candidate. 14.1 includes significant improvements to audio (release notes are not yet complete).
<https://github.com/freebsd/freebsd-ports/commit/6acad34cb2bc3b858f64724620fd3c11b2a602f3>
@itsfoss Pipewire is better because it supports audio and video devices and does both PulseAudio and JACK functionality. But the correct answer would be, "the one that works for me!" If Pipewire not working properly, then continue using PulseAudio.
The long wait is over for users of FreeBSD.
Uncomplicated use of PulseAudio is on the horizon.
Thanks to:
— Lennart Poettering @pid_eins
— Christos Margiolis
— The FreeBSD Foundation @FreeBSDFoundation for sponsorship and other initiatives
– Colin Percival @cperciva for recent release engineering
— everyone else who directly and indirectly progressed things, over the years …
<https://freebsdfoundation.org/our-donors/donors/>
<https://github.com/freebsd/freebsd-src/commit/d692c314d29a310efe875e9be05b0ccebe6b241d>
<https://github.com/freebsd/freebsd-src/commit/3f5f38755b8f521401283370770bc375fe71a725>
@nina_kali_nina That UI reminds me of Gnome 3 :'(
I'm trying to build it now but it looks like it might require pulseaudio under linux. A complete dealbreaker for me if true. I do not negotiate with pulseaudio. It gets removed from everything I use and has never caused me anything but trouble when installed.