How is PipeWire working out for you?

[Christian Fredrik Schaller]

Hi everyone,
So we have been shipping PipeWire for a bit now and Wim has of course been
pushing out regular updates with bugfixes and enhancements. So I am not a
pro-audio user myself so I wanted to ask how things are going, is PipeWire
usable as a daily driver for ProAudio folks now or do you find yourself
reverting to Jack ?

Christian

[Guido Aulisi]

Hi,
IMHO jack is still required for professional audio, there were some issues with pipewire.
I’m personally still using jack, qjackctl, a2jmidid, ardour, audacity and a bunch of LV2 plugin for professional audio.

Ciao
Guido
> Il giorno 1 lug 2021, alle ore 15:06, Christian Fredrik Schaller  ha scritto:
>
> Hi everyone,
> So we have been shipping PipeWire for a bit now and Wim has of course been pushing out regular updates with bugfixes and enhancements. So I am not a pro-audio user myself so I wanted to ask how things are going, is PipeWire usable as a daily driver for ProAudio folks now or do you find yourself reverting to Jack ?
>
> Christian
> _______________________________________________
> music mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Christian Fredrik Schaller]

On Thu, Jul 1, 2021 at 9:09 AM Guido Aulisi  wrote:
> Hi,
> IMHO jack is still required for professional audio, there were some issues
> with pipewire.
> I’m personally still using jack, qjackctl, a2jmidid, ardour, audacity and
> a bunch of LV2 plugin for professional audio.
>
> I was of course hoping for things to work great for you already with

PipeWire, but all feedback is appreciated. I hope you
keep testing PipeWire from time to time and let us know exactly where
things might still be falling down, our goal of course is to
get PipeWire to a state where it can be your daily driver as quickly as
possible.

Christian

[Guido Aulisi]

Il giorno 1 lug 2021, alle ore 15:13, Christian Fredrik Schaller  ha scritto:
> On Thu, Jul 1, 2021 at 9:09 AM Guido Aulisi  wrote:
> Hi,
> IMHO jack is still required for professional audio, there were some issues with pipewire.
> I’m personally still using jack, qjackctl, a2jmidid, ardour, audacity and a bunch of LV2 plugin for professional audio.
>
> I was of course hoping for things to work great for you already with PipeWire, but all feedback is appreciated. I hope you
> keep testing PipeWire from time to time and let us know exactly where things might still be falling down, our goal of course is to
> get PipeWire to a state where it can be your daily driver as quickly as possible.
>
> Christian

For example see:
https://bugzilla.redhat.com/show_bug.cgi?id=1949421

This is probably due to pipewire changing buffer size on the fly when another program attaches.
Changing buffer size is not supported in jconvolverp, jack does not change buffer size once started (AFAIK).

Ciao
Guido

[Be]

I love PipeWire! Yes occasionally there are bugs, which I report, but it is already quite reliable. I have played several DJ gigs with Mixxx using PipeWire through the JACK API and it worked well. The only annoyances were having to edit the PipeWire configuration file to set the sample rate to 44100 Hz to avoid resampling and needing to use the PIPEWIRE_LATENCY environment variable because there is no GUI to set an application's requested buffer size yet.

On July 1, 2021 8:06:57 AM CDT, Christian Fredrik Schaller  wrote:
> Hi everyone,
> So we have been shipping PipeWire for a bit now and Wim has of course
> been
> pushing out regular updates with bugfixes and enhancements. So I am not
> a
> pro-audio user myself so I wanted to ask how things are going, is
> PipeWire
> usable as a daily driver for ProAudio folks now or do you find yourself
> reverting to Jack ?
>
> Christian

[Keith Smith]

Hi Christian,

I've been exclusively using pipewire and been happy with it.  It has 
provided me with low latency and seems to identify all of my hardware 
correctly.  Using Carla, I'm able to re-wire my audio to fit my current 
workflow.  There have been some issues:

