...
3 |
| The current media item has started playing. |
8 |
| The media item has completed playback. |
12 |
| A particular timecode has been reached. See the entry on Timecode Events for more details. |
13 |
| An roAudioPlayerMx instance has begun playback of an audio file. |
14 |
| An roAudioPlayerMx instance has completed playback of an audio file. |
15 |
| The EventTimeStamp of an roAudioPlayerMx instance has been been reached. |
16 |
| A media error has been detected. As opposed to code 30, this event usually indicates transient errors (e.g. low buffer levels). |
17 |
| A media error has been detected during roAudioPlayerMx playback. |
18 |
| The current media item has completed fading out. See the roVideoPlayer.SetFade() entry for more details. |
19 |
| |
20 |
| The FadeOutLocation of an roAudioPlayerMx instance has been reached. |
21 |
| |
26 |
| The stream seems to be underflowing. This event usually indicates that the streaming latency is set too low. It will be generated every few seconds as long as underflow is detected. |
30 |
| A fatal error has been encountered while attempting to start playback (e.g. the video format is not supported). |
| You are trying to play more video simultaneously than is allowed. If you are playing a single video by creating new video tags, reuse the existing video tag when possible to avoid race conditions when a video tag might hold onto a hardware video resource or take too long to disassociate a video player from the video tag. |
The Diagnostic Web Server log may return more specific information about media error states.
...