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. 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 ➜ gst-device-monitor-1.0 | grep pipewire <no output> ➜ gst-device-monitor-1.0 | grep pw <no output> ➜ gst-launch-1.0 -v pipewiresrc ! audioresample ! autoaudiosink Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... <clip> Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: pipewireclock0 <clip> Interrupt: Stopping pipeline ... Execution ended after 0:00:05.618247799 Setting pipeline to NULL ... Freeing pipeline ... ➜ gst-launch-1.0 -v alsasrc ! audioresample ! autoaudiosink Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstAudioSrcClock <clip> Interrupt: Stopping pipeline ... Execution ended after 0:00:06.362230774 Setting pipeline to NULL ... Freeing pipeline ... _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue