ALLEGRO_AUDIO_EVENT_TYPE(3)
π NAME π
ALLEGRO_AUDIO_EVENT_TYPE β Allegro 5 API. And yes bestie, this is the ALLEGRO_AUDIO_EVENT_TYPE(3) page from the Library Functions Manual β iconic manual energy fr fr πΈ
β¨ SYNOPSIS β¨
#include <allegro5/allegro_audio.h>
enum ALLEGRO_AUDIO_EVENT_TYPE
π§ DESCRIPTION π§
These are the events sent by al_get_audio_stream_event_source(3) or al_get_audio_recorder_event_source(3) β literally the audio-event source situation, no cap π«Ά
π ALLEGRO_EVENT_AUDIO_STREAM_FRAGMENT π
Sent when a stream fragment is ready to be filled in. See al_get_audio_stream_fragment(3). That's the βbestie, your fragment is readyβ moment π
π¦ ALLEGRO_EVENT_AUDIO_STREAM_FINISHED π¦
Sent when a stream is finished. Periodt, the stream said bye π
π ALLEGRO_EVENT_AUDIO_RECORDER_FRAGMENT π
Sent after a user-specified number of samples have been recorded. Convert this to ALLEGRO_AUDIO_RECORDER_EVENT(3) via al_get_audio_recorder_event(3).
You must always check the values for thebufferandsamplesas they are not guaranteed to be exactly what was originally specified. Like, do not assume bestie β check them fr fr π
β SINCE β
5.1.1
[Unstable API]: The API may need a slight redesign.
okay thatβs the whole page, bestie β source: the Allegro reference manual, page: ALLEGRO_AUDIO_EVENT_TYPE(3), version vibe: 5.1.1; the footer didnβt give us a date, so weβre not inventing one ππβ¨
π¦ where this page comes from
- arch rolling: allegro 5.2.11.3-2 Β· Zlib AND BSD-3-Clause AND OFL-1.1 AND LicenseRef-Custom
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms