home.social

#pulseaudio — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pulseaudio, aggregated by home.social.

  1. I was trying to listen to an audiobook using VLC. The MP3 files contained a mono track and VLC was playing it through only one headphone.

    I found out it was caused by the selected output module. To fix it, I opened Settings → Tools → Preferences → Audio and switched the output module from PipeWire to PulseAudio.

    #VLC #PulseAudio

  2. Unity (game engine) having severe lag spikes from PulseAudio on Ubuntu 24.04.4 #pulseaudio #unity3d

    askubuntu.com/q/1566594/612

  3. Considered: PulseAudio module-tunnel-source. Load it on the remote, point at the local PA server. Same native protocol, no SSH tunnel.

    The cost: the auth cookie travels in the clear. No encryption.

    SSH tunnel gives encryption for free. That is not a small thing.

    #PulseAudio #SSH #Privacy #Linux #SelfHosting

  4. What's Pulseaudio's problem? A2DP works for two days. Today, it's unavailable (again) and my Bluetooth headset only connects with HFP, with no option to switch to A2DP. It's totally random. Re-pairing doesn't help. Killing Pulseaudio doesn't help either. Killing Bluetooth doesn't help either. Restarting my laptop doesn't help either. Will A2DP be available again tomorrow? Maybe. Maybe not. Its availability switches between days. Maybe it's related to the weather? Maybe to political news? This is so annoying! I would be really grateful for any lasting tips to fix this Pulseaudio A2DP headset mess. I don't want HFP. I don't need HFP. I just want to listen to my music. With my Bluetooth headset.

    #linux #LinuxMint #pulseaudio #a2dp #hfp #bluetooth

  5. Lenovo IdeaPad Slim 5 15ARP10 (83J3) - No speaker sound with Conexant SN6140 on Ubuntu 26.04 #sound #pulseaudio #lenovo #alsa

    askubuntu.com/q/1566336/612

  6. Durante el fin de semana también trabajé en la integración de los permisos para Wayland, XWayland y las aplicaciones Snap. Ahora estos permisos aparecen en una ventana emergente y se activan de inmediato, y se pueden consultar o editar más tarde en la configuración del sistema.

    En el caso de Snaps, ten en cuenta que no utilizamos el módulo de políticas snapd (por lo que c...

    Sigue en t.me/ubports_noticias/489

    #Wayland #XWayland #PulseAudio #UBports #UbuntuTouch #Lomiri #SoftwareLibre #GNULinux

  7. Durante el fin de semana también trabajé en la integración de los permisos para Wayland, XWayland y las aplicaciones Snap. Ahora estos permisos aparecen en una ventana emergente y se activan de inmediato, y se pueden consultar o editar más tarde en la configuración del sistema.

    En el caso de Snaps, ten en cuenta que no utilizamos el módulo de políticas snapd (por lo que c...

    Sigue en t.me/ubports_noticias/489

    #Wayland #XWayland #PulseAudio #UBports #UbuntuTouch #Lomiri #SoftwareLibre #GNULinux

  8. Durante el fin de semana también trabajé en la integración de los permisos para Wayland, XWayland y las aplicaciones Snap. Ahora estos permisos aparecen en una ventana emergente y se activan de inmediato, y se pueden consultar o editar más tarde en la configuración del sistema.

    En el caso de Snaps, ten en cuenta que no utilizamos el módulo de políticas snapd (por lo que c...

    Sigue en t.me/ubports_noticias/489

    #Wayland #XWayland #PulseAudio #UBports #UbuntuTouch #Lomiri #SoftwareLibre #GNULinux

  9. Durante el fin de semana también trabajé en la integración de los permisos para Wayland, XWayland y las aplicaciones Snap. Ahora estos permisos aparecen en una ventana emergente y se activan de inmediato, y se pueden consultar o editar más tarde en la configuración del sistema.

    En el caso de Snaps, ten en cuenta que no utilizamos el módulo de políticas snapd (por lo que c...

    Sigue en t.me/ubports_noticias/489

    #Wayland #XWayland #PulseAudio #UBports #UbuntuTouch #Lomiri #SoftwareLibre #GNULinux

  10. #PulseAudio network audio between my two laptops (at least receiving, never figured out microphones properly) now works so reliably that I frequently forget which device my headset is actually connected to, which leads to me sounding like talking through a toilet paper roll because teams only finds the built-in microphone on my webcam as input device 😅

  11. So, mein Manjaro-Arbeitssystem erfolgreich von #Pulseaudio auf #Pipewire umgestellt, weil #Niri sonst die Audiodevices nicht findet. Eigentlich ist Pipewire ja der Standard, aber die Installation ist wohl doch schon ne Weile her. Das Schönste: Hat auf Anhieb geklappt. #linux

  12. Tip: You can setup an audio input channel as a monitor of any audio output using `pavucontrol` on Linux

    In other words, if you have audio playing through speakers, you can record those samples with another app which can save them to file. Great for recording audio from VOIP calls and other streams locally

    #audio #linux #PulseAudio

  13. @iju Aika paljon vaikuttaa työpöytäympäristö (jos sellaista edes on); periaatteessa varmasti komentorivin työkaluillakin (#PulseAudio / #Jack) joku osaa säätöjä tehdä, mutta helpottaa, kun on graafinen kikkare kuten kuvan #Plasma'ssa. Toisessa koneessa, jossa emolevyn äänipiirin lisäksi on vanha #SoundBlasterZ, ”profiilien” luettelo on vielä hulppeasti pidempi.

  14. I switched from #pulseaudio to #pipewire some weeks ago.
    Now I need to found out how to make jackd-applications (#Hydrogen, #Ardour mostly but some others as well in the future) work, and it seems not an easy task.
    (Yes I know pipewire-jack and qpwgraph exists and I'm looking at those right now)

    #debian #linux #music #MAO #jackd

  15. The latest release of the newest major branch of #PulseAudio is two years ago. Maybe it is time to abandon PulseAudio.

    reference: gitlab.freedesktop.org/pulseau

  16. Using a to boot device before installing a flake. ISO seems to have an implicit default enabling . When upgrading to higher version, PulseAudio options are removed/deprecated and cause service.pulseaudio does not exist during nixos-rebuild switch (before the flake). Flow is: sudo nix-channel --update (24.05 metadata only) → patch configuration.nix for audio compatibility → sudo nixos-rebuild switch. Curious if this is expected behaviour?

  17. @justine

    Heya! I've been daily-driving it for nearly a month on my main at-home laptop (Thinkpad X260).

    It's pretty great! ZFS is darn near bulletproof, and after some initial challenges of getting wifi and GUI configured, it was pretty "boring"... until I tried upgrading to 15.0, lol

    Figured out how to roll back to 14.3, and I'm now waiting for 15.1 before I try again (although I believe the issues I had have now been resolved, but I'm still going to wait ;)

    Package availability is amazing (better than Debian in some cases!), and most things compile without any issues, although some things that don't have very well-written Makefiles are iffy and I got stuck.

    Been having fun with Dosbox-X, playing games I loved 20-30 years ago. I couldn't get the Linux version of Kerbal Space Program to run under compat_linux, but I didn't really expect it to.

    #OpenBSD definitely gets my vote for noob-friendly #BSD, since it has X11 in the base install, and it configures itself, but I now have sway (Wayland) running under #FreeBSD just as if I were still on Linux, so as long as someone is willing to skim through the pertinent parts of the handbook, it's a great OS.

    The only downsides to #FreeBSD vs. Linux is that S3 resume takes a little longer (8 seconds instead of 1-3 seconds), and I have occasional hiccups, which I'm sometimes not able to recover from. Loading some websites in Firefox will make everything hang for several seconds at times (even though I'm launching Firefox via nice (1)), and there are some times that sway never quite recovers from S3 suspend, although that's rare. The good thing is that sometimes it will catch the power button and shut down cleanly, and even when it doesn't, #ZFS is so bulletproof that it just takes it all in stride.

    There are occasional Linuxisms that feel a bit odd, like some of my packages (the swaync notification system and the duckstation console emulator are notable examples) require #pulseaudio of all things, which sometimes eats up my CPU. That's... really weird to me. I liked how minimal sndio on OpenBSD is.

    Both major BSDs have very sane syntax for the config file that governs Wifi access points, and that's very refreshing to me after using a TUI to join networks on #Debian (although it's definitely possible to uninstall #NetworkManager on Debian and use the native interface config files, but they're not as nice/simple as the BSDs').

    One really fun (if a bit cartoonish) way of comparing the BSD philosophy to the Linux philosophy is to look at doas vs sudo, specifically man doas.conf, then man sudoers.

    The manpage for the sudoers file is pretty long and convoluted, as is the syntax for the file itself. doas.conf is super brief and to-the-point, and its manpage is pretty concise.

    I think once they add the setup tool for GUIs to the FreeBSD setup wizard, that will be a real game-changer.

    P.S., I haven't really daily-driven OpenBSD in a while, but I'm planning on getting an adapter so I can power my OpenBSD Thinkpad X200t off of a power bank, instead of the very dodgy third-party battery, so I can experiment with OpenBSD some more. I know the latest version has fixed the problems I was having with Emoji support, so I think that OS deserves another look. With the little bit of experimentation I've done in the last week, I've been pleasantly surprised with even Firefox' performance on that little Core 2 Duo. The only bummer about OpenBSD to me is the lack of ZFS or any other modern filesystem, so the occasional power losses or hang-ups become much more dangerous.

    Edit: minor clarifications

  18. Si alguien tiene problemas con #Joplin en #Linux puede deberse a un bug de su versión de #Electron en escritorios con #Wayland actualizados al interactuar con #PulseAudio.
    Si a alguien más le sirve esta información y prueba a desactivar/desconectar dispositivos de sonido para que Joplin deje de quedarse colgado al inicio, me alegro. 💛

  19. @jwcph

    ALSA are drivers to talk to hardware - 90% of audio interfaces (whatever enables you to plug an audio cable into your computer) use ALSA. (exceptions are FireWire interfaces and some other). if a new audio interface is 'incompatible' with Linux, it means it doesn't have an ALSA driver (aka kernel module) - yet.

    on top of #ALSA drivers (so, using those drivers) there were two systems in last decade:

    1. PulseAudio - designed to be invisible way to handle all desktop audio - mutiple application would be able to send sound to your audio output (to ALSA). not capable of low-latency audio needed for professional music/audio work. if you had multiple outputs (ALSA), like HDMI or analog out, you could choose one of those for a particular application (like web browser), and similarly for inputs (microphones etc)

    2. JACK audio server - low latency, designed for pro audio work, allowed completely free patching between multiple applications (ins and outs), standalone audio plugins, and audio interface(s) - essentially infinite patchbay among "everything". all decent audio apps work with JACK, but not 'desktop' apps, something like web browsers for example.

    at first #JACK and #PulseAudio were incompatible - you were supposed to suspend (or uninstall) PulseAudio in order to use JACK and vice-versa. they fought for access to ALSA. Later on, bridges were developed so you could send sound from web browser (that was using PulseAudio) to your DAW (that was using JACK) or output from DAW to OBS or Zoom...

    audio apps needed code to talk to any of these two systems. they needed to be compatible with JACK, or/and PulseAudio.

    last few years PipeWire ( @pipewire ) appeared to replace JACK and Pulse at the same time and be very transparent and invisible but still configurable if you so needed. Like JACK and PulseAudio it also sits on top of ALSA drivers, but "acts" like it's Pulse and/or JACK. the idea seems to be that replacing JACK and PulseAudio is easy if nothing needs to be changed in those apps. so applications think they are sending audio to JACK but are actually sending it to PipeWire 'in disguise'. it's extremely good at pretending (tech speak: it uses same API). So, if you are using (running) PipeWire, you cannot use (run) JACK or/and PulseAudio.

    PipeWire is amazing solution. it also automatically discoveres new audio devices like usb headphones, or Bluetooth speakers and makes the default audio output. you can unplug your audio devices and apps won't notice. It's still a bit rough on the edges, but it's getting better and better.

    MIDI? well, it's complicated: there's ALSA MIDI and JACK MIDI. Just two different systems trying to do patching between apps. So some apps will show one, and some the other. I think PipeWire tries to make this irrelevant by bridging these two, but it's not always successful. It should be accessible in PipeWire patchbay app like 'qpwgraph'.

    Sorry if that's too long, but I hope it is understandable enough. And sorry for so many edits.

    #LinuxAudio

  20. [SOLVED]

    Ich verwende #LinuxMint 22.2 und möchte sechs Audiokanäle separat einstellen. Ich nutze #PipeWire mit #qpwgraph, habe aber gelesen, dass #PulseAudio die Verbindungen vergisst, sobald das Gerät getrennt wird. Deshalb möchte ich JACK-Audio-Clients verwenden, die sich in diesem Fall automatisch wieder verbinden.
    Das Problem: Wenn ich JACK-Audio-Clients in #OBS Studio erstelle, werden sie in qpwgraph nicht angezeigt.

    #Linux #LinuxHelp #OBSstudio

  21. As I was playing with the #Liquidsoap #docker image (without #podman, though), I was surprised how hard it is (and few documented) to play on the host's #pulseaudio from the #container. So here is the trick : mkir.ch/2025-11-18/play-sound-

  22. If, after an upgrade, your #sound suddenly refuses to work with an error that no such sound profile is available - forget all the internet stuff about random #bluetooth, #pulseaudio or #pipewire and other stuff. Try deleting `.config/wireplumber/wireplumber.conf` first, it might just be an old version and #wireplumber refusing to work means no sound.

  23. Are you a PRO hacker on #pipewire on #LINUX ?? Can you help me to get #SWH 's #LADSPA or #LV2 compressor plugins inserted as the default sink , like it was easy and possible under #pulseaudio ? see awerner.myhome-server.de/doku. for a working puleaudio example. Find the plugins here: github.com/swh

  24. Boosts welcome:
    Looking for some experience exchange about audio session managers on Linux.
    I am enjoying Ray Session on Ununtu Studio a lot. Which one is your favorite, and why?

    #linuxaudio #sessionmanager #raysession #jack #alsa #pipewire #pulseaudio #ubuntustudio