Private
Public Access
30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
← [Back to Twitter thread index](../README.md)
|
|
|
|
---
|
|
title: "Deterrent to ALSA is just parsing through snd_pcm_open() source. It's death by b"
|
|
author: "NOTimothyLottes"
|
|
handle: "@NOTimothyLottes"
|
|
post_url: "https://x.com/NOTimothyLottes/status/2070734717825986566"
|
|
post_id: "2070734717825986566"
|
|
timestamp: "2026-06-27 05:03:23"
|
|
post_count: 2
|
|
reply_count: 1
|
|
repost_count: 0
|
|
like_count: 11
|
|
view_count: 1624
|
|
---
|
|
|
|
# @NOTimothyLottes — Deterrent to ALSA is just parsing through snd_pcm_open() source. It's death by b
|
|
|
|
## Post 1 (2026-06-27 05:03:23)
|
|
|
|
Deterrent to ALSA is just parsing through snd_pcm_open() source. It's death by boiler plate and complexity. Tinyalsa isn't much better. Likely easier to think about this from perspective of devices that can be open()ed from /dev/snd. On my machine doesn't seem to hot plug
|
|
|
|
|
|
|
|
## Post 2 (2026-06-27 05:07:23) — reply to Post 1
|
|
|
|
Assuming 'p'&'c' are PLAYBACK & CAPTURE, so opening different devices (instead of both in one device). Then just have user provide a device, or have the API war-dial open() constructing possible devices to probe what is available 'pcmC{c}D{d}{p|c}'. Easier than listing files.
|
|
|
|
|