3/3 While the ability to run at nice priority -20 still requires root permission for the initial setup (or SYS_CAP_NICE), even that could *potentially* change with the introduction of a latency nice setting, if the kernel developers manage to implement unelevated latency re-nicing without opening up the gates for DOS attacks.

These developments are described in the LWN article 'The many faces of "latency nice"':

lwn.net/SubscriberLink/820659/

2/3 Not only is the risk of system lockups unwarranted to avoid audio drop outs, there is also no need for it to be taken.

Just prioritizing the audio rendering threads to run at nice level -20 is sufficient to prevent drop outs in low-latency setups, i.e. setups with <10ms round trip time. BTW, such setups require audio fragment sizes <= 128 samples (or "periods with <= 128 frames" in ALSA language).

1/3 On the topic of Linux low-latency audio setupsโ€ฆ

Installing jackd (1 or 2) still requests "realtime priority" to minimize latency.

This project should really get its act together and stop demanding this kind of elevation from benign audiophile users.

Don't enable this! Running a process with realtime scheduling priority allows it lock up the system for good (and no code is bug free).

Beast version 0.15.0 is released.

is an LGPLv2+ music synthesizer and composer (), for .
This release supports Jack as PCM driver and the experimental Ebeast frontened got many style updates, play position pointers and supports the Space key.

Full news:
beast.testbit.org/#news

Beast version 0.14.0 is released.

is an LGPLv2+ music synthesizer and composer (), for , including a , real-time and support for Plugins.

The full release announcement is out now:

beast.testbit.org/#news
mail.gnome.org/archives/beast/

Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!