IIRC they’re giving the ground they walk on a perpetual middle finger, with its fingernail being the hoof.

Ballerinas have nothing on 'em horsies.

But how are you supposed to know I’m talking dirty without any cultural context of the language of the free people of Hylaron?

In 25 Jahren wird den verhätschelten Bälgern im Untergrundbunker dann erzählt, wie Opa damals bei 45 ⁰C nachts mit dem Dieselpanzer zur Tankstelle fahren musste, ohne Klimaanlage, und der Verkaufsraum war auch nicht vernünftig klimatisiert, so dass das Dosenbier nur warm und Grillfleisch viel zu teuer war. Verdammte Grüne damals, da kann unser glorreicher Führer heute auch nix mehr retten!!1!

Und jetzt raus aus’m Kühlschrank, Oppa is’ warm!

“Nee lass ma’. Einen neuen Hamster krieg’ ich für’n Zehner, da ist auch einschläfern noch zu teuer.”

“The best way to get your question answered is to post wrong information.”

— Sun Tzu on a web forum ca. 1999, probably

Damit lötet er sich gut einen rein, fürchte ich.

Haben wir die noch? Keine mehr? Gar nichts mehr? Gar keine mehr? Gar kein Bandwürmer mehr? Zwei noch?

Ich sehe Wuggs, ich klicke. Neuronen aktiviert.

I would double down on sqlite for your case. If you are using python, the sqlite3 module is included, but looking at your pseudocode you are probably looking for Godot-SQLite instead. I have no idea what the #python line is supposed to be doing in the first line of your code snippet, besides confusing me.

SQL is old, and it shows. “Proper” relational database design is a black art, as is optimizing SQL queries, but speaking from my own early experience, you’ll be doing 95% with INSERT, SELECT, UPDATE, DELETE, anyway, with an occasional simple JOIN. This is absolutely manageable and somewhat worth learning, as you’re basically custom building your own data structure according to how you plan to use it most easily. This SQL with sqlite tutorial seems solid to me.

Beware LLM output. Wild guess is you’ll be sent off on a tangent to normalize your schema, unconditionally use synthetic, unique integer IDs everywhere, and other “best practices” that may not be necessary, and only complicate your structure beyond the point of understanding. Then it’ll be hell to use. Solid groundwork goes a long way, and you can always change things up when you realize “Damn, I’d love to have <some value> in that tuple for a really simple query!”

Give it a try. Creating your own data structures in the way you want can be really rewarding in itself.

If you’re gravitating towards a NoSQL database to avoid SQL, you’re basically using dicts again, and will have to learn a different query language, anyway. This may be a more approachable option for you IF your data structure isn’t very nested and uses few complex types, like arrays.

And yes, you absolutely will find dozens of things to slap into a DB once you got a taste of it, and there’s little reason not to. Save your settings in there, debug info, events… everything can be a table if you’re brave enough. :)

Looks like Asshole Design to me.

Forget /troutslap, embrace /turtleslap.

Ich würde sagen, dass deine herausragende Leistung für die gesamte Klasse maßgebend war.

So wird man auch auf das Echte Leben™ vorbereitet. Immer schön die richtigen Wieselworte kennen.

I’ll try to add “hw:” in front of the device handles.

Generally that’d be required if you’re using the hw:<card>[,device] device addressing, yes. You probably want to treat all device names, addresses, and handles as “opaque”, though, meaning you don’t care what the actual string looks like, and select your intended device through some other criteria.

That’s where default comes from, in a way. It leaves the device choice to the user. I understood that you intend to access some other audio device, typically non-default. In that case it’s ideal if you have any uniquely identifiable device information associated with the class of device you want to use, enumerate all “sound cards” to find those matching your criteria, and “hand down” the associated PCM handle to where you need it, without needing to know what it actually looks like.

Another way is to get a list of all “sound cards” of the system, and offer a legible selection of names/descriptions to the user in your application’s options to explicitly select the correct device, and have an internal mapping of that selection to it’s ASCII identifiers of PCM handles. Again, no need to know what the identifier looks like, you only need to match the user’s selection to it’s internal ID. This offloads the potentially difficult decision what device to use to your user, though, who may be even more lost being asked that question.

With "pcm" as the iface parameter in snd_device_name_hint() this should not happen. Did you check out and pilfer the code from aplay.c as I suggested before?

Post minimal, compilable sources to show your issue and the output you get, please.

The way is to use the appropriate ALSA library functions as mentioned in the associated docs, and see referenced examples for an outline how the flow is authoritatively supposed to look like, right from the tap.

Please elaborate “weird results for some reason” with minimal examples, as in “this is what I get running this code, and that is what I expected”. More often than not, the process of writing up your problems for external review leads to understanding, or at least to a couple good ideas what you might be doing wrong, or expecting to work differently.

The ALSA API is dense, and very C. It’s super-easy to make wrong assumptions about how things should work there. Great training for slogging through API docs, though. :)

Pronounce it /ˈwaɪzɝd/ for added effect! Don’t go overboard, though, or you may be called a custard.

I’d have a look at the aplay.c implementation for listing PCM device names (-L), pcm_list().

It’s basically using snd_device_name_hint(-1, “pcm”, &hints) and snd_device_name_get_hint() calls to discover the PCM device names.

Sehr geehrter Oberster Nudelgerichtshof,

mit Bedauern nehme ich die Ablehnung des Antrags zur Kenntnis, und werde mich fürderhin form- wie fristgerecht beim nächstem Stammtisch über den endgültigen Verfall deutschen Brauchtums, korrupte und inkompetente Behörden und Politiker, sowie die anhaltende Respektlosigkeit der Jugend gegenüber dem Alter beschweren. Vorbehaltlich stelle ich ebenfalls eine fundierte Kritik der Spielweise der deutschen Fußballnationalmannschaft in Aussicht.

Mit der Ihnen zustehenden Hochachtung,

Ein Wutbürger

Na gut, das kann sicherlich als mildernder Umstand gewertet werden. Hühnerauge sei wachsam!

Sehr geehrte @instantnudel@feddit.org,

ich bringe hiermit einen möglichen Verstoß gegen IIeL #1, #5, und #9 zur Anzeige und stelle Strafantrag. Öffentliches Interesse ist bekundet. Ich fordere unverzügliche und kompromisslose Anwendung der Regularien zur Aufrechterhaltung der öffentlichen Ordnung, bevor Schlimmeres geschieht!

Hochachtungsvoll,

ein besorgter Bürger

PS: Ironie ist irgendwann nicht mehr als solche eindeutig erkennbar. Darum hier: ;-)