Show newer

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).

Β»Video: Wie wichtig Abstand halten ist, um andere nicht mit dem Coronavirus zu infizieren, zeigt ein faszinierendes Video.Β«

Most of us are undergoing a lot of stress right now. People under stress can be short-tempered and impatient and can lash out. Try to be patient, empathetic, sympathetic, and avoid causing more stress or irritate or antagonize.

Try to be extra clear in your own communication, and ask others to clarify if they're not unambiguous. Be explicit about your feelings and expectations.

If you make a mistake, apologize.

BAD G++!

Apparently, g++-9.2.1 does *not* const-initialize a `static Class x;` with a constexpr ctor, *if* it also happens to have an uninitialized uint64_t array member. It does not generate a warning either, but surely triggers the "C++ Static Initialization Order Fiasco" at some inconvenient future point.

If you use certificates, check your hostname here to see if the cert is going to be revoked tomorrow, and you need immediate renewal:

More details:

I just signed a petition to the European Commission:

Demand the Right to Repair your smartphone.

Sign here:

I've written down the details of compatibly selecting modern instruction set extensions for the builds in a blog article.
The crux is avoiding extensions that are Intel only or AMD only.

Web packaging technology is torture.

The last week, I've been fighting webpack, parcel, , babel and bili, just because vue stopped supporting and I had to figure what to use as a replacement in .
^^^ If that sentence sounds like it has too many web tech buzzwords, that's *exactly* the problem.

And it's only a fraction of packages I had to deal with...
Most packages have documentation, but only provide tiny puzzles of a much bigger picture that is revealed nowhere...

Yay! Power loss due to some digging work outside.

Hope the BTRFS disks in the main server survived the sudden outage.

The client for is shell only and really rocks!

But it got way too late again, will have to continue setting up the new Testbit site tomorrow, good n8!

Today, I've implemented per connection cleanup of remote std::shared_ptr references in 's layer.

What we *really* need is per Javascript object cleanup of remote references though, but that requires FinalizationGroup support in Javascript:

That's still unfinished though, why do I always need bleeding edge features?

Time for bed I guess, maybe the edge looks less bleeding tomorrow... ;-)

Last Tuesday 0.15.0 was released.

This is most probably the last release that supports the + Beast UI. We have most of the bits and pieces together to move towards the new EBeast UI and a new synthesis core in the upcoming months and will get rid of a lot of legacy code along the way...

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:

If you use/develop or care about / FLOSS, take some time to answer this survey. Feel free to mention , seems they only know about FB, Birdsite and Slack.

I keep seeing this really odd interaction, where the second I start google-chrome or a newer version (>= 4), my currently running processes start overloading the CPU.

Firefox becomes unresponsive for several seconds, burning CPU. Yesterday I decided to watch FF in gdb and saw that it's accessing thousands of font files , each causing a "SIGSYS, Bad system call".

Can anyone guess why FF gets SIGSYS, failing to access a world-readable file? Bug report:

Show older

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