al_attach_mixer_to_mixer(3alleg5)

💖 al_attach_mixer_to_mixer — Allegro 5 API 🎀

okay bestie, pull up a chair, we're doing audio routing today and it's genuinely not that deep, i promise. this one lives in the Allegro 5 API, it's called al_attach_mixer_to_mixer, and its whole personality is "put this mixer inside that mixer". that's it. that's the page. 💅

---

✨ SYNOPSIS ✨

#include <allegro5/allegro_audio.h>

bool al_attach_mixer_to_mixer(ALLEGRO_MIXER *stream, ALLEGRO_MIXER *mixer)

---

🌸 DESCRIPTION 🌸

okay so here's the vibe: you take the mixer you passed as the first argument and you attach it onto the mixer you passed as the second argument. mixer goes into mixer. nesting hours. 🪆

two rules though, and they are not optional:

• The first mixer — the one that's getting attached — must not already be attached to anything. it's giving "single and ready to mingle", and if it's already taken, this whole thing does not work.
• Both mixers have to use the same frequency, the same audio depth, and the same channel configuration. matching outfits or it's a no from me. 🎀

returns true on success, false on error. classic bool behaviour, no notes. ✅

💀 also, and i cannot stress this enough: it is invalid to attach a mixer to itself. do not do that. that's not main character energy, that's a paradox. attach a mixer to another mixer. be normal about it. 🙈

---

🔥 SEE ALSO 🔥

• al_detach_mixer(3alleg5) — for when you need to undo the attachment, because sometimes we outgrow the group chat 💔

---

and that's the whole page, bestie!! go forth and route your audio, you absolute icon 👑 — this was pulled straight from the Allegro reference manual, page al_attach_mixer_to_mixer(3alleg5), and yes the manual really does say al_attach_mixer_to_mixer(3alleg5) twice, it's committed to the bit 🫶✨