Repository navigation
EZPlayer 0.6.12
A bugfix release with fixes from your error reports and better FPP MultiSync + settings API for integrations.
Bugfixes
- Not sending data to some controllers that were already running when EZPlayer started.
- Handle some sparse FSEQ files written by recent xLights that had >255 sparse ranges and were not properly recorded in the FSEQ header.
- Controller uploads of multi-connection polylines.
- A network hiccup could hang the cloud poller and a few other services.
- The renderer watchdog doesn't make a false report when machine wakes from sleep.
- Security updates for several dependencies.
Viewer control
- Separate Remote Falcon schedule and playlists: when the viewer page and Remote Falcon both run, Remote Falcon can have its own windows and song list, for example a shorter list than the viewer page or different hours. See the manual under Viewer Control - "Real Soon Now" (TM).
- Send song list now button in the Remote Falcon settings: resends your playlist to Remote Falcon on demand and shows the error if the sync fails. Use it after editing sequences on the Remote Falcon site.
FPP MultiSync
- Media sync packets are now sent alongside sequence packets, as FPP and xSchedule masters do, so audio-following remotes (such as PulseMesh) track the song position. The new Send audio sync too switch (on by default) controls this; turn it off to keep FPP remotes that hold the same audio file silent.
- Every sync packet now describes the frame being output at that instant, never a frame ahead of the lights.
pStatusis pushed immediately on every playback event (song start/end, play, skip, stop, pause, resume, queue changes) and carries apositionwith sequence and audio time.
For integrations
- Settings API:
GET /api/ezp/playback-settingsreturns the current settings object, andGET/POST /api/ezp/playback-settings/<path>(for examplesync/multisyncorvolumeControl/defaultVolume) reads or replaces one part without touching the rest. See the API reference.
Support
- Crash dumps are found on macOS and Linux as well as Windows, and an unclean-exit report now says whether a dump was written, which separates a crash from a power loss or kill.