So the client cannot be a Linux or Mac device? Is the client written in Python?
Hey @KCAudio,
Both answers have been sitting patiently in the release posts, waiting to be read. Since they are clearly bored of waiting, allow me to escort them out personally.
Question one. The Linux client was in fact the first one out of the gate. Windows came later. macOS is not supported.
Question two. Yes, peppy_remote is written in Python. It started life as a single monolithic script and was refactored into a proper modular layout in 3.3.2, which is also mentioned in the release notes.
If future questions could be preceded by a quick glance at the release posts, the sleep clinic would appreciate the reduced intake.
Kind Regards,
1 Like
Thanks. Will remember to scan thru the docs next time 
And now that the holidays are over, it’s time to dream again. It would be nice to have an option: Remember settings. New installation - settings are downloaded from a file (just like in Now Playing) 
1 Like
3.4.0 - Continuity Engine - save and restore your plugin settings
Dear Volumionauts,
The experimental branch has just grown a feature that has been quietly at the top of the wishlist for a while: the Continuity Engine. Open the plugin settings, scroll to the new Backup and Restore section, and you will find it sitting right above Debug and Profiling.
What it does is exactly what it sounds like. You give a backup a name, click Create backup, and the plugin saves a snapshot of your current settings into Internal Storage. Later on, pick that backup from the dropdown and click Restore selected backup, and you are back to where
you were. Delete selected backup does the obvious thing.
Three things get saved into each backup: config.json (the UI settings), the PeppyMeter config.txt, and the PeppySpectrum config.txt. Everything else - templates, skins, fonts - is already controlled by the existing Do Not Delete Themes switch, so the Continuity Engine does not duplicate work that setting already does.
The backups live under /data/INTERNAL/peppy_screensaver/backups/, which survives plugin uninstall and reinstall. That is the whole point. Reinstall the plugin, reinstall Volumio itself if you want, your backups will still be sitting there waiting for you.
A few ground rules for the paranoid and the curious:
- Names are letters, digits, spaces, dots, hyphens and underscores only, up to 64 characters. No slashes, no dot-dot nonsense.
- If you try to create a backup with a name that already exists, the plugin will refuse and ask you to delete the existing one first. Nothing is ever silently overwritten.
- If Internal Storage is nearly full, create is rejected with a toast before anything is written.
- Restore parses every file in the backup BEFORE it touches your live config. A corrupt backup is rejected and your current setup is left completely untouched. You cannot break a working setup by trying to restore a damaged backup.
- There is no hard cap on how many backups you can keep, but you will get a gentle warning once you pass 20. @Gelo5, this is for you.
@Gelo5, this was your dream and now it exists. No more re-entering everything from scratch after an update. Make a backup called experiment, go wild, restore if it was a mistake. Rinse, repeat.
Please consider this the formal end of the “I forgot what my settings were” support thread.
@Wheaten, if you can give this a spin on your test rig and try a create/restore/delete cycle plus a reinstall-then-restore cycle, I would be grateful. Twenty minutes should do it, or are we there yet.
Everyone else: the experimental branch installer has the usual instructions in the README. Mandatory debug logs with the relevant trace switches on if you hit anything unexpected. Vague reports without logs will be politely declined as usual.
Version is 3.4.0 for both peppy_screensaver and peppy_remote (the client is version-locked to the plugin, though this particular feature lives entirely in the plugin).
Full wiki page with all the gory details, troubleshooting, and suggested workflows is here:
Kind Regards,
4 Likes
1920x1080
Edit: @nerd - I think I’ve found a small bug: you can’t enter any time (elapsed, remaining, total) into the middle of a progress (arc type). It flickers…
3 Likes
Fantastic designs, Gelo5!! They’re really awesome, thank you!!
1 Like
Hey @Gelo5,
Dreaming again, are we not? Timers inside of an arc progress bar? Right - you wish has been granted. In experimental branch.
You all know the drill by now - test, report it.
Kind Regards,
Thank you, Master!
To be continued…