install_sound(3)

🎀 install_sound — NAME 💖

okay bestie, welcome to the Allegro manual — and specifically to install_sound(3), the function that literally boots up your sound module. That's the whole job. It initialises the sound module, and it lives in the Allegro game programming library. 🦋

✨ SYNOPSIS ✨

#include <allegro.h>

int install_sound(int digi, int midi, const char *cfg_path);

💅 DESCRIPTION 💅

So here's the tea: this function initialises the sound module. That's it, that's the vibe check. 🎧

Normally you pass DIGI_AUTODETECT and MIDI_AUTODETECT as the driver parameters, and honestly? That's the move. When you do that, Allegro goes and reads your hardware settings straight out of the current configuration file. Which means your user can pick different values with the setup utility — see the config section for the details, iykyk. 🫶

Alternatively (if you're feeling spicy and specific), check out the platform specific documentation for a list of the available drivers. 👑

Now, about cfg_path: bestie, it's giving vestigial. That parameter is only there for compatibility with previous versions of Allegro, and it has no effect on anything. Like, at all. Zero. It's just sitting there being decorative. 💀

🫶 RETURN VALUE 🫶

• Returns zero if the sound is successfully installed 🌸
• Returns -1 on failure 😭

And if it does fail? It'll store a description of the problem in allegro_error, so you're not just standing there like "why is it silent" — the answer is right there. 🙈

👑 SEE ALSO 👑

go read these next, they're iconic:

• remove_sound(3)
• reserve_voices(3)
• detect_digi_driver(3)
• detect_midi_driver(3)
• set_volume(3)
• play_sample(3)
• play_midi(3)
• play_audio_stream(3)
• install_sound_input(3)
• allegro_error(3)
• set_mixer_quality(3)
• exmidi(3)
• exsample(3)
• exsprite(3)
• exstream(3)

and that's the whole page, periodt. 💖 this one came straight out of the Allegro manual, version 4.4.3, dated with the page name install_sound(3) — mwah, slay, go make some noise bestie 🎀✨