On Sat, 3 Jul 2021, John Murphy wrote:
On Wed, 30 Jun 2021 16:11:47 -0700 M. Edward (Ed) Borasky wrote:
The biggest issue with Pipewire IMHO is that it does not support
Ubuntu 18.04 LTS. That will be a big obstacle to growth until 18.04 is
no longer supported, which is still about two years
On 6/30/21 3:58 PM, Robin Gareus wrote:
Yes, and ALSA as well to some extent. To applications pipewire looks
like a running JACK server, or pulseaudio or like an ALSA device. So
existing apps do not have to be changed.
When the Jack option is enabled in Pipewire it expects Jack >= 1.9.10 to
On 07/07/21 22:37, Fons Adriaensen wrote:
On Wed, Jul 07, 2021 at 09:58:52PM +0100, Filipe Coelho wrote:
You keep mentioning up that patch, but it only worked for you, it didn't for
anyone else.
It was used for years on the WFS system in Parma, until I switched to
Jack2 in order to have
On Wed, Jul 07, 2021 at 09:58:52PM +0100, Filipe Coelho wrote:
> Except your patch was super messy, not formatted correctly and lead to other
> issues, as described here:
It was indeed a very big one, and fixed several issues:
* wrong order of execution of clients,
* high order polynomial
On Wed, 7 Jul 2021, 22:55 Fons Adriaensen, wrote:
> On Wed, Jul 07, 2021 at 10:44:23PM +0200, Fons Adriaensen wrote:
>
> > With jack2 this takes 0.5s to create the clients, and on average 0.1s to
> > connect all of them in a chain (15 * 32 connect calls).
>
> Correction: after removing some
On 07/07/21 21:44, Fons Adriaensen wrote:
On Wed, Jul 07, 2021 at 01:00:21PM +0200, Wim Taymans wrote:
Challenge accepted!... I made a little jack client with 32 input and 32 output
ports that memcpy the samples. Then I started 16 of those and linked them
all in a long chain.
Then I linked
On Wed, Jul 07, 2021 at 10:44:23PM +0200, Fons Adriaensen wrote:
> With jack2 this takes 0.5s to create the clients, and on average 0.1s to
> connect all of them in a chain (15 * 32 connect calls).
Correction: after removing some print() statements the total connections
time was reduced to 50
On Wed, Jul 07, 2021 at 01:00:21PM +0200, Wim Taymans wrote:
> Challenge accepted!... I made a little jack client with 32 input and 32 output
> ports that memcpy the samples. Then I started 16 of those and linked them
> all in a long chain.
>
> Then I linked the input of the chain to a USB mic
On 7/7/21 9:59 AM, Fernando Lopez-Lezcano wrote:
On 7/7/21 4:00 AM, Wim Taymans wrote:
...
== install patched rtkit in which priorities and cpu usage limits have
been changed to more audio dsp friendly values
< NOTE: max realtime priorities in rtkit are hardwired (in the source
code!!) and
On 7/7/21 4:00 AM, Wim Taymans wrote:
On Tue, 6 Jul 2021 at 21:41, Fons Adriaensen wrote:
I'll give PW its chance when the developers tell me it's ready for
real life. Which will mean a session with around 15 jack clients
with a total of 800 or so ports. Should run without hickups while
On Wed, 7 Jul 2021 at 14:05, Filipe Coelho wrote:
>
> On 07/07/21 12:37, Robin Gareus wrote:
> > On 7/7/21 1:00 PM, Wim Taymans wrote:
> >> This utterly fails with jackd on this system, it doesn't even want
> >> to start all the clients, I'm sure it's something with the config
> >> somewhere...
On 07/07/21 12:37, Robin Gareus wrote:
On 7/7/21 1:00 PM, Wim Taymans wrote:
This utterly fails with jackd on this system, it doesn't even want
to start all the clients, I'm sure it's something with the config somewhere...
jack has a port-limit (IIRC 256 by default). It is not dynamic and
On 7/7/21 1:00 PM, Wim Taymans wrote:
> This utterly fails with jackd on this system, it doesn't even want
> to start all the clients, I'm sure it's something with the config somewhere...
jack has a port-limit (IIRC 256 by default). It is not dynamic and
unbound for performance reasons.
try:
On Tue, 6 Jul 2021 at 21:41, Fons Adriaensen wrote:
>
>
> I'll give PW its chance when the developers tell me it's ready for
> real life. Which will mean a session with around 15 jack clients
> with a total of 800 or so ports. Should run without hickups while
> watching a youtube movie and
On Wed, 7 Jul 2021 09:31:10 +0200
Fons Adriaensen wrote:
>On Tue, Jul 06, 2021 at 03:54:22PM -0700, Fernando Lopez-Lezcano wrote:
>
>> Yes, yes, agreed. And most of the time you cannot remove stuff, and that is
>> by design.
>
>That has been my impression as well.
>
>> I long for simple text
On Tue, Jul 06, 2021 at 03:54:22PM -0700, Fernando Lopez-Lezcano wrote:
> Yes, yes, agreed. And most of the time you cannot remove stuff, and that is
> by design.
That has been my impression as well.
> I long for simple text configuration files, you change it, restart whatever
> it is if it is
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
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
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
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).
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
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
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.
>
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
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
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/
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
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). Everything seems to just work.
On Thu, Jul 01, 2021 at 06:57:59PM -0400, bill-auger wrote:
> On Thu, 1 Jul 2021 07:01:31 +0100 Keith wrote:
>
> the distro is not at fault for "failing" to support something,
> which did not exist, or was very immature, or proprietary, when
> the dirsto was released
>
The distro is at fault
A few weeks ago, before my Ubuntu Studio 20.04 + KX Studio beastie died --
it was an 11-year-old laptop that finally got knocked off of a table -- I
tried Pipewire and completely messed up the system. Prior to that I had
Cadence nicely integrating ALSA, PulseAudio, and JACK. At least, it seemed
to
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). Everything seems to just work. The only thing
I had to set was the Profile for the
Cool! I'll check it out!
On Fri, Jul 2, 2021 at 6:12 PM John Murphy wrote:
>
> On Wed, 30 Jun 2021 16:11:47 -0700 M. Edward (Ed) Borasky wrote:
>
> > The biggest issue with Pipewire IMHO is that it does not support
> > Ubuntu 18.04 LTS. That will be a big obstacle to growth until 18.04 is
> > no
On Wed, 30 Jun 2021 16:11:47 -0700 M. Edward (Ed) Borasky wrote:
> The biggest issue with Pipewire IMHO is that it does not support
> Ubuntu 18.04 LTS. That will be a big obstacle to growth until 18.04 is
> no longer supported, which is still about two years away. I don't know
> what's involved
On 7/2/21 1:32 AM, M. Edward (Ed) Borasky wrote:
The particular incident that relates to Pipewire arose from the latter
category - I saw some interesting writing about Pipewire and wanted to
experiment with it on the NVIDIA Jetsons. They ship with an
NVIDIA-supported operating system called
Let me say a bit more about my situation. I run a mix of Windows 10/11
(including Windows Subsystem for Linux) and Linux audio software. Some
is proprietary with a corporate support model, some is bundled with
hardware (NVIDIA Jetsons and Bela) and supported by the hardware
vendor, and some is
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 Pipewire. This is a Ubuntu problem, not a Pipewire one. If it
> matters
On Thu, 1 Jul 2021 07:01:31 +0100
Keith Edmunds 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 Pipewire. This is a Ubuntu problem, not a Pipewire one. If it
> 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 Pipewire. This is a Ubuntu problem, not a Pipewire one. If it
matters to an 18.04 user, they do have the option of upgrading to
The biggest issue with Pipewire IMHO is that it does not support
Ubuntu 18.04 LTS. That will be a big obstacle to growth until 18.04 is
no longer supported, which is still about two years away. I don't know
what's involved in doing a backport, but I for one would use Pipewire
if it was working on
On 7/1/21 12:48 AM, Yuri wrote:
> Somebody said on GitHub that "Pipewire is the soon to be successor to
> Jack/Pulseaudio".
Yes, and ALSA as well to some extent. To applications pipewire looks
like a running JACK server, or pulseaudio or like an ALSA device. So
existing apps do not have to be
Somebody said on GitHub that "Pipewire is the soon to be successor to
Jack/Pulseaudio".
I ran a quick search in this ML and couldn't find any mentions of it in
the last few years.
Is Pipewire viewed like this by the wider community? Does anybody have
experience using it?
41 matches
Mail list logo
