Good one, “SpikeWatchdog”

I’ll just cite:

“You better write “IBM are you dumb?” . IBM … when Idiots Become Managers is between my favorite ones (ex IBMer here).”

found in Jeff Geerling’s “Dear Red Hat: Are you dumb?”, which in turn I found via arsTechnica’s “Red Hat’s new source code policy and the intense pushback, explained”

And yes, as I stated before: the recommendation for us “normal people” is to stay away as far as you can from everything “Enterprise”. I learnt it more than 20 years ago, even then Red Hat was nothing about freedom, and everything about making money. Take Debian instead, which is a true free software project – and if you want to support it financially, look for “Software in the public interest“.

And yes, ex IBMer here as well πŸ˜‰

How to avoid double conversions

My computer normally runs with a 48000Hz sampling rate for audio, that’s the one you would also use for most video productions like when producing something for the ‘tubes and such.

But CDs had 44100Hz which is also perfectly fine, and which saves some space if you record with that frequency – and so some (or even most?) of my friends over at Wikiloops use that sampling rate for their music.

No problem; Ardour checks when importing, and would normally automatically convert the imported 44.1kHz files to 48kHz ones. But that would mean that I’d make it harder for others who would probably like to add my single tracks to the rest (with 44.1Khz). And also, each conversion diminishes the quality just a tiny bit, so it’s always best if/when you can avoid these and use the material as it comes. Even Ardour says so:

But how to temporarily set Ardour to 44.1kHz? Easy in case you’re using the new pipewire! I just wrote the following short shell script which I named ‘’:

pw-metadata -n settings 0 clock.force-rate 44100
PIPEWIRE_LATENCY=128/44100 pw-jack ardour
pw-metadata -n settings 0 clock.force-rate 0

So if I start Ardour using that, I can use 44100Hz just perfectly fine – and when Ardour ends, the system will be set back to 48000Hz; just what I wanted. Here are some screenshots from Ardour’s Edit and Mixer windows while it ran with 44100Hz:

And when I stop Ardour, the script ends with:

set property: id:0 key:clock.force-rate value:0 type:(null)

Just what I always wanted, as Tigger would say πŸ™‚ Thanks to the pipewire crew, and thanks also to my friends over at Wikiloops πŸ™‚

Oh, and what I’m also using with pipewire (which is now the standard audio “engine” on Debian and most other Linux distributions) is a program called qpwgraph, and that is a graphical patchbay like the older tools (qjackctl, Carla, Catia & Co). Looks like this:

Here you see three inputs for my upright bass on the left, which go into Ardour. The right side shows Ardour’s monitor section and its metronome going out into my sound interface, and from there, into my headphones. The outputs of individual tracks go back into Ardour’s master track, which gives you this figure 8 shape. Easy peasy, isn’t it? Virtual cabling, so to say…

Thanks to you for reading.

Started to play again

Today, for the first time since quite a while, I stood and sat down with both my upright and also my fretless basses, playing to some template/song from Wikiloops again. And it’s fun. And although I’m not after perfection anymore – the journey is the reward – I’ll have to put in some time again. Can’t wait…

Fretless bass at the computer desk, MΓΆrfelden-Walldorf 2023

Like always, thanks for reading, and for viewing.