Hello
There’s nothing in older versions of the Spotify plugin different that justify using it…
And nothing related to boot sequence or power.
The issue is probably in the Alsa pipeline with no known solution…
Please, update the plugin to v0.0.3 and test Spotify.
Let me know 
Have you installed both Peppy_Meter and Peppy_meter_Basic as I see the same posts in 2 different topics?
Some time ago I tried to install PeppyMeter via the command line.
However all my April posts are based on the latest Volumio OS which comes with a PeppyMeter (perhaps basic, not sure) plug-in.
Spotify works best with that if I use the second last version but still not reliable.
I am at a point to consider to change away from Volumio. If anyone could recommend a good Streamer OS with VU meter display I would be grateful.
(PiCorePlayer has also issues I used that before)
Bjoern
I see… you do anything, occupy people to help you, blame Volumio and ask advice for another system! You are a joke!
Good luck
1 Like
Taken with Liam Neeson 
but what I do have are a very particular set of skills. Skills I have acquired over a very long career.
Could reflect on Peppy 
1 Like
Come On thats not fair, I have spent many weeks trying to make it work. Unfortunately I am not a software guy. I am not blaming Volumio or anything else for that matter, I just try to find a solution to get Spotify work with nice VU meters showing. I really love the design of PeppyMeter.
Well… In that case, simply install peppymeterbasic from the store.
Test and feedback
This thread is only about peppymeterbasic!
If i may chip in, please take a new SD card and start with a clean install.
As I am not sure if any of the tries left some orphaned stuff, causing issues.
When it’s not working we need your support to provide info as request. Keep in mind all we have to go with is a black box and the information you give us.
@BjoernStefan
Everyone here really wants to help you.
Just tried a clean install on a rPi4, with V3.799. I see in you previous log:
time=“2025-03-29T17:51:49+08:00” level=debug msg=“fetched chunk 2/10, size: 524288” uri=“spotify:track:1f4NJhdLUzvAo13K7XTsh6”
time=“2025-03-29T17:51:49+08:00” level=debug msg=“fetched chunk 5/10, size: 524288” uri=“spotify:track:1f4NJhdLUzvAo13K7XTsh6”
time=“2025-03-29T17:51:49+08:00” level=debug msg=“fetched chunk 4/10, size: 524288” uri=“spotify:track:1f4NJhdLUzvAo13K7XTsh6”
time=“2025-03-29T17:51:49+08:00” level=debug msg=“alsa driver configured, rate = 44100 bps, period time = 100000 us, period size = 4410 frames, buffer time = 500000 us, buffer size = 22050 frames, periods per buffer = 5 frames”
time=“2025-03-29T17:51:49+08:00” level=info msg=“loaded track "Indecisive - Is It A Crime" (paused: false, position: 44545ms, duration: 142968ms, prefetched: false)” uri=“spotify:track:1f4NJhdLUzvAo13K7XTsh6”
go-librespot: pcm_meter.c:1216: snd_pcm_scope_s16_get_channel_buffer: Assertion `s16->buf_areas’ failed.
These errors I can reproduce with a faulty configured sound card (yeah some Chinese wanna be DAC HAT).
If you create a clean install, can you select the jack output on the rPi4 and check if it is working.
When succesfull the next step is adding your DAC, as I expect there is the issue. (a driver/config issues with the Sabre plugin)
This reply is in no way chiming into someone else’s issues…I’m just reporting what I’m trying and experiencing at the moment.
I did a fresh install of 3.799 on an USB 3 key on a Pi4b. Other than that it won’t reboot and need hard reset, the other major issue I have appears to be with PeppyMeter Basic. The pi is connected to my DAC via USB. When I activate this plugin, of course, also while using FusionDSP, everything comes out as 44.1kHz…when before this update, PeppyMeter Basic did not impede in the actual playing of music. I found this out after doing a bunch of troubleshooting and reinstalling again.
Turning off the plugin and only this plugin, returns music playback to the way it used to be. I also tried the old 0.2 beta and it’s the same. So to be clear, I don’t really think it’s an issue with the plug-in, but is it then an issue with the 3.799 update?
Are you sure you reply in the correct topic, as this is your first post in this topic. And for sure confusing to whom you make this statement?
- rPi4 and boot issues from a USB thumb/key, see; [Guide] Prepare Raspberry Pi for boot from USB/NVMe - #46 by nerd .
- Your 2nd point I can confirm. Playing a track 96kHz/24bits shows as 44.1kHz on the DAC.
-{,"samplerate":"96 kHz","bitdepth":"24"}
With Peppy_Meter_Basic:
Without Peppy_Meter_Basic:
Volumio V3.799, V3.795, V.3.779 Plugin V0.0.3 same issue.
Volumio V3.799, V3.779, Plugin V0.0.1 is working.
@balbuze , can you take a look. Something is different between V0.0.1 and V0.0.3
1 Like
Apologies for confusion. I was reporting my issue and I read above someone else was advised to try a fresh install and since I’m also doing a fresh install, I didn’t want to appear to be chiming into other ppl’s issues. I’m specifically asking if something changed with the plugin or the fresh install that’s on 3.799 causing the issue.
Thanks for the link to the USB issue too!
@RedEyeNinja
Please use V0.0.1 for the time being, which seems to work fine for me…
1 Like
Last change made in the plugin v0.0.3 to fix non moving needs lead to the sample rate issue…
I’m trying to fix both issues.
As @Wheaten suggested, use v0.0.1 by waiting the fix.
1 Like
For info, @Gelo5 added plenty of very nice meters in different resolutions. Thanks you @Gelo5 , the master of meters!
To use them, just update the list in plugin!
Enjoy
1 Like
Added resolutions:
1920x1080, 1920x515, 1920x480, 1480x320, 1280x400, 1024x600, 2560x720, 1280x800
1 Like
Yeah he keeps on spitting new ones out 