4
Is there any way to get the PCM handles for ALSA devices? (lemmy.world)
submitted 6 months ago by to c/learn_programming@programming.dev
5 comments fedilink hide all child comments
 

All the tutorials I can find is just telling me to jUSt UsE tHe DefAUltS (or even to use SDL or some similar library instead of my own solution), but some more advanced features such as getting HD rumble working on controllers with such features would require to connect to select devices.

So far I've tried:

  • using library functions, but they give weird results for some reason.
  • reading the contents of /proc/asound/cards, which supposed to work and contains some very useful addresses, but not the PCM handles themselves.

Unfortunately, 99% of my search results is about how to configure ALSA to be used in Linux, which is obviously not what I need.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 6 months ago* (last edited 6 months ago) (3 children)

On function snd_pcm_open():

name ASCII identifier of the PCM handle

What does this mean exactly? What can I pass to it besides of "default"?

Originally I tried the function snd_device_name_hint, but it only worked for MIDI devices so far. For PCM, it lists all kinds of things.

Update: I'll try to add "hw:" in front of the device handles.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 6 months ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 6 months ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •