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
> Maybe pipewire is not run by the same user than the cron job.
This was my initial idea, however what I think is more likely is that there
is no dbus session for the process to connect to.
Are you running PW as a user or system-wide?
___
Le Wed, 7 Jul 2021 19:24:38 +0100,
John Murphy a écrit :
> On Wed, 7 Jul 2021 19:01:25 +0100 Keith Edmunds wrote:
>
> /tmp/cronjob.txt says error: pw_context_connect() failed: Host is down
Maybe pipewire is not run by the same user than the cron job.
Dominique
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
Hello again!
The 'Vee One Suite' of 'old-school' software instruments,
* synthv1 [1] as a polyphonic subtractive synthesizer;
* samplv1 [2] a polyphonic sampler synthesizer;
* drumkv1 [3] as yet another drum-kit sampler;
* padthv1 [4] as a polyphonic additive synthesizer.
Are all being
On Wed, 7 Jul 2021 19:33:18 +0100 Keith Edmunds wrote:
> > /tmp/cronjob.txt says error: pw_context_connect() failed: Host is down
>
> I can't help you with that, sorry, but hopefully it points the way to
> resolving the problem.
Hopefully it will mean something to someone if/when I write to
> /tmp/cronjob.txt says error: pw_context_connect() failed: Host is down
I can't help you with that, sorry, but hopefully it points the way to
resolving the problem.
--
Great music, chat and even some wit.
Join me every Friday evening at 8pm for
Keith's Music Box:
Follow:
On Wed, 7 Jul 2021 19:01:25 +0100 Keith Edmunds wrote:
> Try:
>
> /usr/bin/pw-record /home/john/crontest.wav > /tmp/cronjob.txt 2>&1
>
> ...and have a look in /tmp/cronjob.txt after it's run
/tmp/cronjob.txt says error: pw_context_connect() failed: Host is down
I've no idea what that means, or
> Thanks, but no change, except the syslog entry:
> Jul 7 18:20:01 NUC1 CRON[10931]: (john) CMD (/usr/bin/pw-record
> /home/john/crontest.wav)
Try:
/usr/bin/pw-record /home/john/crontest.wav > /tmp/cronjob.txt 2>&1
...and have a look in /tmp/cronjob.txt after it's run
--
Great music, chat and
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 Wed, 7 Jul 2021 16:50:48 +0100 Keith Edmunds wrote:
> The first thing I'd suggest is to put the full pathname of both the
> command and the wav file. Under cron, the PATH variable may not be what
> you have interactively:
>
> /usr/bin/pw-record /home/me/crontest.wav (edit as required)
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
The first thing I'd suggest is to put the full pathname of both the
command and the wav file. Under cron, the PATH variable may not be what
you have interactively:
/usr/bin/pw-record /home/me/crontest.wav (edit as required)
> Could someone please do a simple test on any Pipewire
Could someone please do a simple test on any Pipewire installation
set up to use/replace Jack (or shed any light on this).
If I run 'pw-record crontest.wav' it works fine, as expected.
If I run 'pw-cat 2> er.txt' ditto, of course.
If I setup a user cronjob with 'crontab -e' to run the
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 07/07/21 09:54, Louigi Verona wrote:
Not a single complaint about systemd in this thread. In fact, I think
systemd is the good guy here.
systemd is awesome and I can't imagine moving forwards without it!
(there broke the link again, talking back about systemd hehe)
But seriously, the way
Hey Keith,
Loved your message. First, I can relate. We've all been there: bad morning,
not enough coffee, and then bham! Someone is wrong on the Internet. My
life's story.
Second, the fact that you wrote an email asking why everyone is complaining
about systemd means that your first email to the
On 2021-07-07 09:51, Keith Edmunds wrote:
Most of the mails I've seen so far are people whining about systemd.
Well. YMMV but if there is a discussion about the problem of systemd and audio
it's probably not whining.
Is that normal for this list,
No
or have I just joined at the wrong
Hi, I'm new to the list.
Most of the mails I've seen so far are people whining about systemd.
Is that normal for this list, or have I just joined at the wrong time? I
really don't need to read about systemd on this list.
Thank you,
Keith
--
Great music, chat and even some wit.
Join me every
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
29 matches
Mail list logo
