Thank you. It worked!
Hi,
Hopefully you have a little time to advice me on this issue.
I am using the latest Volumio image and the PeppyMeter plug in that comes with it.
I tried many many things to get the PeppyMeters working with my Pi3 Band also Pi4 (now).
Without playing music (Spotify) I see the VU meter in the correct resolution (1920x1080) and all looks promising.
However when I try to play my phone gets disconnected from Volumio installed on Pi4B.
I have tried many things e.g. Software Mixer, DSD direct / DSD via PCM , but nothing makes a difference.
My Pi is plugged into an Audiophonics Board which i selected as an output device.
Once I switch PepperMeter off all is working.
Sometimes I can play a song but the meter needles wont move.
This is the link if you like to see the entire log:
https://logs.volumio.org/volumio/A8uR2QS.html 4
I did a bit more research on this error:
Mar 30 12:29:49 volumio volumio[857]: info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0
and my understanding is that the error might be caused by some conflict with my Audiophonics DAC ?
I tried with a different DAC setting (HifiBerry seems compatible) but that didnt solve anything either.
Regards,
Bjoern
Are you sure it’s Peppymeter? Or Peppymeter Basic?
Hey Grzegorz, how’ve you been?
Spotify still doesn’t behave well with PeppyMeter. As RedEyeNinja said, you have to install the FusionDSP plugin and enable it in PeppyMeter in order to have the needles move. It works that way; however, it cuases another problem. Now it prevents me to play my 96 kHz 24 (or 32) bit wave music that I ripped from my vinyl.
Still scratching my head. 
Andy
Hey Andy, this is a question for @2aCD, I don’t use Spotify. I have Tidal and it works fine.
I know. Haven’t visiting this forum for a while. I hope everybody is doing okay.
This is what Gemini’s answer. It’s scary good…
"Ah, hello! It sounds like you’re navigating the classic audio enthusiast’s labyrinth of plugin conflicts and bit-depth woes. It’s a familiar struggle! Let’s break down this PeppyMeter, FusionDSP, and high-resolution playback conundrum.
Here’s a structured approach to troubleshoot and potentially resolve your issues:
1. Understanding the Conflict:
- PeppyMeter’s Dependency:
- PeppyMeter, in its standard form, often relies on audio output streams that might be altered or bypassed when other DSP plugins are active.
- The need for FusionDSP to make it work with Spotify suggests that Spotify’s audio stream is being processed in a way that PeppyMeter can’t directly intercept.
- FusionDSP’s Impact:
- FusionDSP, by design, intercepts and processes the audio stream. This is why it allows PeppyMeter to function with Spotify.
- However, this interception can introduce limitations or compatibility issues with high-resolution audio formats like your 96 kHz/24 (or 32) bit WAV files.
- FusionDSP is likely downsampling or otherwise altering the audio stream.
- Bit-Depth and Sample Rate:
- High-resolution audio relies on preserving the original bit depth and sample rate. DSP plugins can sometimes introduce resampling or bit-depth reduction, which degrades audio quality.
2. Troubleshooting Steps:
- FusionDSP Configuration:
- Bypass for High-Res: Check FusionDSP’s settings for options to bypass processing for specific file types or sample rates. Look for settings that allow you to exclude high-resolution WAV files from its processing chain.
- Output Settings: Ensure that FusionDSP’s output settings are configured to maintain the original sample rate and bit depth. If it’s set to a fixed lower rate, that’s your problem.
- PeppyMeter Configuration:
- Input Selection: If PeppyMeter has input selection options, explore different input sources to see if any bypass FusionDSP.
- Version Check: Make sure you’re using the latest versions of both PeppyMeter and FusionDSP. Older versions might have known compatibility issues.
- Audio Output Chain:
- Direct Playback: Temporarily bypass FusionDSP and PeppyMeter to confirm that your 96 kHz/24 (or 32) bit WAV files play correctly on their own. This will help isolate the problem.
- Output Device Settings: Verify your system’s audio output device settings to ensure they support the desired sample rate and bit depth.
- Plugin Order:
- If possible, try changing the order in which the plugins are loaded. Sometimes, the order of processing can affect compatibility.
- Alternative Visualizers:
- If PeppyMeter and FusionDSP continue to conflict, explore alternative visualizer plugins that might be more compatible with your setup.
- Log Files:
- Check log files for both PeppyMeter and FusionDSP. They might contain error messages or warnings that provide clues about the source of the problem.
- System Resources:
- High-resolution audio playback and DSP processing can be resource-intensive. Ensure your system has sufficient CPU and memory to handle the load.
3. Potential Solutions:
- Conditional Bypassing: The ideal solution would be a configuration setting in FusionDSP (or PeppyMeter) that allows for conditional bypassing based on file type or sample rate.
- Dedicated Output: If your audio hardware supports it, consider using a separate output device for high-resolution audio playback, bypassing the plugins.
- Plugin Updates: Keep an eye out for updates to both PeppyMeter and FusionDSP. Developers often release updates to address compatibility issues.
In essence:
The core of the issue is that FusionDSP is altering the audio stream. You need to find a way to have FusionDSP process the spotify stream for PeppyMeter, but to have it leave the high resolution files alone.
I hope this helps!"
Is there a way to tell fusion dsp what files to intercept or not? That’d be great if we can.
I tried the following which improves the situation:
Instead of installing the latest version of Spotify I used one version older.
Then the VU meters move and I can connect.
However sometimes after I switch on the Streamer I got issues again. Could that have to do with the booting sequenze or with the fact that the Raspberry Pi will lose power during switch off instead of a proper software shutdown?
I believe there is a way in Linux to repair the OS during boot-up, can somebody help me out with some advice please ?
Highly appreciated
Bjoern
Maybe there is a way to display stereo (vu) levels on LCD1602, like in the picture? Most likely off topic, but I could not find a more suitable section. Thanx.
@VictorDUA
You’ll have to ask in the mpdoled thread. Maybe the guys can advise something.
Thank you. In next release maybe will be. Trying to test in alpha. Topic “VU meter for 1602”.
Hi!
Does anybody here know if Peppymeter screensaver work on volumio alpha/bookworm?
regards C
Not working (for now)
Peppymeter Basic works.
Ok!
Thanks!
Regards /C
I remember the PeppyMeter worked on Tidal Connect long time ago. Now I have Qobuz connect, PeppyMeter shows on the screen but the needles don’t move. Is this normal?
hi @Gelo5 i’ve installed peppyscreensaver from your guide. all ok but why don’t run?
what i can control?
What’s not working? What version of Voumio? What version of Peppymeter?
volumio version 2.917
downloadable version from your installation guide
after installing and setting as described, no meter available in any resolution starts.
Please upgrade to a supported version. V3.812.
V2.xxx is EOL for a long time.
I’ve been trying the new version for a week but I’m having trouble installing the display and then with peppymeter-basic.
that is, I managed to put everything in but my display is small (3.5" hdmi) and I can’t change the size of the text or graphics like I did with the contemporary plugin used on version 2.9. I looked for help in different sections but I received no solution.
see:
1: [PLUGIN] Touch Display - #1501 by nadirfly
2: Contemporary optimizations plugin for local connected displays - #478 by nadirfly
3: Peppy Meter Basic - The plugin! - #111 by nadirfly