ALLEGRO_AUDIO_EVENT_TYPE(3alleg5)
β¨ ALLEGRO_AUDIO_EVENT_TYPE β¨
okay bestie, so this is from the Allegro 5 API β the Allegro reference manual, and it's giving very "audio events" energy, and honestly? obsessed. π
πΈ SYNOPSIS πΈ
#include <allegro5/allegro_audio.h>
enum ALLEGRO_AUDIO_EVENT_TYPE
π DESCRIPTION π
so like. these are the events that get sent out by al_get_audio_stream_event_source(3alleg5) or al_get_audio_recorder_event_source(3alleg5). that's the whole vibe. they show up in your event queue and you handle them. no cap. π¦
π ALLEGRO_EVENT_AUDIO_STREAM_FRAGMENT
sent when a stream fragment is ready to be filled in. this is your moment, main character. go fill it. π«Ά
see al_get_audio_stream_fragment(3alleg5) for the actual doing-of-the-thing.
π ALLEGRO_EVENT_AUDIO_STREAM_FINISHED
sent when a stream is finished. that's it, that's the event. it's done. periodt. π
π ALLEGRO_EVENT_AUDIO_RECORDER_FRAGMENT
sent after a user-specified number of samples have been recorded. β¨
convert this one to ALLEGRO_AUDIO_RECORDER_EVENT(3alleg5) via al_get_audio_recorder_event(3alleg5) β that's how you get the good stuff out of it.
β οΈ okay listen, this part is important: you must always check the values for the buffer and samples, because they are not guaranteed to be exactly what was originally specified. fr fr. don't just assume, bestie, actually look. π
π SINCE π
5.1.1
π§ [Unstable API]: The API may need a slight redesign.
and that's the whole page, babes β it came from the Allegro reference manual and it's literally the ALLEGRO_AUDIO_EVENT_TYPE(3alleg5) page, so go slay those audio events. πβ¨π
π¦ where this page comes from
- debian trixie: allegro5-doc 2:5.2.10.1+dfsg-1 Β· Zlib
- ubuntu questing: allegro5-doc 2:5.2.10.1+dfsg-1build1
- ubuntu resolute: allegro5-doc 2:5.2.11.3+dfsg-1 Β· Zlib
- ubuntu stonking: allegro5-doc 2:5.2.11.3+dfsg-1 Β· Zlib
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms