[Plugin] PeppyMeter/Spectrum Screensaver for VOLUMIO Bookworm

[nerd]

Hey @naimnatnod,

Well done on figuring out the spinning cassette animation - positioning those reel holes is fiddly work.

To get your template into the GitHub repository, first you need to prepare your files correctly, then submit them. Here is the full process:

---

STEP 1 - PREPARE YOUR FILES

Your zip file must follow this structure:

[resolution]_[name].zip
  +-- [resolution]_[name]/
        +-- meters.txt
        +-- preview.png
        +-- *.png (all your image assets)

Example if your template is 1920x1080:

1920x1080_cassette_spinning.zip
  +-- 1920x1080_cassette_spinning/
        +-- meters.txt
        +-- preview.png
        +-- background.png
        +-- needle_left.png
        +-- (etc - all your assets)

Required files:

• meters.txt - your meter configuration
• preview.png or preview.jpg - screenshot showing the template in action
• All PNG/JPG image assets

Naming rules:

• Use underscores, not hyphens or spaces
• Lowercase preferred
• Resolution prefix required (e.g., 1920x1080_name)

---

STEP 2A - IF YOU HAVE A GITHUB ACCOUNT

1. Go to GitHub - foonerd/peppy_templates
2. Click “Fork” button (top right) to create your own copy
3. In your fork, navigate to: template_peppy/[width]/[height]/
   • For 1920x1080: template_peppy/1920/1080/
   • For 1280x720: template_peppy/1280/720/
   • Create folders if they do not exist
4. Click “Add file” then “Upload files”
5. Upload your zip file
6. Write commit message: “Add 1920x1080_cassette_spinning”
7. Click “Commit changes”
8. Go back to main peppy_templates repository
9. Click “Pull requests” then “New pull request”
10. Click “compare across forks”
11. Select your fork as the head repository
12. Click “Create pull request”
13. Add description with: template name, resolution, what hardware you tested on
14. Submit

The automation will generate README entries after merge.

---

STEP 2B - IF YOU DO NOT HAVE A GITHUB ACCOUNT

1. Upload your zip file using one of these methods:

   • Attach directly to forum post (if under size limit)
   • Google Drive (set sharing to “anyone with link”)
   • WeTransfer or similar file transfer service
   • Any other public file hosting

2. Post the link here with the following information:

   • Template name
   • Resolution
   • What hardware you tested on (Pi model, display)
   • Brief description

3. Someone with repository access will upload it for you

---

Let me know if any step is unclear.

Kind Regards,

[Gelo5]

Andy, you have a bad samplerate position.

[naimnatnod]

I know. I fixed it after I took the video.

[Old_Duffer]

Following an update to 3.1.2 from 3.1.1 (I think…) I seem to have the following problems;

With Touch screen timeout set higher than Peppy;

Peppy doesn’t start on its own, if left alone it will not start, even after a track change. Moving to the next track via the u.i. will kick it into action. Once that has been done once, Peppy continues to work through the list except for……

I seem to have lost the ‘fade’ between screens (default setting of 0.5s). Setting the fade time to 5 seconds will stop the movements but the screen is ‘stationary’ and ‘un-fading for the 5 seconds, then abruptly switches to the next one. The meters don’t appear for a second or two.

Once up and running, moving onto the next track via the u.i. will cause Peppy to drop out and revert to the Volumio screen. Peppy will then start up again - at the first screen.

Volumio 4.073
Pi5 8gb

Is this perhaps a setting (old human interface) problem.
If logs are needed, when should I grab them?
Many thanks for any help, I just hope it’s not too much of an Old Duffer’s inability to get things right!

[Old_Duffer]

I’ve just done a complete re-flash.
Volumio 4.073
Peppy now 3.1.3
I’m still having the same problems.
No fade;

• setting ‘Fade’ or ‘No Fade’ has the same effect - meters and timer stop - short delay (as set in Transition delay) - next screen appears - short delay (as set…) - meters and timer start. No fade.

