Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • engine engine
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • AURAAURA
  • engineengine
  • Issues
  • #3
Closed (moved) (moved)
Open
Issue created Feb 06, 2020 by David Trattnig@davidOwner

Playout & Fallback Logic

In case some schedule cannot be played for some reason, there are 3 types of fallback/emergency scenarios:

  1. Schedule Fallback: Another programmed playlist for some empty timeslot is played (#44 (closed))
  2. Show Fallback: Another programmed playlist for this show is aired (#44 (closed))
  3. Station Fallback: A playlist or folder with random music for this show is aired (#43 (closed))

Each playlist can consist of audio file entry. They can be played in linear order or randomly (compare Random Music feature). In case of a playlist consisting of live or stream contents, it is expected that there is a recording of such show available. In such scenario the recorded version is played back only. (Update: It turned out, that playlists can always change there contents by design, see comment #3 (comment 1637))

In case a fallback is triggered, following should happen:

  1. Notify PM/PK about the incident via email (#38 (closed))
  2. Include info on the fallback type and if the timeslot was empty (no schedule programmed) (#38 (closed))
  3. (Optionally) Notify even before the actual broadcast has happened (this is scheduled for a later AURA release as it's optional)
Edited Nov 04, 2020 by David Trattnig
Assignee
Assign to
Time tracking