Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread Fernando Lopez-Lezcano
On 7/6/21 12:41 PM, Fons Adriaensen wrote: On Tue, Jul 06, 2021 at 12:37:55PM +0100, Will Godfrey wrote: At one time you added things that you wanted. These days you have to remove what you don't want - but might not even know was there until it interferes with what you want to do. This is *e

Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread John Murphy
New problem. I run jack_capture, at certain times, via cron. Can run the script manually and it works fine, but just doesn't start from the cronjob. I have no idea why. Same story with arecord and pw-record (which has no -d duration). Script works fine from command line, but no joy from the cront

Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread Fons Adriaensen
On Tue, Jul 06, 2021 at 12:37:55PM +0100, Will Godfrey wrote: > At one time you added things that you wanted. These days you have to remove > what you don't want - but might not even know was there until it interferes > with what you want to do. This is *exactly* what I profoundly hate about the

Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread Fernando Lopez-Lezcano
On 7/4/21 6:25 PM, Robin Gareus wrote: On 7/4/21 6:35 PM, John Murphy wrote: On Wed, 30 Jun 2021 15:48:31 -0700 Yuri wrote: [...] Does anybody have experience using it? https://pipewire.org/ Yes. I've used it for a whole day now, on Linux Mint 20.1 Ulyssa base (Ubuntu 20.04 focal). Everythin

Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread John Murphy
On Tue, 6 Jul 2021 15:27:53 +0100 I wrote: > I may have to do one of those. I think James Szinger's prediction [1] > is accurate, although, while I am confused I am not yet "wailing". > Now wailing with joy having found a workaround. Simply need to send 'play' to jack_transport after any 'locate'.

Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread John Murphy
On Mon, 5 Jul 2021 03:25:09 +0200 Robin Gareus wrote: > On 7/4/21 6:35 PM, John Murphy wrote: > > On Wed, 30 Jun 2021 15:48:31 -0700 Yuri wrote: > > [...] > >> Does anybody have experience using it? > >> > >> https://pipewire.org/ > > > > Yes. I've used it for a whole day now, on Linux Mint 20

Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread Will Godfrey
On Tue, 6 Jul 2021 12:42:06 +0200 Fons Adriaensen wrote: >On Tue, Jul 06, 2021 at 12:05:00PM +0200, Wim Taymans wrote: > >> The pipewire daemon is meant to be small and modular. You could run >> a custom version of that with only what you want. It could possibly be >> smaller than jack. > >Syst

Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread Fons Adriaensen
On Tue, Jul 06, 2021 at 12:05:00PM +0200, Wim Taymans wrote: > The pipewire daemon is meant to be small and modular. You could run > a custom version of that with only what you want. It could possibly be > smaller than jack. Systemd started off like that as well... and now it has its tentacles ev

Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread Fons Adriaensen
On Tue, Jul 06, 2021 at 10:04:28AM +0100, Will Godfrey wrote: > What on earth has this got to do with systemd? Although I > suppose I shouldn't be surprised with it coming from redhat. I've started moving away from systemd on all systems. Not finished yet but getting close. Had a look at the PW

Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread Will Godfrey
On Tue, 6 Jul 2021 10:51:17 +0200 Dominique Michel wrote: > For pipewire, as >systemd is an optional run time depend Why? What on earth has this got to do with systemd? Although I suppose I shouldn't be surprised with it coming from redhat. -- Will J Godfrey https://willgodfrey.bandcamp.com/ h

Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?

2021-07-06 Thread Dominique Michel
Le Thu, 1 Jul 2021 18:57:59 -0400, bill-auger a écrit : > On Thu, 1 Jul 2021 07:01:31 +0100 Keith wrote: > > > The biggest issue with Pipewire IMHO is that it does not support > > > Ubuntu 18.04 LTS. > > > > I would suggest you have that round the wrong way: Ubuntu 18.04 > > doesn't support