Build EZPlayer Playlists
Give each playlist a clear job. A dependable EZPlayer setup might use one opening list, one main show set and one closing list. Build those from songs you have already checked, rehearse their transitions, and then assign them to a schedule.
A playlist defines content and order. The calendar entry supplies dates, times and runtime behavior. Keeping those decisions clear makes a seasonal edit easier: you can change a set of songs without guessing which calendar window controls them. The official Playlists manual describes how these lists connect the library to the schedule.
Name the job before adding songs
Mattos recommends readable names such as “Opening message,” “Weeknight main” and “Closing message.” These are planning examples, not required EZPlayer names. Add a date or “rehearsal” suffix when you need a temporary version, and remove ambiguity before the public show.
Scroll sideways to see all columns.
| Playlist purpose | What to decide | What to rehearse |
|---|---|---|
| Opening | What the audience needs to hear or see first. | The transition from idle to the first main song. |
| Main show | Song order, variety and the intended audience experience. | Every transition and the return to the first item if looping. |
| Closing | The final message and intended end state. | The last song, closing item and lights afterward. |
| Rehearsal | A short set that exposes mapping and audio problems. | A repeatable comparison after a change. |
Intro and outro are roles you assign on a schedule entry. They are not a reason to create separate copies of every library song. One verified song can be used where it is needed; record its purpose in the planning workbook.
Build the first set
- Open Playlists and choose Create Playlist. Give the set a name that will still make sense during a late-night support call.
- Find the ready songs in the library panel on the left. Search or filter by tags when the library is large.
- Add the chosen songs to the right-hand playlist panel, then drag them into the intended order. Review the complete list before using Add All.
- Save the playlist with at least one song. Compare its song count and displayed duration with your planning record.
If the expected song is missing from the editor, return to Songs and media import. A missing or unfinished FSEQ is a library-readiness issue. Rebuilding a playlist does not complete a cloud render or supply a missing file.
Decide where random order belongs
The editor’s Shuffle action changes the order saved in that playlist. A schedule’s Shuffle choice affects playback at runtime. Those are different decisions. If a specific opening-to-closing story matters, write down the expected order and confirm it after editing.
For a first rehearsal, use a fixed order. That makes an unexpected song easy to recognize. Add runtime variation only after the basic sequence works. When you reach show scheduling, remember that schedule Loop and Shuffle are mutually exclusive in the current documented behavior. See the official Schedule Options.
Rehearse transitions, not just individual songs
The playlist row’s Play action starts one pass immediately. Use it during a deliberate rehearsal window. Listen for an abrupt level change, a long silent gap or an ending that feels cut short. Watch for the visual transition into the next sequence and record the exact pair of songs when something needs attention.
For a small first test, choose three already-verified items with distinct beginnings and endings. Write their expected order on paper, play the list once, and mark each transition only after observing it. This is a simple repeatable test you can use again after replacing audio, modifying a sequence or changing an output device.
On-demand playback can change what is heard next: a Jukebox song’s Play action interrupts immediately, while Queue waits for a sequence boundary. Avoid accidental requests during the controlled pass. The official Jukebox guide explains these controls; the show-night guide covers monitoring and stopping.
Make edits easy to understand
Clone a working playlist when you want to compare a revised set without losing your original order. Give the copy a clear name, review it and explicitly select the intended version on the calendar. A clone becomes useful only when you can tell which version the schedule actually uses.
Deletion has wider effects than clearing a draft list. Deleting a playlist leaves its songs in the library, but schedule entries that still reference it need repair. Deleting a song can also change playlists that used that song. After either change, check the affected calendar entries and regenerate the relevant preview.
Cloud-managed playlists can also be delivered or updated through EZRGB. Confirm which side owns your setup before making parallel changes in two places; follow cloud setup for that decision. Keep a working backup before broad seasonal changes.
Ready to schedule: the playlist name is unambiguous, its order and duration are understood, the transitions have been rehearsed, and you know which lists will serve as main, intro and outro. Continue with Schedule Your EZPlayer Show.
Documentation review: October 29, 2026, including the official EZPlayer v0.6.12 documentation. These are Mattos planning and operating guides. The workflows have not been run on an EZPlayer installation or physical display as part of this guide review; complete the suggested checks on your own system.
Back to the EZRGB & EZPlayer Learning Center
