AuMonitorNotifyEvent(3)
π NAME π
AuMonitorNotifyEvent β it's the monitor notify event structure, bestie. That's the whole thing. Short, sweet, iconic. π
β¨ STRUCTURES β¨
okay so first things first, you gotta have the header pulled in:
#include <audio/audiolib.h>
then there's this union called _AuEvent, and our girl aumonitornotify is just sitting in there as one of the members, living her best life:
typedef union _AuEvent
{
. . .
AuMonitorNotifyEvent aumonitornotify;
. . .
}AuEvent;
and here's the actual struct β the main character herself:
typedef struct _AuMonitorNotifyEvent
{
int type;
AuUint32 serial;
AuBool send_event;
AuServer *server;
AuTime time;
AuFlowID flow;
unsigned char element_num;
unsigned char format;
unsigned char num_tracks;
unsigned short count;
unsigned short num_fields;
AuUint32 data;
AuUint32 data1;
AuUint32 data2;
}AuMonitorNotifyEvent;
π¦ MEMBERS π¦
okay so let's go field by field, no skipping, we're doing the whole tour:
typeβ the event type, duh. MonitorNotify events are typeAuEventTypeMonitorNotify. that's the whole personality.serialβ the serial ID of the event, expanded from the 16 bit value the server sent you. glow-up from 16 bits, we love to see it. β¨send_eventβAuTrueif the event came from aSendEventprotocol request. so if it'sAuTrue, it's a SendEvent baby, no cap.serverβ the connection to the audio server that this event was read from. your link to the mothership. π«Άtimeβ the server time in milliseconds for when the event was generated. timestamped, periodt.flowβ specifies the ID of the flow that caused the event. yes, that flow. she did this. πelement_numβ the index of theExportMonitorelement that generated this event.formatβ the format of the monitor data. rn, the following formats are defined:AuFormatULAW8,AuFormatLinearUnsigned8,AuFormatLinearSigned8,AuFormatLinearSigned16MSB,AuFormatLinearUnsigned16MSB,AuFormatSignedLinear16LSB, andAuFormatLinearUnsigned16LSB. taken from theExportMonitorelement, so like, that's where she got it from. πnum_tracksβ the number of tracks in the monitor data. also taken from theExportMonitorelement. matching energy. πcountβ always0. like, literally always. don't ask, she's just built that way.num_fieldsβ always2. same deal, it is what it is. π€·dataβ monitor data. yes, that's the whole description. slay.data1β monitor data. again. iconic.data2β monitor data. three of them. we been knew. π
πΈ DESCRIPTION πΈ
so here's the tea: MonitorNotify events will be sent to clients with flows containing ExportMonitor elements. that's it, that's the whole deal β if you got an ExportMonitor element in your flow, the server is gonna come find you. iykyk. π
π₯ SEE ALSO π₯
go read these next, bestie, they're all in the same friend group:
AuAnyEventAuElementNotifyEventAuErrorEventAuGrabNotifyEventaudiolibβ Network Audio System C Language Interface
and that's the page!! this was audiolib - events, version 1.9.5, and yeah β it's giving manual page, it's giving networking audio, it's giving everything. go forth and monitor those events. mwah. πβ¨ππ¦
π¦ where this page comes from
- fedora 43: nas-devel 1.9.5-11.fc41 Β· MIT
- fedora 43: nas-devel 1.9.5-11.fc41 Β· MIT
- fedora 43: nas-devel 1.9.5-14.fc43 Β· MIT
- fedora 43: nas-devel 1.9.5-14.fc43 Β· MIT
- fedora 44: nas-devel 1.9.5-15.fc44 Β· MIT
- fedora 44: nas-devel 1.9.5-15.fc44 Β· MIT
- copyright 1994 Steven King
- Copyright 1993 Network Computing Devices, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms