Other projects using #libwebrtc will pick it automatically one they land/enable #PipeWire camera support. I.e. Chromium/Electron and hopefully soon #gnomeweb

"If you fancy freeing yourself from tethered speakers or uncomfortable headphones and have a spare Raspberry Pi, Frédéric Danis‘ step-by-step tutorial will show you how to turn any pair of speakers into a high-quality Bluetooth audio system." https://all3dp.com/1/best-raspberry-pi-projects/

#OpenSource #Bluetooth #PipeWire

GNOME is shaping up really nicely for privacy

• Background App indicator
• App permissions
• Device Security Settings
• Mic / Camera* indicators
• Screen Sharing indicator
• Remote Desktop indicator
• Location indicator
• Incrementally better app sandboxing
• VPN (incl Wireguard) support
• Quick Network Toggles

Made possible by #Flatpak #Wayland #PipeWire and our talented community.

#Linux #privacy #WireGuard #VPN #GNOME #freedesktop

* Available in the upcoming GNOME 45 release

#QEMU 8.1 Released with New #PipeWire Audio Backend, Multi-Touch Support for the GTK GUI, and Many Improvements for #ARM and #RISCV https://9to5linux.com/qemu-8-1-released-with-new-pipewire-audio-backend-many-improvements

#OpenSource #FreeSoftware #KVM #virtualization

ICYMI: Ashok Sidipotu's talk "WirePlumber: Propelling PipeWire for embedded", recorded at #EmbeddedOSSummit in Prague, explores #WirePlumber, the modular session manager for #PipeWire? : https://col.la/eossas

Interested in learning more about #WirePlumber, the modular session manager for #PipeWire? Ashok Sidipotu presents "WirePlumber: Propelling PipeWire for embedded", recorded at #EmbeddedOSSummit in Prague: https://col.la/eossas @pipewire

Good old times, where are you? Todays topic: #sound

My laptop, now on #Debian #bookworm, (and #PipeWire "just works". That is, music plays either via the local speaker, a USB Audio device, a Headphone, a USB headphone (one of those used for video calls), one or two bluetooth connected speakers or, now also, via HDMI. Without a hassle. It even remembers things when I plug/unplug. It lets me easily (KDE, something in the task bar) change stuff around, and it also has no problem to have one source push to multiple of the targets - at home music usually goes to two at the same time. You can even easily adjust the delay that one of them needs.

No long fiddling with any setup, magic or tools, it just works.

(Compared to the customer laptop that runs a recent copy of the #Windows fuckup that #microsoft dares to name "Operating system" - that one is overburdened just dealing with local speaker and usb headphones and breaks on that often enough). No idea why anyone uses that crap system.

3. A simple API. If your app has its own #v4l2 handling code, switching to #PipeWire gives you a much nicer API to work with. This is especially true if your app already support screen sharing on #Wayland - in that case you already have both #PipeWire and portal support and can reuse a lot of that. That's for example done in #libwebrtc for #Firefox and #Chromium.

2. If you use #GStreamer for cameras #PipeWire support in turn comes for free via the PW GST plugin. Additionally supporting proper #Flatpak sandboxing via the camera portal is possible with little work using #libportal or #ashp and the `GstPipeWireDeviceProvider`. Feel free to ping me if you need help with this - there'll also be a new example in #workbench for this soon.

(this thread is written in real-time and on satellite inet, so please bear with me :P).

While "complex" cameras have been common for phones and professional cameras for a long time now, the linux ecosystem more or less got away with only supporting UVC cameras via V4L2.

By now more and more laptops using non-UVC cameras are entering the market on one hand and new use-cases like #LinuxMobile become more common on the other.

Switching to #PipeWire gives you support for #libcamera for free.

So we'll have a neat little camera indicator in #gnome45.

It will only show up for apps that use #PipeWire for camera access so we depend on more apps switching to it.

During the #GUADEC2023 "State of the Shell" talk I was asked what incentives there are for app developers to do so and unfortunately I messed up to make the probably most convincing ones, so short 🧵

1. support for modern cameras via #libcamera (as opposed to only #v4l2 / UVC cameras).

#GUADEC

#PipeWire 0.3.75 is pretty important for #libcamera and thus #LinuxMobile. It allows #wireplumber to ensure to advertise cameras only once, even if both the libcamera and the v4l2 backends are active. This opens the door for distros to install/enable the libcamera backend by default everywhere, using it only for devices that are not supported by the v4l2 backend alone - avoiding possible regressions.

Apart from that the release closes a nasty camera portal issue.

@capyloon Here are the patches: https://bugzilla.mozilla.org/show_bug.cgi?id=1843786

We can hopefully upstream the #webrtc patches so all variants of #Firefox and #Chromium have good camera support on #LinuxMobile

#PipeWire #libcamera

@dino 0.4.3 just got released with some exciting improvements for #LinuxMobile

1. Several fixes for touch input, making audio/video calls actually usable on phones
2. Fixes for video support so devices with #libcamera / #pipewire support like the #PinePhonePro work now
3. The app is now recognized as mobile friendly on #Phosh
4. Stricter #Flatpak sandbox - no device/all any more

The new version is available on #Flathub and lots of distro repos.

#GNOME #xmpp #Jabber

@awai assuming that the main attack vendor will be network connected apps such as messengers, and further assuming that the complexity of such apps will for the foreseeable future stay too high to make them really secure - IMHO also a strong case for sandboxed apps.

I.e. using #Flatpak and portals - especially for camera and microphone access. We're getting closer with the former, having more and more apps support cameras via #PipeWire. The later is still further away unfortunately.

One of the issue preventing #LinuxMobile distros from shipping a #PipeWire / #libcamera camera stack is the fact that it requires #wireplumber as session manager, which again does not always play nicely with #pulseaudio, if that is still used as sound server.

Unfortunately switching to PW for sound is not always possible yet because some mobile-specific packages depend on PA. So if you want to help with camera enablement, please consider helping with issues such as https://source.puri.sm/Librem5/wys/-/issues/13 :)

This is @halfmexican; GNOME Outreachy student excited that their effort to make a modern and sandboxed Camera demo for Workbench has paid off 🛠️

Well done! 🎉

Thanks @philn and @slomo for your help!

#GNOME #Outreachy #development #students #GStreamer #PipeWire #Flatpak #freedesktop #libcamera #GTK

#EmbeddedOSSummit: Ashok Sidipotu detailing the fundamental changes to #WirePlumber's configurations system. #PipeWire #OpenSource

#EmbeddedOSSummit: Our last presentation of the day is up next at 13:05 UTC: Ashok Sidipotu presents "WirePlumber: Propelling #PipeWire for #embedded". South Hall 3B https://sched.co/1LcNl

Tomorrow at #EmbeddedOSSummit: #MediaTek upstreaming, stateless #V4L2 video encoding & a look at the changes coming to #WirePlumber, PipeWire's session manager! Join us! https://col.la/eoss #PipeWire #Embedded