Re: gstreamer pipeline directly using pipewire device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 06 Aug 2022 05:30:32 -0000
Adam Chasen via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

> I am hoping for some guidance on if I should be using pipewiresrc (vs
> alsasrc) in my gstreamer pipeline.
> 
> From my understanding we fully switched over to PipeWire for managing
> audio devices in Fedora. To me, this means all "non-pipewire"
> interfaces (PulseAudio, ALSA, OSS, etc) are now using compatibility
> layers to plumb the audio to PipeWire. I presume that the "most
> correct" pipeline source object type to use is pipewiresrc.

alsa is the hardware layer.  It supports the drivers for all audio
devices on the system.  Pulse and pipewire give access to alsa devices
in a more user friendly way and add capabilities that alsa doesn't
have.  They both use alsa to access the actual devices. The official
switch in Fedora is from pulseaudio to pipewire as an enhancement layer.
I think I still see new pulseaudio versions available, so maybe it will
still work. But, whichever you choose, it should be the only one active
on the system at any time.  Two managers (pulseaudio and pipewire), one
employee (alsa), not a recipe for good things happening.

> If the answer is to use pipewiresrc, how can I inspect the pipewire
> "devices" seen by gstreamer?  `gst-device-monitor-1.0` only shows the
> expected PipeWire devices via the ALSA api. The upstream
> documentation indicates the devices should be listed as of 2 years
> ago
> https://github.com/PipeWire/pipewire/blob/master/README.md#running-gstreamer-applications

When I looked at this, I was also confused.  There doesn't seem to be a
clear translation from the alsa device assignment / label to the
pipewire device assignment / label. My investigation was months ago,
so it could have changed in the meantime, and could still be changing.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux