Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 be installed, despite Pipewire being Jack's successor. Yuri ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Simple Pipewire test request
> 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? ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Simple Pipewire test request
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 ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 parallel execution, as well as in the production studio of La Casa della Musica, on various systems operated by the univerities of Parma, Bologna, and Pesaro, by the RAI (Italian public radio & TV) and three private Linux-based music studios. None of those reported any problems. So stop spreading plain lies. I don't think it is a lie when nobody else reported it to work. Maybe your changes were in a copy that got reused? I am not doubting that it worked for you. Of course it did. But the patch, when applied, didn't work as for other as it did for you. Maybe something went wrong with the diff procedure.. I don't know now. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 complexity of several basic operations. This all depended on new data structures, and there was no way to split it up in smaller steps without introducing non-functional intermediates. > 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 parallel execution, as well as in the production studio of La Casa della Musica, on various systems operated by the univerities of Parma, Bologna, and Pesaro, by the RAI (Italian public radio & TV) and three private Linux-based music studios. None of those reported any problems. So stop spreading plain lies. -- FA ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 print() statements the total connections > time was reduced to 50 ms on average (jack2 of course). > > My script spawns jack_connect 480 times, It's probably going to be faster with an application... I'll try to get some measurements of that later. Wim > Ciao, > > -- > FA > ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 the input of the chain to a USB mic and the output to another USB card (it needs to do adaptive resampling to keep this going), That takes about 6 seconds to setup on my machine. I run this with a buffer size of 128 samples and 48KHz. ... With jack1 this fails miserably. Reason is probably that jack1 recomputes the graph for each and every connection change, even if the actual client dependencies don't change [1]. ... [1] This was one of the many things that my rejected patch (years ago) actually fixed. IIRC the complexity of jack_connect() in jackd1 is at least O(n^2) if not O(n^3) where n is the number of existing connections - this doesn't scale. Except your patch was super messy, not formatted correctly and lead to other issues, as described here: https://lists.linuxaudio.org/archives/linux-audio-user/2021-February/113821.html and then Rui added a note: https://lists.linuxaudio.org/archives/linux-audio-user/2021-February/113822.html You keep mentioning up that patch, but it only worked for you, it didn't for anyone else. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 ms on average (jack2 of course). Ciao, -- FA ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 and the output to another > USB card (it needs to do adaptive resampling to keep this going), > > That takes about 6 seconds to setup on my machine. I run this with a buffer > size of 128 samples and 48KHz. Tried something similar: 16 instances of JackGainctl (from zita-jacktools) with 32 channels (i.e. 64 ports) each, run from a Python script. 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). With jack1 this fails miserably. Reason is probably that jack1 recomputes the graph for each and every connection change, even if the actual client dependencies don't change [1]. Plain unpatched kernel, with -p256, no xruns after one hour. > Works okish, some xruns here and there and this is a stock fedora setup > with extra rtprio for the user. No low latency kernel or any tuning. I had to > increase the max fds to 8192. Why on earth do you need that many kernel objects (fds) to synchronise just 16 processes ? Again something doesn't scale here... > 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... See above if you were using jackd1. [1] This was one of the many things that my rejected patch (years ago) actually fixed. IIRC the complexity of jack_connect() in jackd1 is at least O(n^2) if not O(n^3) where n is the number of existing connections - this doesn't scale. Ciao, -- FA ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] [ANN] Vee One Suite 0.9.23 - An Early-Summer'21 Release batch #2
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 released as the second batch of the so called 'QStuff*' (northern) Early-Summer'21 season. Notable changes for this season are as follows: - Fixed some ages old Glide/portamento potential crash bug (as reported by AnClark, while on synthv1 [1]; also applies to samplv1 [2] and padthv1 [4]). - Add support for LV2 UI Windows platform (by AnClark, also while on synthv1 [1]). - Sustenuto pedal controller (MIDI CC#66) is now implemented. - Fixed old Sustain/Damper/Hold pedal controller (MIDI CC#64) note-off processing. (also implemented new on drumkv1 [3]) - Have some tolerance for buffer-size changes. - All builds default to Qt6 (Qt >= 6.1) where available. - CMake [12] is now the official build system. As usual, all delivered in dual form: - a pure stand-alone JACK client with JACK-session [5], NSM (Non Session Management [6]) and both JACK MIDI and ALSA MIDI [7] input support; - a LV2 instrument plug-in [8]. The 'Vee One Suite' are free, open-source Linux Audio [10] software, distributed under the terms of the GNU General Public License (GPL) [11] version 2 or later. And again in detail... **synthv1 - an old-school polyphonic synthesizer [1] ** synthv1 0.9.23 (early-summer'21) is released! synthv1 is an old-school all-digital 4-oscillator subtractive polyphonic synthesizer with stereo fx. LV2 URI: http://synthv1.sourceforge.net/lv2 website: https://synthv1.sourceforge.io http://synthv1.sourceforge.net project page: https://sourceforge.net/projects/synthv1 downloads: https://sourceforge.net/projects/synthv1/files - source tarball: https://download.sf.net/synthv1/synthv1-0.9.23.tar.gz - source package: https://download.sf.net/synthv1/synthv1-0.9.23-64.1.rncbc.suse.src.rpm - binary packages (openSUSE Tumbleweed): https://download.sf.net/synthv1/synthv1-jack-0.9.23-64.1.rncbc.suse.x86_84.rpm https://download.sf.net/synthv1/synthv1-lv2-0.9.23-64.1.rncbc.suse.x86_84.rpm - AppImage [9] package (JACK stand-alone only): https://download.sf.net/synthv1/synthv1-jack-0.9.23-64.1.x86_64.AppImage git repos: https://git.code.sf.net/p/synthv1/code https://github.com/rncbc/synthv1.git https://gitlab.com/rncbc/synthv1.git https://bitbucket.org/rncbc/synthv1.git **samplv1 - an old-school polyphonic sampler [2]** samplv1 0.9.23 (early-summer'21) is released! samplv1 is an old-school polyphonic sampler synthesizer with stereo fx. LV2 URI: http://samplv1.sourceforge.net/lv2 website: https://samplv1.sourceforge.io http://samplv1.sourceforge.net project page: https://sourceforge.net/projects/samplv1 downloads: https://sourceforge.net/projects/samplv1/files - source tarball: https://download.sf.net/samplv1/samplv1-0.9.23.tar.gz - source package: https://download.sf.net/samplv1/samplv1-0.9.23-64.1.rncbc.suse.src.rpm - binary package (openSUSE Tumbleweed): https://download.sf.net/samplv1/samplv1-jack-0.9.23-64.1.rncbc.suse.x86_84.rpm https://download.sf.net/samplv1/samplv1-lv2-0.9.23-64.1.rncbc.suse.x86_84.rpm - AppImage [9] package (JACK stand-alone only): https://download.sf.net/samplv1/samplv1-jack-0.9.23-64.1.x86_64.AppImage git repos: https://git.code.sf.net/p/samplv1/code https://github.com/rncbc/samplv1.git https://gitlab.com/rncbc/samplv1.git https://bitbucket.org/rncbc/samplv1.git **drumkv1 - an old-school drum-kit sampler [3]** drumkv1 0.9.23 (early-summer'21) is released! drumkv1 is an old-school drum-kit sampler synthesizer with stereo fx. LV2 URI: http://drumkv1.sourceforge.net/lv2 website: https://drumkv1.sourceforge.io http://drumkv1.sourceforge.net project page: https://sourceforge.net/projects/samplv1 downloads: https://sourceforge.net/projects/drumkv1/files - source tarball: https://download.sf.net/drumkv1/drumkv1-0.9.23.tar.gz - source package: https://download.sf.net/drumkv1/drumkv1-0.9.23-64.1.rncbc.suse.src.rpm - binary package (openSUSE Tumbleweed): https://download.sf.net/drumkv1/drumkv1-jack-0.9.23-64.1.rncbc.suse.x86_84.rpm https://download.sf.net/drumkv1/drumkv1-lv2-0.9.23-64.1.rncbc.suse.x86_84.rpm - AppImage [9] package (JACK stand-alone only): https://download.sf.net/drumkv1/drumkv1-jack-0.9.23-64.1.x86_64.AppImage git repos: https://git.code.sf.net/p/drumkv1/code https://github.com/rncbc/drumkv1.git https://gitlab.com/rncbc/drumkv1.git https://bitbucket.org/rncbc/drumkv1.git **padthv1 - an old-school polyphonic additive synthesizer [4]** padthv1 0.9.23 (early-summer'21) is released! padthv1 is an old-school polyphonic additive synthesizer with stereo fx. padthv1 is based on the PADsynth algorithm by Paul Nasca, as a special variant of additive synthesis. LV2 URI:
Re: [LAD] Simple Pipewire test request
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 Pipewire/ issues and I know how to see cron errors now, so it's all good. I'll wait a while, hoping someone can try it on their Pipewire system. Would prove if it's just a local problem. Thinking the host might be up if there was already a recording happening; I started a recording manually first, but no change. -- Thanks again, John. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Simple Pipewire test request
> /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: https://www.facebook.com/KMBEngland On Friday go to: https://www.mixcloud.com/live/KeithsMusicBox/ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Simple Pipewire test request
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 why that should be so. I tried with arecord in place of /usr/bin/pw-record and got: arecord: main:852: audio open error: Host is down. -- Thanks, John. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Simple Pipewire test request
> 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 even some wit. Join me every Friday evening at 8pm for Keith's Music Box: Follow: https://www.facebook.com/KMBEngland On Friday go to: https://www.mixcloud.com/live/KeithsMusicBox/ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 cannot be changed, same for scheduling ring (also hardwired in the source code to SCHED_RR, does not allow use of SCHED_FIFO), so for testing I built a patched rtkit package > BZZT! WRONG!! rtkit can be "configured" by using runtime parameters when started. Sigh, I did not realize that was possible, I should have dived deeper and/or RTFR (the README, no man page). Better than nothing but IMHO not a realistic configuration strategy (in my case it would involve editing the systemd unit that starts the service). -- Fernando ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Simple Pipewire test request
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) 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) -- John. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 watching a youtube movie and compiling a kernel at the same time (which I can do now without any problem). 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 and the output to another USB card (it needs to do adaptive resampling to keep this going), That takes about 6 seconds to setup on my machine. I run this with a buffer size of 128 samples and 48KHz. Then I started firefox and loaded a video. Then I also started compiling all of GStreamer on all cores. Here is the screenshot: https://people.freedesktop.org/~wtay/pw-load.png Works okish, some xruns here and there and this is a stock fedora setup with extra rtprio for the user. No low latency kernel or any tuning. Just to see if it makes a difference xrun-wise you could try rebooting with the "preempt=full" kernel option. Recent Fedora 5.12* kernels are built with HAVE_PREEMPT_DYNAMIC=y so it should be possible to change preemption from "voluntary" (the default in Fedora, pretty lame for audio work) to "full" which is much better - but not as good as an RT patched kernel. < the okish part is, well, not goodish enough because of the xruns, ha ha - but then again when running jackd you may get the same performance, depends on tuning, frames per period or "quantum" size, etc > I had to increase the max fds to 8192. I'm sure you can eliminate more xruns with some tuning. 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... This is probably not a representative setup but at 16+ clients and 1024+ ports we're ballpark.. It probably starts to fail more with some real processing. I'll have to re-test, but when I last tested rtprio was not really doing the right thing for me when running pipewire as a jackd replacement (tested using supernova, the DSP multi-core sound synthesis engine of SuperCollider). If anyone cares to read really boring stuff about my tests (Jun 18, so maybe outdated) I am including some stuff I documented at the end of this email... maybe some of this has been fixed (my proposed solution was to drink a lot of wine[*] :-) While testing I found a scalability bug in the feedback loop detection, which should be fixed now. It might explain startup delays with complex projects... Ah, can't wait to test with my complex ardour sessions - which were failing to load in a "reasonable" time. -- Fernando [*] actual wine, not the Windows emulator version == some rt priority testing, June 18 2021 ... Several issues... more diving into source code, including supernova... < I did file a ticket with rtkit git about the hardwired limits that do not allow for audio workstation usage, we'll see if I get any answers > This is all in xxx (Fedora 34) == 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 cannot be changed, same for scheduling ring (also hardwired in the source code to SCHED_RR, does not allow use of SCHED_FIFO), so for testing I built a patched rtkit package > == install the real jack, run jack @ priority 65 - supernova threads: all FF (SCHED_FIFO), all priority 60 which is 5 less than main jackd thread, this is the normal expected behavior when using jackd $ ps -eLo pid,class,rtprio,pri,pcpu,stat,comm --sort -rtprio | grep DSP 1151907 FF 60 100 0.5 SLl+ DSP Thread 0 1151907 FF 60 100 0.0 SLl+ DSP Thread 1 1151907 FF 60 100 0.0 SLl+ DSP Thread 2 == install pipewire-jack, set pipewire to use the rtkit module, set priority for pipewire to be 88, set priority for jack to be 71 (in local account pipewire configuration) - supernova threads: not what it should be, first thread is the right priority but wrong scheduling class (SCHED_RR which is hardwired in rtkit), second and third are the right scheduling class (SCHED_FIFO) but wrong priority. I don't know how this is happening (some clues at the end of the email). $ ps -eLo pid,class,rtprio,pri,pcpu,stat,comm --sort -rtprio | grep DSP 1152815 RR 71 111 0.5 SLl+ DSP Thread 0 1152815 FF 20 60 0.0 SLl+ DSP Thread 1 1152815 FF 20 60 0.0 SLl+ DSP Thread 2 supernova complains on startup: Warning: cannot raise thread priority - pipewire threads: running at the right priority and scheduling class (which is hardwired in rtkit) $ ps -eLo pid,class,rtprio,pri,pcpu,stat,comm --sort
Re: [LAD] Simple Pipewire test request
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 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 commands > (at the start of the next minute or so) the first does nothing, > while the second works. > > Cron writes to /var/log/syslog like: > > CRON[7694]: (john) CMD (pw-record crontest.wav) > rtkit-daemon[1277]: Supervising 7 threads of 4 processes of 1 users > > (second line repeated) > > -- > John (older than 95.6% of the population). > ___ > Linux-audio-dev mailing list > Linux-audio-dev@lists.linuxaudio.org > https://lists.linuxaudio.org/listinfo/linux-audio-dev -- Great music, chat and even some wit. Join me every Friday evening at 8pm for Keith's Music Box: Follow: https://www.facebook.com/KMBEngland On Friday go to: https://www.mixcloud.com/live/KeithsMusicBox/ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] Simple Pipewire test request
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 commands (at the start of the next minute or so) the first does nothing, while the second works. Cron writes to /var/log/syslog like: CRON[7694]: (john) CMD (pw-record crontest.wav) rtkit-daemon[1277]: Supervising 7 threads of 4 processes of 1 users (second line repeated) -- John (older than 95.6% of the population). ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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... > > jack has a port-limit (IIRC 256 by default). It is not dynamic and > > unbound for performance reasons. > I got the same script working on JACK2 (minus the youtube video), I needed to increase mlock limits. JackLinuxFutex uses MAP_LOCKED, which can fail when there is too much locked already. JACK2 takes about the same amount of time to create the clients and set up the links and uses about the same amount of DSP (-+25%) as PipeWire. Wim ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 unbound for performance reasons. This limit was bumped in v1.9.15 to 256 clients and 2048 ports. See https://jackaudio.org/news/2020/10/15/jack2-v1915-release-and-current-status.html These can still be changed at compile time, as always. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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: jackd --port-max 1024 -d alsa ... -- robin OpenPGP_signature Description: OpenPGP digital signature ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 compiling a kernel at the same time > (which I can do now without any problem). 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 and the output to another USB card (it needs to do adaptive resampling to keep this going), That takes about 6 seconds to setup on my machine. I run this with a buffer size of 128 samples and 48KHz. Then I started firefox and loaded a video. Then I also started compiling all of GStreamer on all cores. Here is the screenshot: https://people.freedesktop.org/~wtay/pw-load.png Works okish, some xruns here and there and this is a stock fedora setup with extra rtprio for the user. No low latency kernel or any tuning. I had to increase the max fds to 8192. I'm sure you can eliminate more xruns with some tuning. 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... This is probably not a representative setup but at 16+ clients and 1024+ ports we're ballpark.. It probably starts to fail more with some real processing. While testing I found a scalability bug in the feedback loop detection, which should be fixed now. It might explain startup delays with complex projects... Wim > > Ciao, > > -- > FA > > > ___ > Linux-audio-dev mailing list > Linux-audio-dev@lists.linuxaudio.org > https://lists.linuxaudio.org/listinfo/linux-audio-dev ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Whining
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 systemd manages boot scripts makes complete sense on a multi-threaded system. The complex dependencies of some services would be a very painful thing to manage without it. Then integration with libsystemd means custom written code can notify when a service is truly ready. For example, when dealing with jack one no longer needs "jack_wait -w", jackd can notify the exact instance/time it is ready for use and services that depend on jack can start nicely without needing hacks to wait for startup. People hate change, and also the complexities systemd brings (also being monolithic). Which is very understandable, but doesn't negate it has great points too. As someone that had to do dev-ops and system adminstration, systemd is a "god send" as they say. Compared to the time I had to setup stuff on Alpine/OpenRC, systemd is a bliss and don't want to go back anymore. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Whining
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 list was to complain about the list! And you are asking if you belong? Man, you're now one of us. Complaining about the list is the secret first step to becoming the list's veteran, so, welcome! Finally, I love the elegance of the solution. You've actually broken the link. We're now talking about something else! Not a single complaint about systemd in this thread. In fact, I think systemd is the good guy here. Louigi Verona https://louigiverona.com/ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Whining
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 time? You can read the archives and you probably see that it's a list about linux audio dev. https://lists.linuxaudio.org/archives/linux-audio-dev/ 156 appearances of systemd since 2009 (start 2002) 38429 messages since then. So, 0.4% is about systemd. I think you are safe. I really don't need to read about systemd on this list. See my first comment. Cheers, -- /bengan ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] Whining
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 Friday evening at 8pm for Keith's Music Box: Follow: https://www.facebook.com/KMBEngland On Friday go to: https://www.mixcloud.com/live/KeithsMusicBox/ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 configuration files, you change it, restart whatever
>> it is if it is not dynamic, and it works! (or not :-)
>
>Same here.
>
>> Maybe this is just confirmation that I am old now, ha ha.
>
>Then we both are :-)
{raises hand} :)
>> What distro are you using these days?
>
>I have been using Archlinux for around 10 years.
>Now evaluating Artix, which is Arch without systemd.
>
>Ciao,
Devuan here - except a still working eeepc900 on debian squeeze.
--
Will J Godfrey
https://willgodfrey.bandcamp.com/
http://yoshimi.github.io
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Is Piperware a successor to Jack/Pulseaudio?
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 not dynamic, and it works! (or not :-) Same here. > Maybe this is just confirmation that I am old now, ha ha. Then we both are :-) > What distro are you using these days? I have been using Archlinux for around 10 years. Now evaluating Artix, which is Arch without systemd. Ciao, -- FA ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