- When freewheeling wasn't implemented I was shutdown from rendering in 
Ardour for a couple of weeks. That's now fixed

-Ardour seemed to be unstable with pipewire. That's from both my 
experience and what I've read on various forums.

-While App developers tend to try to be helpful, there's not a wide 
acceptance of pipewire yet.  A common response is to go back to Jack, or 
switch to alsa.  I've come across several individuals in forums who 
advocate to everyone to avoid pipewire and stick with jack.

-I switched to Reaper, but Reaper fails to reconnect everything in 
pipewire.  This is annoying as every time I restart Reaper, or render in 
Reaper I have to go into Carla and reconnect my sources and sinks.

-Reaper has no way to set pipewire buffer size and I couldn't get 
jackCtl to work to control it.  Apparently this works with Jack? My work 
around is to define the environmental variable to set pipewire buffer 
when evoking Reaper from the command line,

-Gucview no longer saves audio under pipewire during video recording and 
there seems to be no progress, or even acknowledgement of where the 
problem lies.

-I customized alsa-monitoring to rename my audio interface and its 
ports, but upon updating pipewire all the customization was 
overwritten.  The update did back-up the original file, however having 
to re-do the customization every time pipewire updates is annoying

-Finally, I wish there was a set of good quality GUI utilities 
specifically for pipewire available from Fedora repository. I believe 
such utilities would go a long way in giving the impression that 
pipewire is polished and a worthy replacement for Jack and pulseaudio.

I hope this helps,

Keith

On 7/1/21 6:06 AM, Christian Fredrik Schaller wrote:
> Hi everyone,
> So we have been shipping PipeWire for a bit now and Wim has of course 
> been pushing out regular updates with bugfixes and enhancements. So I 
> am not a pro-audio user myself so I wanted to ask how things are 
> going, is PipeWire usable as a daily driver for ProAudio folks now or 
> do you find yourself reverting to Jack ?
>
> Christian
>
> music mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Christian Fredrik Schaller]

Hi Keith,
First of all thanks for the detailed feedback, more inline:

On Thu, Jul 1, 2021 at 1:21 PM Keith Smith  wrote:
> Hi Christian,
>
> I've been exclusively using pipewire and been happy with it.  It has
> provided me with low latency and seems to identify all of my hardware
> correctly.  Using Carla, I'm able to re-wire my audio to fit my current
> workflow.  There have been some issues:
> When freewheeling wasn't implemented I was shutdown from rendering in
>
> Ardour for a couple of weeks. That's now fixed
>
> -Ardour seemed to be unstable with pipewire. That's from both my
> experience and what I've read on various forums.
>
> You say seemed (as in the past), but I get the understanding here that

this is still the case for you right?
> -While App developers tend to try to be helpful, there's not a wide
> acceptance of pipewire yet.  A common response is to go back to Jack, or
> switch to alsa.  I've come across several individuals in forums who
> advocate to everyone to avoid pipewire and stick with jack.

Yeah, that is always going to be a challenge, hopefully as PipeWire gets
wider adoption and further improves the resistance will fall away.
> -I switched to Reaper, but Reaper fails to reconnect everything in
> pipewire.  This is annoying as every time I restart Reaper, or render in
> Reaper I have to go into Carla and reconnect my sources and sinks.

I have no experience with this, but can I assume that what you are saying
is that Reaper do reconnect everything if you use Jack? Or is it just that
Reaper in compared to Ardour doesn't reconnect everything?
> -Reaper has no way to set pipewire buffer size and I couldn't get jackCtl
> to work to control it.  Apparently this works with Jack?  My work around is
> to define the environmental variable to set pipewire buffer when evoking
> Reaper from the command line,

Does the workaround from Wim in comment 9 fix this issue for you?
https://bugzilla.redhat.com/show_bug.cgi?id=1949421
> -Gucview no longer saves audio under pipewire during video recording and
> there seems to be no progress, or even acknowledgement of where the problem
> lies.

