User-Automated Broadcast

12-Step User-Automation Broadcast Workflow The lifespan of media getting on the DOM broadcast system is unlike any other TV station in the world. DOM staff is never involved in ANY of these steps unless a problem arises, enabling us to focus on teaching, fundraising, production, building better systems for individuals with disabilities, etc.

1. From home, registered members reserve an ingest kiosk/editing station.
2. Members show up with their show in an acceptable format (mpeg2, DVD, etc).
3. Members ingest it to the server without staff help (ingest module).
4. Members provide the metadata, including the theme-block information that determines the broadcast slot (DOMinizer Module).
5. Once the show is “DOMinized”, ffmpeg encodes it for web (320X240 Flash) and for broadcast (720X480 Mpeg2).
6. DOM scripts move the broadcast version to the broadcast server archive for storage.
7. Drupal creates the webpage where viewers watch, rate, and give feedback on the video.
8. Once the video is fully uploaded and encoded the producer of the show can schedule the show to air on Channel 56, either in a recurring timeslot (if a Series request is made) or as a single playback event.
9. Additional airings occur when DOM's Scheduling Algorithm fills in gaps in the playback schedule by looking for shows based on rules like theme, freshness, and vote history, with repeat airings determined by viewer votes.
10. Newest shows are scheduled for Channel 56 first, based on the chosen theme block.
11. Then, depending on the number of votes received, competition within theme block, and freshness it will be scheduled on Channel 57.
12. Automated scripts move the show to the Princeton Broadcast server in time for broadcast (and clear it when done).
13. Viewers at home and on the web let us know if there’s a problem (and DOM staff step in, if needed).