PeppyMeter and moOde

[Tim Curtis]

Couple things:

1. MPD native dsd and pcm peppy display can be done but it's a complex configuration. I'm not convinced it's a good idea to implement because of the complexity and niche usage scenario.
2. CamillaDSP is a PCM processor and its not limited by any particular sample rate
3. Peppy is a PCM processor that converts all input to 16/44.1K via the peppyalsa ladspa plugin
4. DoP format will produce no meaningful results in peppy because DoP is not an actual pcm waveform

[Nutul]

FWIW, DSP will alter ANY source. It is made on purpose, and that's WHY it's called DSP: DIgital Sound Processing => processed != original.

[Tim Curtis]

Question:

With a Pi4 or pi5 which have two HDMI ports is it possible to have the WebUI on one display and Peppy on the other?

[steve4star]

Question:

With a Pi4 or pi5 which have two HDMI ports is it possible to have the WebUI on one display and Peppy on the other?

I am away from my devices to test for a few days. 
However, from memory peppymeter redirects output to fb0. 
It might be possible to alter this to use fb1?
Might also require the max_framebuffers=2 being set in config.txt.

[Nutul]

This sounds already amazing...
If it was also possible to use independently the local display together with any HDMI output,,, well, "I'll eat my hat" (cit. Rockerduck)

[Tim Curtis]

After some research it looks like the default in the kernel mode video driver supports HDMI 1 and 2 to be mirrored or to be configured as a single extended display.

There is a Direct Rendering Manager (DRM) API that apparently can be used to configure each HDMI port as a separate, independent display but it requires writing software using libdrm.

Another way to achieve the configuration whereby moode is displaying Peppy on an attached display and a second display is showing the WebUI/CoverView is to use a second Pi. See below.

Pi-1 "moode"
Connected to the audio system and a small DSI or HDMI display specifically for showing Peppy.

Pi-2 "moode-2"
Connected to another DSI or HDMI display for showing "moode" WebUI/CoverView.
The URL for Local Display would be set to "http://moode/" instead of "http://localhost/"
Basically just using this Pi to run a browser

Something like below:
   

[Tim Curtis]

After some research it looks like the default in the kernel mode video driver supports HDMI 1 and 2 to be mirrored or to be configured as a single extended display.

There is a Direct Rendering Manager (DRM) API that apparently can be used to configure each HDMI port as a separate, independent display but it requires writing software using libdrm.

Another way to achieve the configuration whereby moode is displaying Peppy on an attached display and a second display is showing the WebUI/CoverView is to use a second Pi. See below.

Pi-1 "moode"
Connected to the audio system and a small DSI or HDMI display specifically for showing Peppy.

Pi-2 "moode-2"
Connected to another DSI or HDMI display for showing "moode" WebUI/CoverView.
The URL for Local Display would be set to "http://moode/" instead of "http://localhost/"
Basically just using this Pi to run a browser

Something like below:

Tests indicate this works perfectly :-)

[mgarman40]

Many thanks FdeAlexa for the github guide to install and configure PeppyMeter. I followed your instructions to the letter and managed to get it going quickly. My previous attempts failed because I was not using the pi account.

Cheers

[nattaphoomd]

Hi @Tim Curtis ,

add on function suggestion. 2x screen is great option! and needed. Maybe we have local display DSI on rpi... and run HDMI to Big screen.

BUT if only consider streaming device with 1x screen.

1. if Consider only 1x screen i have possibility to switching Toggle between Moode Chormium base WebUI cover and PEPPYMETER.py? instead of 2x screen.
Just 1x GPIO to trigger Bash python peppymeter.py... and vice versa to switchback to moode.

I've modify peppymeter.py with GPIO button Interrupt. it could be touch UI in Moode WebUI to toggle peppymeter.py and to return could be touch the screen to exit Peppy.

2. and the next development would be insert COVERArt into Peppymeter + Currentsong + additional start / next track controller button in the same screen layout with customization faceplate layout?

Will that be needed for everyone?
here is example I did on moode 8.3
https://youtu.be/PrHhCLp8I5E?si=Yep1vfiVquvjExin

How do you activate Peppymeter now? and how to go back to Moode WebUI.

Best REgards,
Nattaphoom

[Tim Curtis]

Peppy display is turned on/off via the command below

Code:

pi@moode9:~ $ sudo /var/www/daemon/peppy-display.sh --help
Usage: peppy-display.sh [OPTION]

OPTIONS
--meter [on|off|restart]       Control PeppyMeter display
--spectrum [on|off|restart]    Control PeppySpectrum display
--help                         Print help
pi@moode9:~ $

1. To programmatically switch between Local display and Peppy display you need to stop one and start the other

Code:

# Switch to Peppy display
sudo systemctl stop localdisplay
sudo .var/www/daemon/peppy-display.sh --meter on

# Switch to Local display
sudo .var/www/daemon/peppy-display.sh --meter off
sudo systemctl start localdisplay

2. I mentioned before that embedding cover art, metadata and buttons directly into Peppy display probably requires modifying the Peppy sources to read moode currentsong.txt and then write the desired items to the screen. The Peppy config parser would also need to be modified to read some new options from the files that define the positions of the metadata items and cover art image.

It's a substantial effort and definitely not something for my TODO list but maybe an interested dev will take on the challenge and volunteer to do the coding and provide long term maintenance and support.