Ok, something that needs to debugged further
> -I customized alsa-monitoring to rename my audio interface and its ports,
> but upon updating pipewire all the customization was overwritten.  The
> update did back-up the original file, however having to re-do the
> customization every time pipewire updates is annoying

Ok, also worth looking into what we can do.
> -Finally, I wish there was a set of good quality GUI utilities
> specifically for pipewire available from Fedora repository. I believe such
> utilities would go a long way in giving the impression that pipewire is
> polished and a worthy replacement for Jack and pulseaudio.

Agreed, it is an area where I hope the community will step up and help
though as Wim got limited time and thus things like these ends up getting
pushed down his priority list.
> I hope this helps,

It is very helpful, thank you.
> On 7/1/21 6:06 AM, Christian Fredrik Schaller wrote:
>
> Hi everyone,
> So we have been shipping PipeWire for a bit now and Wim has of course been
> pushing out regular updates with bugfixes and enhancements. So I am not a
> pro-audio user myself so I wanted to ask how things are going, is PipeWire
> usable as a daily driver for ProAudio folks now or do you find yourself
> reverting to Jack ?
>
> Christian
>
> music mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
> music mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

[Bruno Vernay]

Hi,
Currently Ardour is fine and most programs are.  It is nice to be able
to play sound from Ardour (Jack/Pipewire) and from the browser
(PA/Pipewire) without having to tweak the configuration.

Musescore still crashes instantly when configured to use Jack.  I have
to configure it to use Alsa or PA.   So I cannot have the Jack
transport synchro between Ardour and MuseScore.
Not that Musescore ever had a lot of Linux users, so I guess it will
take time until it plays nice with Jack/Pipewire.

The Pipewire configuration is still a little confusing to me, seems
like there are a lot of possibilities, but examples, uses cases would
be helpful.  I expect we will start to see more of them from the
community, as its usage expands.

Bruno

On Thu, Jul 1, 2021 at 8:16 PM Christian Fredrik Schaller
 wrote:
> Hi Keith,
> First of all thanks for the detailed feedback, more inline:
>
> On Thu, Jul 1, 2021 at 1:21 PM Keith Smith  wrote:
> > Hi Christian,
> >
> > I've been exclusively using pipewire and been happy with it.  It has provided me with low latency and seems to identify all of my hardware correctly.  Using Carla, I'm able to re-wire my audio to fit my current workflow.  There have been some issues:
> > When freewheeling wasn't implemented I was shutdown from rendering in Ardour for a couple of weeks. That's now fixed
> >
> > -Ardour seemed to be unstable with pipewire. That's from both my experience and what I've read on various forums.
>
> You say seemed (as in the past), but I get the understanding here that this is still the case for you right?
> > -While App developers tend to try to be helpful, there's not a wide acceptance of pipewire yet.  A common response is to go back to Jack, or switch to alsa.  I've come across several individuals in forums who advocate to everyone to avoid pipewire and stick with jack.
>
> Yeah, that is always going to be a challenge, hopefully as PipeWire gets wider adoption and further improves the resistance will fall away.
> > -I switched to Reaper, but Reaper fails to reconnect everything in pipewire.  This is annoying as every time I restart Reaper, or render in Reaper I have to go into Carla and reconnect my sources and sinks.
>
> I have no experience with this, but can I assume that what you are saying is that Reaper do reconnect everything if you use Jack? Or is it just that Reaper in compared to Ardour doesn't reconnect everything?
> > -Reaper has no way to set pipewire buffer size and I couldn't get jackCtl to work to control it.  Apparently this works with Jack?  My work around is to define the environmental variable to set pipewire buffer when evoking Reaper from the command line,
>
> Does the workaround from Wim in comment 9 fix this issue for you? https://bugzilla.redhat.com/show_bug.cgi?id=1949421
> > -Gucview no longer saves audio under pipewire during video recording and there seems to be no progress, or even acknowledgement of where the problem lies.
>
> Ok, something that needs to debugged further
> > -I customized alsa-monitoring to rename my audio interface and its ports, but upon updating pipewire all the customization was overwritten.  The update did back-up the original file, however having to re-do the customization every time pipewire updates is annoying
>
> Ok, also worth looking into what we can do.
> > -Finally, I wish there was a set of good quality GUI utilities specifically for pipewire available from Fedora repository. I believe such utilities would go a long way in giving the impression that pipewire is polished and a worthy replacement for Jack and pulseaudio.
>
> Agreed, it is an area where I hope the community will step up and help though as Wim got limited time and thus things like these ends up getting pushed down his priority list.
> > I hope this helps,
>
> It is very helpful, thank you.
> > On 7/1/21 6:06 AM, Christian Fredrik Schaller wrote:
> >
> > Hi everyone,
> > So we have been shipping PipeWire for a bit now and Wim has of course been pushing out regular updates with bugfixes and enhancements. So I am not a pro-audio user myself so I wanted to ask how things are going, is PipeWire usable as a daily driver for ProAudio folks now or do you find yourself reverting to Jack ?
> >
> > Christian
> >
> > music mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
> >
> > music mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
> music mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Christian Fredrik Schaller]

