Hello
You have to install the plugin “touch display” first and have it running (volumio playback screen is displayed).
Then, you can use peppyneter basic.
The size settings in the plugin determine the size of meters displayed, but don’t set the screen resolution!
1 Like
Unfortunately not working. I will try it another cable. Thanks for help!
Another 10 skins for 1920x720 resolution added to Basic. Have fun!
2 Likes
Good morning, does anyone have this package but for 800x480 resolution? If so, please share it. Thank you.
Which package?
Press “update list” and you will see all available packages
ok. 
I’m running 4.0.25 on a Pi5. While running the latest PeppyMeter Basic 1.0.9, I’m getting audio drop outs all over the place and basically unstable playback. I’ve gone back to 1.0.7 and things are stable again. Reviewing the logs, I saw a lot of errors with 1.0.9:
Sep 26 03:20:27 volumio-pi5-beta volumio[21157]: info: peppymeterbasic Daemon Started
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: failed to open /dev/dri/renderD128: Permission denied
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: glx: failed to create dri3 screen
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: failed to load driver: drm-rp1-dsi
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: failed to open /dev/dri/renderD128: Permission denied
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: glx: failed to create dri2 screen
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: failed to load driver: drm-rp1-dsi
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: failed to open /dev/dri/renderD128: Permission denied
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: glx: failed to create dri3 screen
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: failed to load driver: drm-rp1-dsi
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: failed to open /dev/dri/renderD128: Permission denied
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: glx: failed to create dri2 screen
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: failed to load driver: drm-rp1-dsi
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: Failed to create /home/volumio/.cache/mesa_shader_cache for shader cache (Permission denied)---disabling.
Sep 26 03:20:27 volumio-pi5-beta volumio[25743]: Failed to create /home/volumio/.cache/mesa_shader_cache_db for shader cache (Permission denied)---disabling.
Sep 26 03:20:27 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:28 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000010] -121
Sep 26 03:20:28 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:28 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:28 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:28 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000010] -121
Sep 26 03:20:28 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:28 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:29 volumio-pi5-beta volumio[21157]: info: FusionDsp - Clipping Monitor started
Sep 26 03:20:29 volumio-pi5-beta volumio[21157]: info: FusionDsp - Clipping Monitor started
Sep 26 03:20:29 volumio-pi5-beta volumio[21157]: info: FusionDsp - Clipping Monitor started
Sep 26 03:20:29 volumio-pi5-beta volumio[21157]: info: FusionDsp - Clipping Monitor started
Sep 26 03:20:29 volumio-pi5-beta volumio[21157]: info: FusionDsp - Clipping Monitor started
Sep 26 03:20:29 volumio-pi5-beta volumio[21157]: info: FusionDsp - Clipping Monitor started
Sep 26 03:20:29 volumio-pi5-beta volumio[21157]: info: FusionDsp - Clipping Monitor started
Sep 26 03:20:29 volumio-pi5-beta volumio[21157]: info: FusionDsp - Clipping Monitor started
Sep 26 03:20:33 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:33 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000010] -121
Sep 26 03:20:33 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:33 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:34 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:34 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000010] -121
Sep 26 03:20:34 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121
Sep 26 03:20:34 volumio-pi5-beta kernel: i-sabre-codec-i2c 1-0048: ASoC: error at snd_soc_component_update_bits on i-sabre-codec-i2c.1-0048 for register: [0x00000021] -121So I’ve done some more testing with my Pi5 on 4.029:
1.0.9 w/ FusionDSP > Audio dropouts
1.0.9 w/o FusionDSP > Works fine
1.0.7 w/ Fusion DSP > Works fine
EDIT: I think I’ve read somewhere, maybe this thread, that there are incompatibility with FusionDSP, so the context of findings is based on 1.0.7
1 Like
I am not a developer nor am I well-versed in the culture of development so this preface is clarify my intentions as observations out of pure curiosity than any perceived critique of the plugin and its development.
After installing the newest Volumio beta and having worked thru my unique deployment, I reviewed my logs for anything else I can optimize. One of the things my local ai [touchy topic, I know] helped me identify is that Peppymeter can benefit from a “monitor branch” thru CamillaDSP to improve latency and CPU load. On my Pi5 and PC Volumio, CPU load doesn’t appear to be an issue itself but playing certain high bitrate files and certain hardware setups might benefit from not having multiple calls to ALSA [pardon if I am getting my terminology wrong]…here’s a quote:
That “monitor branch” idea comes straight from how CamillaDSP’s YAML lets you build parallel signal paths.
Right now PeppyMeter “hears” Volumio through an ALSA loopback device, which adds one extra buffering stage.
Instead, you can feed PeppyMeter directly from inside CamillaDSP before the audio ever leaves for your DAC.
[Volumio/MPD PCM input]
│
▼
┌──────────────┐
│ CamillaDSP │
│ ├─ main path ─► DAC (FusionDSP effects)
│ └─ monitor ──► PeppyMeter (same audio)
└──────────────┘
There are some steps I can try but I understand the plugin is in active development and I’d rather contribute than appear to ask for something or tell someone what to do as I ain’t no dev myself. I have a better understanding now of how the stack interacts and perhaps it is just something I need to learn with using CamillaDSP directly.
Short answer: the PeppyMeter plugin’s default “listen via ALSA loopback” design is mostly about universality, safety, and not depending on FusionDSP. Your Camilla “monitor branch” idea is cleaner for your stack—but it’s harder to ship as a default that works for everyone.
Hi @balbuze,
Once again thank you for this great plugin.
I’ve now some more time to testing and trying to make some own skins and become across some questions that I couldn’t find answers.
1 - I have checked GitHub for the “How to Own Templates for PeppyMeter” but I’m not sure if your plugin is 100% compatible with all the “commands” for meters.txt that they show on GitHub. Are all compatible? If not where can I read for all that is supported in meters.txt
2 - I have a 1920x1080 screen but I usually use skins that are of smaller resolution and they appear centered on screen:
2.a) Can we insert some kind of x, y coordinates on meters.txt that make a smaller resolution template not to show centered?
2.b) I have tried, from bars template of 800x400 to adapt to a smaller one 800x218 so that the background image not cover so much screen, but I only get a black background with no bars. Does Peppymeter support only specific resolutions:
What I’ve tried was:
With the following meters.txt:
[bar]
meter.type = linear
channels = 2
ui.refresh.period = 0.033
bgr.filename = bar-bgr.png
indicator.filename = bar-indicator.png
left.x = 0
left.y = 0
right.x = 0
right.y = 100
position.regular = 11
position.overload = 3
step.width.regular = 34
step.width.overload = 47
meter.x = 0
meter.y = 0
screen.bgr =
note: I only get a black background of 800x218 and I know that left.x, etc are wrong since they where a kind of desperate trial and error result.
With Peppy Meter Basic, you can’t move the black background of pygame.
I believe the example from Gelo18 is for PeppMeter/Spectrum.
The background will be centered on the screen and the size is taken from the folder name.
You’re right @wheaten, I didn’t test it on Peppymeter BASIC, only on Peppymeter Peppyspectrum. But why Gelo18?
I can’find any skins suitable for Raspbery Pi Touch Display 2 (720x1280). Are there anybody kind person that maybe have some time to make some?
I have not used any graphic software since Adobe Fireworks which doesn’t work anymore
I would be very thankful!
Best Regards/ C
Use paint.net, it’s free.
1 Like
Try 1280x800
1 Like
Hi,
I’m using this plugin on Volumio v4.071 and all is working fine and stable.
Currently I connect HDMI0 of Rapsberry Pi5 to a Samsung 22" 1920x1080 Monitor.
Now I’ve ordered a 1280x400 touch display with HDMI interface and I was wandering if I can connect both monitors to the Rapsberry Pi5 while using:
Samsung 1920x1080 for Volumio interface;
New 1280x400 touch display for PeppyMeter Basic only
If so, how can I configure it? 
Hey!
First, you have to configure both displays… This is not in this plugin…
Once done, even if I never tested, what you can try:
Modify the file in the plugin folder called
startpeppybasic.sh.tmpl
And change
export DISPLAY=:0
To
export DISPLAY=:1
Save the file, then save in the plugin to regenerate the config.
Let me know how it goes.
1 Like
Thank you very much @balbuze 
I’m still waiting for the 1280x400 touch display to be delivered and, as soon I receive it, I will test and give feedback!