Peppy drops out, back to u.i. screen;

• when selecting next from the u.i. peppy stops, reverts to the u.i. screen and starts again with the first screen in the list. This doesn’t happen if the track is left to end on its own, peppy stays ready for the next track.

Edit. Just updated to Volumio 4.088 in hope but no difference.

I’m sure that I’ve had this working well before. Anyone any suggestions?

[Fire]

After several days of research, I finally learned how to make my own skin, thank you all

[pjorgenunes]

Will you gonna share it via github?

[Fire]

I don’t have a github account. If you have an email address, I can send it to you.The current resolution is 1280X582, I don’t know if it is suitable for your screen.

[Gelo5]

Just wait a little longer. You won’t be disappointed. There will be brand new skins.

[pjorgenunes]

Hi,

I’ve searched but couldn’t find anything related to this.

When using Peppymeter with FusionDSP with the enable FusionDSP integration ON even if I’m resampling to 96KHz my DAC is always stucked on 48K. If i disable Peppymeter or the FusionDSP integration option, the DAC says the correct 96K.
Any idea? Is it supposed to go “down” to 48K?

Thanks

[Wheaten]

Did you set Modular Alsa In peppy, change it to DSD native.

[pjorgenunes]

With that option it works but… whenever I enable FusionDSP integration i cannot choose anymore and get back to 48K. If I disable that option it works again (96K).

I get this warning but all seems to work anyway… (Peppymeter & FusionDSP):

[d3nnisc]

Hi Wheaten,

I still cant get this to work any ideas?

Regards,

Dennis

[Wheaten]

[Wheaten]

Sorry, Can’t help on Spotify

[Wheaten]

You need to enable the DSP setting in the Peppy plugin:

But it seems FusionDSP and Peppy don’t go well together.

You can try this sequence:
When making changes to FusionDSP settings while using PeppyMeter, follow this sequence:

1. Go to PeppyMeter settings
2. Turn OFF “FusionDSP Integration”
3. Make your changes in FusionDSP (sample rate, filters, etc.)
4. Return to PeppyMeter settings
5. Turn ON “FusionDSP Integration”

[pjorgenunes]

Thanks for your suggestion

Still stucked on 48K max output even with no resampling playing files natively at 96K ou 192K.

Just have to admit that they really don’t like each other until someday they will

BR

Is there any specific order of installation of both plugins? Peppymeter or fusionDSP first?

[Wheaten]

Nope,
I can duplicate the issue, Don’t have a solution at this moment.

[nerd]

Dear Volumionauts,

PeppyMeter: Display Persistence Feature

New option in Playback Behavior settings - “Keep display active after pause/stop”

What it does: Configurable delay (15s/30s/1m/2m/5m) before PeppyMeter shuts down when playback pauses or stops. Eliminates screen flicker during track changes caused by Volumio’s stop-play sequence on next/prev.

Time display options:

• Freeze: Shows track time at moment of pause
• Countdown: Shows time until display turns off (orange)

Technical:

• JS timer delays /tmp/peppyrunning flag removal
• Python stays alive, meters idle naturally on silence
• Animations continue smoothly through volatile track transitions

Default: 30 seconds, enabled.

Kind Regards,

[nerd]

Dear Volumionauts,

PeppyMeter Indicators - Beta

New feature for PeppyMeter Screensaver: Playback State Indicators

Display volume, mute, shuffle, repeat, play/pause status, and track progress directly on your meter skins.

---

What’s New

• Volume - numeric, slider, arc gauge, or image-based fader
• Mute - 3-state indicator (mute on /off / volume =0)
• Shuffle - 3-state (off / shuffle / infinity)
• Repeat - 3-state (off / all / single)
• Play/Pause/Stop - 3-state
• Progress bar - track position

Display Modes

• LED mode - colored circles/rectangles with optional glow
• Icon mode - custom PNG icons with optional glow outline

---

Documentation

Full configuration reference in the wiki.

Kind Regards,