On Thu, Jul 1, 2021 at 3:28 PM Bruno Vernay  wrote:
> Hi,
> Currently Ardour is fine and most programs are.  It is nice to be able
> to play sound from Ardour (Jack/Pipewire) and from the browser
> (PA/Pipewire) without having to tweak the configuration.
>
> Musescore still crashes instantly when configured to use Jack.  I have
> to configure it to use Alsa or PA.   So I cannot have the Jack
> transport synchro between Ardour and MuseScore.
> Not that Musescore ever had a lot of Linux users, so I guess it will
> take time until it plays nice with Jack/Pipewire.
>
> The Pipewire configuration is still a little confusing to me, seems
> like there are a lot of possibilities, but examples, uses cases would
> be helpful.  I expect we will start to see more of them from the
> community, as its usage expands.
>
> Glad Ardour works fine for you, as for Musescore hopefully that can be

resolved.

Yeah, we hope that too, that said we are also hoping to reduce the amount
of configuration people should need to do,
ideally we should reach a point where we can detect enough of what is
happening to adjust automatically. Our medium/long term hope is
to make PipeWire work so well that musicians shouldn't need a phd in config
files to create music. So the config files will still be there of course,
but
hopefully we can make having to use them be the exception to the rule.

Christian

[Christian Fredrik Schaller]

Hi Bruno,
I checked with Hubert Figuiere who maintains the Flathub Flatpak of
musescore. He said it had problems with previous versions of PipeWire, but
that it works fine for him
with the current version of PipeWire. Would you mind testing again, maybe
test both Fedora RPM and Flathub flatpak version to see if you generally
hit the problem or if there could
be an issue with the Fedora RPM.

Christian

On Thu, Jul 1, 2021 at 3:35 PM Christian Fredrik Schaller <
[e-mail]> wrote:
> On Thu, Jul 1, 2021 at 3:28 PM Bruno Vernay  wrote:
> > Hi,
> > Currently Ardour is fine and most programs are.  It is nice to be able
> > to play sound from Ardour (Jack/Pipewire) and from the browser
> > (PA/Pipewire) without having to tweak the configuration.
> >
> > Musescore still crashes instantly when configured to use Jack.  I have
> > to configure it to use Alsa or PA.   So I cannot have the Jack
> > transport synchro between Ardour and MuseScore.
> > Not that Musescore ever had a lot of Linux users, so I guess it will
> > take time until it plays nice with Jack/Pipewire.
> >
> > The Pipewire configuration is still a little confusing to me, seems
> > like there are a lot of possibilities, but examples, uses cases would
> > be helpful.  I expect we will start to see more of them from the
> > community, as its usage expands.
> >
> > Glad Ardour works fine for you, as for Musescore hopefully that can be
>
> resolved.
>
> Yeah, we hope that too, that said we are also hoping to reduce the amount
> of configuration people should need to do,
> ideally we should reach a point where we can detect enough of what is
> happening to adjust automatically. Our medium/long term hope is
> to make PipeWire work so well that musicians shouldn't need a phd in
> config files to create music. So the config files will still be there of
> course, but
> hopefully we can make having to use them be the exception to the rule.
>
> Christian

