Back Up, Update and Recover EZPlayer

A useful recovery plan brings back the layout, songs, playlists, schedule and settings together. Keep a dated working copy before changing the software, moving the player or replacing a show folder, then verify the restored result with a small rehearsal.

Reviewed October 29, 2026. This guide uses the documented file structure and update controls available with public release 0.6.12. It describes a folder-based backup procedure; it does not assume an undocumented all-in-one export button.

1. Record what makes this installation work

Write down the EZPlayer version, operating system, active show-folder path, any separate Media Folder, layout-management mode and intended audio output. Include the controller address plan and a reference to the exact playlist and schedule that passed rehearsal.

Some settings live outside the show folder. The official settings overview distinguishes machine-level update preferences and device/browser UI preferences from show settings. Keep a record of startup behavior and audio-device choices so another computer can be checked deliberately.

2. Back up the complete working files

  1. Choose a time when the show can stop. Quit EZPlayer normally and make sure another instance is not using that folder.
  2. Copy the entire show folder to a dated backup location, including its .ezplayer subfolder. Use a copy, preserving the working original.
  3. Include separately stored audio or media that the show depends on. Record where it belongs when restored.
  4. Verify the copy contains the expected layout and network files, sequence/audio files and EZPlayer state. Check a few recognizable filenames and file sizes.
  5. Keep an additional copy away from the show computer. Label it with the version and last successful rehearsal date.

EZPlayer's files reference documents the song catalog, playlists, schedule and playback/cloud settings under .ezplayer. Copying only FSEQ files omits that organization. Directly editing state files while the player is running can be overwritten or conflict with its own writes.

A separate Media Folder remains a separate backup responsibility. Give the backup a simple written inventory rather than relying on the folder's total size to prove it is complete.

3. Treat the backup as private show data

Cloud registration is associated with the show folder, and its saved configuration includes player identity. Keep backups private. The official privacy guidance explains that possession of a Player ID or private control link can allow remote control.

Before migrating, decide which machine will become the active player. Shut down the old instance during the handover and avoid running two restored copies of the same registered show. Record the identity privately, rather than putting it on a public bench sheet or support screenshot.

4. Plan the software update

Official EZPlayer Software Update screen showing update mode and version controls
Official EZPlayer manual example showing an older 0.6.5 installation. Use the version shown on your own machine; 0.6.12 was the current public release when this guide was reviewed. Source and current instructions.

Open Settings → Software Update and read the installed version and update mode. The documented automatic mode can check after startup, download while the player is idle and queue installation for the next quit. Manual — only check when I ask is available when you want to control that timing.

Check for Updates checks the available release. After downloading, Install & Restart applies it immediately; Install on Quit defers the restart. A completed download may already be queued for installation on quit, so account for that before ending a session. Read the update behavior before scheduling maintenance.

Use a maintenance window with enough time to test and recover. Keep the previous working backup intact. The official download page and reviewed release listing identify the software source; a newer version is still a change that needs a rehearsal on your installation.

5. Run an acceptance check after the change

  • Confirm the app opens the intended folder and reports the expected version.
  • Check layout ownership and cloud state before syncing.
  • Play one known song, listen through the intended output and inspect the real props.
  • Verify a short scheduled start and its selected ending behavior.
  • Rehearse the actual computer/app startup process expected on show night.

Keep the test sequence and conditions consistent so you can compare results. For 0.6.12, retain the documented background-effect limitation: 0.6-era Overlay/Underlay controls do not select those distinct modes. Refer to the version note if a background effect behaves differently from your assumption.

6. Recover without overwriting your evidence

If the update or move fails, stop and keep the unsuccessful folder for comparison. Restore the known working backup into a separate location while EZPlayer is closed. Disconnect the recovery computer from the network before opening the copy, preventing immediate cloud sync or scheduled network output during inspection. Then use the desktop app's Settings → Show Folder to open it. Re-establish external media paths and inspect the songs and playlists before testing.

Reconnect deliberately after deciding which layout and settings should be authoritative: current cloud changes can replace an older restored layout. The Cloud screen identifies the layout owner and provides pause/resume controls; registration guidance explains how existing folders retain their association.

Use the software version and data combination that you recorded as working. If you need an older release, follow the documented manual-version selection and review its compatibility before opening newer data. Restoring a backup is a controlled test, not a guarantee that every software/data combination is interchangeable.

7. Close the recovery with an observed show

Repeat the acceptance check, then save a fresh dated record of what passed. Windows and Mac's Start EZPlayer when I sign in acts after sign-in, so a successful app restart alone does not prove recovery from a complete power interruption. Follow startup settings and test the real startup path.

If the restored show still fails, use EZPlayer troubleshooting to isolate the stage. Keep the saved files and error notes available for support; controller resets are a separate hardware action and are not part of a routine player-folder restore.

EZRGB & EZPlayer Learning Center · Planning tools and checklists

Official references and documentation

EZRGB & EZPlayer Guides · All Mattos learning resources