Re: Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)
> * re-evaluate situation for f35 beta freeze to make a default switch. > > Although a bit slower than expected, I guess more testing is good. It sounds > like an acceptable plan to me. > I'm not sure how it works, if spinoffs can/want to make an earlier switch? I feel that based on testing if there are no caveats discovered the switch could still be made for F34 as the default and there could be an easy switch back to PulseAudio if users need it for some reason. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)
I can confirm that this works great. I've used it with BlueJeans without issue. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)
> On Tue, Nov 24, 2020 at 3:30 PM Tom Seewald > Currently the PipeWire developers have been doing it by hand while > they are developing the software. I have been going through and fixing > things so that regular folks can do it semi-automatically. Are there instructions available for this semi-automatic process to test this change now? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)
I'm very excited about this change and ultimately want to be able to test it out but it seems that there are still package dependency issues. How can I test this out on my end using the repos in their current state on either Fedora 33 or Rawhide? I've got a few systems I can test on to see if there are any regressions, and don't mind running Rawhide to do some testing. Is there a write-up of how to test this that we can follow in the meantime until the packaging fixes land in Rawhide, or should end-users wait until Pipewire is packaged and set as default in a nightly Rawhide build? It seems like it would greatly benefit the Fedora project to get as many people trying this change out as possible. -- Dylan Taylor ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