[Bruno Vernay]

Thanks a lot it is actually working fine. I can configure Musescore to
use Jack and it does *not* crash when using the Flatpak version!
(I retested that the RPM version does crash if configured to use Jack.)
I have Musescore sending MIDI tracks to Ardour, fine.
Jack transport works if MuseScore is the Master, but not the other way
around (at least it does not crash, it just does not start)

It is funny, over the years, sometimes RPM are best to get Musescore,
sometimes it is the official AppImage and now the Flatpak version

Anyway, thanks a lot
Bruno

On Fri, Jul 2, 2021 at 3:48 PM Christian Fredrik Schaller
 wrote:
> Hi Bruno,
> I checked with Hubert Figuiere who maintains the Flathub Flatpak of musescore. He said it had problems with previous versions of PipeWire, but that it works fine for him
> with the current version of PipeWire. Would you mind testing again, maybe test both Fedora RPM and Flathub flatpak version to see if you generally hit the problem or if there could
> be an issue with the Fedora RPM.
>
> Christian
>
> On Thu, Jul 1, 2021 at 3:35 PM Christian Fredrik Schaller  wrote:
> > On Thu, Jul 1, 2021 at 3:28 PM Bruno Vernay  wrote:
> > > Hi,
> > > Currently Ardour is fine and most programs are.  It is nice to be able
> > > to play sound from Ardour (Jack/Pipewire) and from the browser
> > > (PA/Pipewire) without having to tweak the configuration.
> > >
> > > Musescore still crashes instantly when configured to use Jack.  I have
> > > to configure it to use Alsa or PA.   So I cannot have the Jack
> > > transport synchro between Ardour and MuseScore.
> > > Not that Musescore ever had a lot of Linux users, so I guess it will
> > > take time until it plays nice with Jack/Pipewire.
> > >
> > > The Pipewire configuration is still a little confusing to me, seems
> > > like there are a lot of possibilities, but examples, uses cases would
> > > be helpful.  I expect we will start to see more of them from the
> > > community, as its usage expands.
> >
> > Glad Ardour works fine for you, as for Musescore hopefully that can be resolved.
> >
> > Yeah, we hope that too, that said we are also hoping to reduce the amount of configuration people should need to do,
> > ideally we should reach a point where we can detect enough of what is happening to adjust automatically. Our medium/long term hope is
> > to make PipeWire work so well that musicians shouldn't need a phd in config files to create music. So the config files will still be there of course, but
> > hopefully we can make having to use them be the exception to the rule.
> >
> > Christian

[Christian Fredrik Schaller]

ok, hopefully the maintainer of the Fedora RPM is on this list and can take
a look at figuring what is wrong.

Christian

