[EPIC] Architecture: Metadata state to be held and posted by Engine Core instead of Engine

Currently meta data updates e.g. on current playing track is send from Engine Core to Engine. Engine in turn is notifying Engine API about the new playlog. Evaluate if there is a possibility to avoid the need of using Engine as a intermediary.

This involves:

  • Posting playlogs
  • Posting playout state such as "normal" and "fallback"

Not so straight-forward:

  • Planned playlist items required by engine clock: these will still be posted by Engine

Tasks

Edited by David Trattnig