The mm-renderer service can report events so you can monitor and react to changes in playback activity,
input and output attachments, and any errors that occur.
The API includes functions for arming the notification of an
mm-renderer event, waiting until an event occurs, and retrieving
information on the latest event. The information is stored in an
mmr_event_t structure and includes but is not limited to:
- the event type
- the new context state
- the current playback speed
- a warning string, when applicable
- detailed error information, when applicable
You can process events in an automated way to keep up with the state of
mm-renderer, by writing a loop that monitors events and processes
them by storing their data and performing follow-up actions.