On Fri, Jul 2, 2021 at 3:36 PM Bruno Vernay  wrote:
> Thanks a lot it is actually working fine. I can configure Musescore to
> use Jack and it does *not* crash when using the Flatpak version!
> (I retested that the RPM version does crash if configured to use Jack.)
> I have Musescore sending MIDI tracks to Ardour, fine.
> Jack transport works if MuseScore is the Master, but not the other way
> around (at least it does not crash, it just does not start)
>
> It is funny, over the years, sometimes RPM are best to get Musescore,
> sometimes it is the official AppImage and now the Flatpak version
>
> Anyway, thanks a lot
> Bruno
>
> On Fri, Jul 2, 2021 at 3:48 PM Christian Fredrik Schaller
>  wrote:
> > Hi Bruno,
> > I checked with Hubert Figuiere who maintains the Flathub Flatpak of
>
> musescore. He said it had problems with previous versions of PipeWire, but
> that it works fine for him
> > with the current version of PipeWire. Would you mind testing again,
>
> maybe test both Fedora RPM and Flathub flatpak version to see if you
> generally hit the problem or if there could
> > be an issue with the Fedora RPM.
> >
> > Christian
> >
> > On Thu, Jul 1, 2021 at 3:35 PM Christian Fredrik Schaller <
>
> [e-mail]> wrote:
> > > On Thu, Jul 1, 2021 at 3:28 PM Bruno Vernay
>
> wrote:
> > > > Hi,
> > > > Currently Ardour is fine and most programs are.  It is nice to be able
> > > > to play sound from Ardour (Jack/Pipewire) and from the browser
> > > > (PA/Pipewire) without having to tweak the configuration.
> > > >
> > > > Musescore still crashes instantly when configured to use Jack.  I have
> > > > to configure it to use Alsa or PA.   So I cannot have the Jack
> > > > transport synchro between Ardour and MuseScore.
> > > > Not that Musescore ever had a lot of Linux users, so I guess it will
> > > > take time until it plays nice with Jack/Pipewire.
> > > >
> > > > The Pipewire configuration is still a little confusing to me, seems
> > > > like there are a lot of possibilities, but examples, uses cases would
> > > > be helpful.  I expect we will start to see more of them from the
> > > > community, as its usage expands.
> > >
> > > Glad Ardour works fine for you, as for Musescore hopefully that can be
>
> resolved.
> > > Yeah, we hope that too, that said we are also hoping to reduce the
>
> amount of configuration people should need to do,
> > > ideally we should reach a point where we can detect enough of what is
>
> happening to adjust automatically. Our medium/long term hope is
> > > to make PipeWire work so well that musicians shouldn't need a phd in
>
> config files to create music. So the config files will still be there of
> course, but
> > > hopefully we can make having to use them be the exception to the rule.
> > >
> > > Christian
>
> --
> Bruno VERNAY

[Keith Smith]

Hi Christan,

I also responded inline below:

On 7/1/21 11:15 AM, Christian Fredrik Schaller wrote:
> Hi Keith,
> First of all thanks for the detailed feedback, more inline:
>
> On Thu, Jul 1, 2021 at 1:21 PM Keith Smith <[e-mail] 
> > wrote:
> Hi Christian,
>
> I've been exclusively using pipewire and been happy with it.  It
> has provided me with low latency and seems to identify all of my
> hardware correctly.  Using Carla, I'm able to re-wire my audio to
> fit my current workflow.  There have been some issues:
>
> - When freewheeling wasn't implemented I was shutdown from
> rendering in Ardour for a couple of weeks. That's now fixed
>
> -Ardour seemed to be unstable with pipewire. That's from both my
> experience and what I've read on various forums.
>
> You say seemed (as in the past), but I get the understanding here that 
> this is still the case for you right?

The main issue with Ardour is that the plugins I wanted to use (vital 
synth, sfizz) were constantly crashing Ardour.   I switched to Reaper 
about 3 weeks ago and haven't played with Ardour since. Reaper, besides 
having a ton of features beyond Ardour, seems very stable with plugins.  
It doesn't use pipewire to internally interconnect and show up in Carla 
as a single block with just hardware in/out ports
> -While App developers tend to try to be helpful, there's not a
> wide acceptance of pipewire yet.  A common response is to go back
> to Jack, or switch to alsa.  I've come across several individuals
> in forums who advocate to everyone to avoid pipewire and stick
> with jack.
>
> Yeah, that is always going to be a challenge, hopefully as PipeWire 
> gets wider adoption and further improves the resistance will fall away.

If you're interested and want to read a bunch of musicians gripping 
about linux check out my thread here:

https://forum.cockos.com/showthread.php?t=254750

