User talk:Tonij

From ArchWiki
Jump to navigation Jump to search

reverts on JACK page

Hi! I've reverted your edits for the JACK page (https://wiki.archlinux.org/index.php?title=JACK_Audio_Connection_Kit&type=revision&diff=580313&oldid=580294), because information on how to edit the realtime-privileges configuration does not belong there. Additionally, these configurations are meant to be used, as it is explained in the article already (by adding one's user to the realtime group). Your addition didn't add any new or useful information to the page (the settings you are describing are the ones that are being installed by the package).

Secondly, the addition on how to start JACK using jackd 'with defaults' doesn't make sense, as 'starting with defaults' would mean to plainly call jackd (without any parameters).

Davezerave (talk) 15:43, 18 August 2019 (UTC)

When I installed realtime-priviledges, the configuration file had the first line as "rtprio 98" which will not work with realtime. It has to be changed to "rtprio 99" to enable realtime. As for starting with defaults. If you run jackd with no parameters it will not start jack. Jackd requires at least the backend to to start, hence why I had it as jackd -d alsa Tonij (talk) 16:25, 18 August 2019 (UTC)
Here is the file by the way, so that you can confirm: https://git.archlinux.org/svntogit/community.git/tree/trunk/99-realtime-privileges.conf?h=packages/realtime-privileges Tonij (talk) 16:27, 18 August 2019 (UTC)
I checked over it and actually I was wrong, it does not need to be set to 99. So you can discount my previous statement about that. But jackd definitly does have to be run with the backend as a parameter. Also, without giving people that command, there are no instructions on that page on how to start jack without jack2 dbus. Tonij (talk) 16:39, 18 August 2019 (UTC)
Yes, realtime-privileges only 'enables' your user to run any application with an RTPRIO up to 98. It is not advisable to run something at 99, as kernel related processes (e.g. watchdog) could be interfered with.
In regards to running jackd: Choosing a backend is required, but the alsa backend is not 'the default'. There are plenty of others: jackd(1).
Additionally (to add to the confusion), jackd respects ~/.jackdrc, which holds the last configuration and hence could be considered 'the default' for a system, once jackd was run ( :-/ ).
I guess it would be more helpful to point to the man page and give one or two examples (e.g. start with alsa backend, start with dummy backend, or something generic e.g. jackd -d <alsa,firewire,dummy>).
What do you think?
Davezerave (talk) 16:56, 18 August 2019 (UTC)
Yes, some examples like that would be very good. It would alleviate a lot of confusion with starting jack. Tonij (talk) 18:32, 18 August 2019 (UTC)
Alright. Please give me a couple of days for it. I'll add them there. Meanwhile, jack2 1.9.13 will bring some changes (and an additional way of using jackd...). I want to drop jack2-dbus then (or preferably earlier), because it is included in jack2 already. Davezerave (talk) 19:55, 18 August 2019 (UTC)