ReadonlystreamingReadonlystreamingDispatched when a stream needs re-buffering, which results in an audio interruption for the customer.
The event is emitted only for stalls that interrupt playback, not stalls on pre-buffering or after a seek. The callback is invoked after the rebuffer has finished.
If playback is interrupted, the rebuffer start time is at the point of interruption. The rebuffer is considered over when any of these conditions occur:
https://console.harmony.a2z.com/music-metrics/docs/event/streamingRequiredReBuffering
ReadonlystreamingDispatched when a track stops playing for any reason, including pause, ended, seeking, looped, or deactivated.
streamingTerminated and trackStreamed share a couple source triggers: track unload and track looped. In these cases, streamingTerminated will always be dispatched first.
https://console.harmony.a2z.com/music-metrics/docs/event/streamingTerminated
ReadonlytrackDispatched when a track has finished or is repeated.
Pause/resume or system interrupts will not result in this event.
trackStreamed has a 1:1 relationship with streamingInitiated, that is, every streamingInitiated event should have a trackStreamed event.
https://console.harmony.a2z.com/music-metrics/docs/event/trackStreamed
Dispatched when a track starts playing for the first time and not after resume. Will be emitted at most once per track change.
If a track begins playing, is deactivated and reactivated, then plays again, a second firstPlaying callback will be invoked.
https://console.harmony.a2z.com/music-metrics/docs/event/streamingInitiated