Also, please let me know if I said something incorrect.
> -I switched to Reaper, but Reaper fails to reconnect everything in
> pipewire.  This is annoying as every time I restart Reaper, or
> render in Reaper I have to go into Carla and reconnect my sources
> and sinks.
>
> I have no experience with this, but can I assume that what you are 
> saying is that Reaper do reconnect everything if you use Jack? Or is 
> it just that Reaper in compared to Ardour doesn't reconnect everything?

Since i do not have jack installed I can only guess at what jack users 
are experiencing.  I haven't found anyone complaining about reconnection 
issues.  Ardour was good at reconnecting, Reaper both randomly re-orders 
its ports and seems to randomly reconnect up to the wrong sources and 
sinks.  I haven't files a bug report with them because its difficult to 
explain, and a course I use pipewire.
> -Reaper has no way to set pipewire buffer size and I couldn't get
> jackCtl to work to control it. Apparently this works with Jack? 
> My work around is to define the environmental variable to set
> pipewire buffer when evoking Reaper from the command line,
>
> Does the workaround from Wim in comment 9 fix this issue for you? 
> https://bugzilla.redhat.com/show_bug.cgi?id=1949421 
> https://bugzilla.redhat.com/show_bug.cgi?id=1949421

I don't think this is related.  When you select jack as the audio 
backend in Reaper it no longer provides a means to change the buffer 
size.  I tried setting it in QJackCtl first, but that didn't seem to 
work.  I since added

bash -c "PIPEWIRE_LATENCY=256/48000 /opt/REAPER/reaper" %F

to the advanced setion of the KDE launcher Reaper application and that 
worked. (except I can't change it on the fly, which would be nice).

To tell the truth, I'm not sure how to debug this very well
> -Gucview no longer saves audio under pipewire during video
> recording and there seems to be no progress, or even
> acknowledgement of where the problem lies.
>
> Ok, something that needs to debugged further
> -I customized alsa-monitoring to rename my audio interface and its
> ports, but upon updating pipewire all the customization was
> overwritten.  The update did back-up the original file, however
> having to re-do the customization every time pipewire updates is
> annoying
>
> Ok, also worth looking into what we can do.
> -Finally, I wish there was a set of good quality GUI utilities
> specifically for pipewire available from Fedora repository. I
> believe such utilities would go a long way in giving the
> impression that pipewire is polished and a worthy replacement for
> Jack and pulseaudio.
>
> Agreed, it is an area where I hope the community will step up and help 
> though as Wim got limited time and thus things like these ends up 
> getting pushed down his priority list.
> I hope this helps,
>
> It is very helpful, thank you.
> On 7/1/21 6:06 AM, Christian Fredrik Schaller wrote:
> > Hi everyone,
> > So we have been shipping PipeWire for a bit now and Wim has of
> > course been pushing out regular updates with bugfixes and
> > enhancements. So I am not a pro-audio user myself so I wanted to
> > ask how things are going, is PipeWire usable as a daily driver
> > for ProAudio folks now or do you find yourself reverting to Jack ?
> >
> > Christian
> >
> > _______________________________________________
> > music mailing list [e-mail]  <mailto:[e-mail]>
> > To unsubscribe send an email [e-mail]  <mailto:[e-mail]>
> > Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/  <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
> > List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines  <https://fedoraproject.org/wiki/Mailing_list_guidelines>
> > List Archives:https://lists.fedoraproject.org/archives/list/[e-mail]  <https://lists.fedoraproject.org/archives/list/[e-mail]>
> > Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure  <https://pagure.io/fedora-infrastructure>
> _______________________________________________
> music mailing list -- [e-mail]
> <mailto:[e-mail]>
> To unsubscribe send an email to
> [e-mail]
> <mailto:[e-mail]>
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> <https://fedoraproject.org/wiki/Mailing_list_guidelines>
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> <https://lists.fedoraproject.org/archives/list/[e-mail]>
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
> <https://pagure.io/fedora-infrastructure>
>
>
> music mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure