PeppyMeter

fdealexa · 2022-01-10 10:49 pm

rpi said:
Hi Francesco,

Do you mean that if you don't have Pygame installed on your OS then using commands:
sudo apt update --allow-releaseinfo-change
sudo apt-get install python3-pygame
will install Pygame of version 1.9.4? I'm not sure how it works. How does it know that you don't want to install Pygame 2 which is the latest?

Thank you!

Hi rpi,
before the command:
sudo apt update --allow-releaseinfo-change
I gave the normal command:
sudo apt-get install python3-pygame
and the system trys to load 1.9.4 with errors; so I gave the command:
sudo apt update --allow-releaseinfo-change
followed by:
sudo apt-get install python3-pygame
and I got the 1.9.4 installed.

The following is a part of the library installed:
ii python3-pygame 1.9.4.post1+dfsg-3 armhf SDL bindings for games development (Python 3)

Or, if you prefer:
pi@moOde-FdA-Mansarda:~/FdA_OLED $ python3
Python 3.7.3 (default, Jul 25 2020, 13:03:44)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

>> import pygame

pygame 1.9.4.post1
Hello from the pygame community. https://www.pygame.org/contribute.html

>>

Best regards and thanks,
Francesco

rpi · 2022-01-11 6:09 pm

Hi Francesco,

What kind of error do you see when you run at the beginning:
sudo apt-get install python3-pygame
?

Thanks!

fdealexa · 2022-01-11 11:07 pm

Hi rpi,
during the download something like:
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian..
and at the end:
"Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?"
I have tryed, but this option does not resolve.
Regards and thanks,
Francesco

ambrits · 2022-02-12 9:17 am

Hi!

I wold like to use the PeppyMeter on my mpd (mini PC) streamer.

I would like to use the PeppyMeter on my mpd streamer. The system:

Arch Linux
Alsa
MPD
Chromium-kiosk

I follow de wiki doc and installed the PeppyAlsa plugin.

When I run the ./peppyalsa-client I have got the following:

Code:

Peppy ALSA Client. Goya Edition. 2018/09/08
No pipe name provided, defaulting to /home/pi/myfifo

If I play a music file, it's works, the sound is ok on the external dac but not show the L R indicators, like on the picture.

Code:

[root@hp src]# aplay -D peppyalsa song.wav 
Playing WAVE 'song.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

My soundcard:

Code:

0 [HDMI           ]: HDA-Intel - HDA Intel HDMI
                      HDA Intel HDMI at 0xf7c34000 irq 30
 1 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xf7c30000 irq 29
 2 [Audio          ]: USB-Audio - DigiHug USB Audio
                      FiiO DigiHug USB Audio at usb-0000:00:14.0-5, full speed

My asound.conf:

Code:

pcm.!default {
        type plug
        slave.pcm "softvol_and_peppyalsa"
}

ctl.!default {
        type hw
        card 2
}

pcm.peppyalsa {
        type meter
        slave.pcm "hw:2,0"
        scopes.0 peppyalsa
}

pcm.softvol_and_peppyalsa {
        type softvol
        slave.pcm "peppyalsa"
        control {
                name "PCM"
                card 2
        }
}

pcm_scope.peppyalsa {
    type peppyalsa
    decay_ms 400
    meter "/root/myfifo"
    meter_max 100
    meter_show 0
}
                                     
pcm_scope_type.peppyalsa {
        lib /usr/local/lib/libpeppyalsa.so
}

pcm.dsp0 peppyalsa

The myfifo file is created in the /root folder, but the size is 0.

I'm stuck here. I don't know where to go next. Can anyone help me with what could be the reason it is not working? Did I do something wrong or did I not understand something well?

Thanks!

rpi · 2022-02-12 6:45 pm

Hi ambrits,

Was the compilation and installation of the 'peppyalsa' plugin successful? To verify that make sure the following file exists in the folder:
/usr/local/lib/libpeppyalsa.so

I guess you use USB DAC. Just to make sure that card and device is 2:0 please show the output from the command 'aplay -l'.

When you play file you can check if anything comes to the named pipe by running command:
cat ~/myfifo
It should show some binary data which looks like garbage in the terminal. That will prove that data comes to the named pipe.

Best regards

ambrits · 2022-02-12 7:27 pm

rpi said:
Hi ambrits,

Was the compilation and installation of the 'peppyalsa' plugin successful? To verify that make sure the following file exists in the folder:
/usr/local/lib/libpeppyalsa.so

I guess you use USB DAC. Just to make sure that card and device is 2:0 please show the output from the command 'aplay -l'.

When you play file you can check if anything comes to the named pipe by running command:
cat ~/myfifo
It should show some binary data which looks like garbage in the terminal. That will prove that data comes to the named pipe.

Best regards

Hi rpi!

Grateful thanks for the answer!

The content of /usr/local/lib:

Code:

[root@hp lib]# ls -l
total 160
-rw-r--r-- 1 root root 82006 Feb 12 09:28 libpeppyalsa.a
-rwxr-xr-x 1 root root   987 Feb 12 09:28 libpeppyalsa.la
lrwxrwxrwx 1 root root    21 Feb 12 09:28 libpeppyalsa.so -> libpeppyalsa.so.0.0.0
lrwxrwxrwx 1 root root    21 Feb 12 09:28 libpeppyalsa.so.0 -> libpeppyalsa.so.0.0.0
-rwxr-xr-x 1 root root 70632 Feb 12 09:28 libpeppyalsa.so.0.0.0

aplay -l:

Code:

[root@hp lib]# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC221 Analog [ALC221 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Audio [DigiHug USB Audio], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Audio [DigiHug USB Audio], device 1: USB Audio [USB Audio #1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Wow, when I run the cat /root/myfifo and play the sound, it works. The indicators appears. I don't say that I mean exactly 🙂

According to these, PeppyAlsa installation is fine.
I need to install Peppymeter now.
I try it!

Thank you so much!

ambrits · 2022-02-12 9:42 pm

Hi rpi!

I installed Peppy Alsa to my non-test system.
When I play a song with aplay, it works fine, the myfifo include characters and appears the indicators.

If I play music with MPD, the mpd.log show this:
Feb 12 22:26 : player: played "Jazz-instrumental/Buddy Tate & Harry Edison/2019 - i cried for you (DSD)/01 - I've Got the World on a String.dsf"
Feb 12 22:26 : exception: Failed to open "peppyalsa" (alsa); Failed to open ALSA device "peppyalsa": Device or resource busy

My MPD conf:

Code:

audio_output {                                                                                                                                                         
    type            "alsa"                                                                                                                                         
    name            "UD-503"                                                                                                                                       
    device          "hw:CARD=UD503"                                                                                                                                
    mixer_type      "none"
    auto_resample   "no"                                                                                                                                           
    auto_channels   "no"                                                                                                                                           
    auto_format     "no"                                                                                                                                           
}                                                                                                                                                                      
                                                                                                                                                                       
audio_output {                                                                                                                                                         
    type        "alsa"                                                                                                                                                    
    name        "peppyalsa"                                                                                                                                               
    device      "peppyalsa"                                                                                                                                             
    mixer_type  "none"                                                                                                                                              
    dop         "no"                                                                                                                                                       
}

asound.conf (In the forum, I see the mistake and there as if such a setting would have been the solution🙂

Code:

pcm.peppyalsa { 
    type meter 
    slave.pcm "pippo" 
    scopes.0 peppyalsa
}

pcm.pippo { 
    type plug 
    slave.pcm "hw:CARD=UD503"
}

pcm_scope.peppyalsa {
    type peppyalsa
    decay_ms 400
    meter "/home/ambrits/myfifo"
    meter_max 100
    meter_show 1
}

pcm_scope_type.peppyalsa {
        lib /usr/local/lib/libpeppyalsa.so
}

pcm.dsp0 peppyalsa

What do I do wrong?

rpi · 2022-02-12 10:46 pm

Can you try to play just a regular WAV file? Also make sure that there is only one program which is "listening" to the pipe either PeppyMeter or peppyalsa-client, not both. Also there can be only one writer to the pipe.

ambrits · 2022-02-13 9:06 am

rpi said:
Can you try to play just a regular WAV file? Also make sure that there is only one program which is "listening" to the pipe either PeppyMeter or peppyalsa-client, not both. Also there can be only one writer to the pipe.

1. If I start the cat /home/ambrits/myfifo command, and parallel play a wav file, it works.

2. moving step by step so I have not installed Peppymeter yet, I only installed PeppyAlsa. After that try with mpd play. Peppysya-Client has no compiled on this machine.

If I understand the operation when I start a cat /home/ambrits/myfifo command, this command is the "listener" and it works when I play a WAV file.
Since there is no peppyalsa-client and no peppymeter what else can be listener?

This is my mpd.conf

Code:

audio_output {
    type        "alsa"
    name        "UD-503"
    device        "hw:CARD=UD503"
    mixer_type      "none"
    auto_resample    "no"
    auto_channels    "no"
    auto_format    "no"
}

audio_output {
    type "alsa"
    name "PeppyAlsa"
    device "peppyalsa"
    mixer_type "none"
    dop "no"
}
}

and my asound.conf

Code:

pcm.!default {
        type plug
        slave.pcm "softvol_and_peppyalsa"
}

ctl.!default {
        type hw
        card 1
}

pcm.peppyalsa {
        type meter
        slave.pcm "hw:1,0"
        scopes.0 peppyalsa
}

pcm.softvol_and_peppyalsa {
        type softvol
        slave.pcm "peppyalsa"
        control {
                name "PCM"
                card 1
        }
}

pcm_scope.peppyalsa {
    type peppyalsa
    decay_ms 400
    meter "/home/ambrits/myfifo"
    meter_max 100
    meter_show 1
}

pcm_scope_type.peppyalsa {
        lib /usr/local/lib/libpeppyalsa.so
}

pcm.dsp0 peppyalsa

When I switched HW: 0 to HW: 1, then the MPD error message has been discontinued, but if I run cat /home/ambrits/myfifo, it does not show anything. If I use HW: 0, peppyalsa is busy. My DAC is on the hw:0.

Code:

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: UD503 [UD-503], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Well guessing if I run Peppysya-client when MPD is playing, do I have to see something? If so, sorry is nothing 🙁

Any idea of what I didn't set up well?

rpi · 2022-02-13 5:02 pm

Hi,

It looks like you are trying to use the same ALSA device to output data to the DAC and peppyalsa plugin. You should have two separate outputs in your mpd.conf. One for the DAC and the other for the 'peppyalsa' plugin. Probably this post can be helpful:
https://github.com/project-owner/peppyalsa/issues/1#issuecomment-701853934
Best regards

ambrits · 2022-02-14 10:49 am

rpi said:
Hi,

It looks like you are trying to use the same ALSA device to output data to the DAC and peppyalsa plugin. You should have two separate outputs in your mpd.conf. One for the DAC and the other for the 'peppyalsa' plugin. Probably this post can be helpful:
https://github.com/project-owner/peppyalsa/issues/1#issuecomment-701853934
Best regards

Hi rpi!

Very thank you, this really helped. Now in MPD playback, data is also available on the console. The next step is the PeppyMeter install.

ambrits · 2022-02-14 1:40 pm

Hi!

A question before I move on: A Spostify Connect and Shairport-Sync can also be configured to use with PeppyAlsa?

Best regards.

rpi · 2022-02-14 4:13 pm

Hi,

As soon as there is a way to define 'peppyalsa' as the ALSA output device for the software player everything should work.
I'm sure you can do that for the Spotify and Spotify Connect. You just need to find the configuration file where you can define the ALSA output device.
You can find more details by searching for 'Spotify' in the same forum/thread:
https://community.volumio.org/t/pro...gin-for-volumio-v2-9xx-and-3-0xx-buster/45862
As far as I remember you can do the same for the shairport-sync by configuring the output device in the configuration file /etc/shairport-sync.conf:
output_device = "peppyalsa";

Though in that case you will need a different asound.conf file than you have for mpd - you will need to forward sound to the DAC from 'peppyalsa' entry.

Best regards

lifewater · 2022-04-07 11:52 am

ambrits said:
Hi!

A question before I move on: A Spostify Connect and Shairport-Sync can also be configured to use with PeppyAlsa?

Best regards.

Dont think so. Have been looking for this since last 2 years. Am using Moode Audio and the moment you use Bluetooth or Spotify Connect, it just displays the dumb "Bluetooth" or "Spotify Connect" screen😡

rpi · 2022-04-07 5:34 pm

Shairport-Sync/AirPlay should work with peppyalsa. You just need to set proper user/group as described here:
https://github.com/project-owner/Peppy/issues/9

The rest should also work. More likely it just needs changes in the .asoundrc file.

Best regards

lifewater · 2022-04-08 4:53 am

Tried but Moode audio crashes. I am not much of a coder so will not be able to give an expert opinion but wherever you look it seems other than the MPD Peppy meter is no supported in moodeaudio.

rpi · 2022-06-04 7:27 pm

Here are some examples of the Volumio screensaver which is using PeppyMeter:

rpi · 2022-06-06 10:14 pm

Hi,

I have just released the PeppySpectrum. This is new stand-alone program which can display Spectrum Analyzer. It leverages the same peppyalsa plugin as PeppyMeter. The structure and the configuration of the new program is also very similar to the PeppyMeter:
https://github.com/project-owner/PeppySpectrum
here is the documentation:
https://github.com/project-owner/PeppySpectrum.doc
The PeppySpectrum can be used either as a stand-alone program or integrated into any Pygame based program/UI.

Best regards

akasaka · 2022-06-29 9:59 pm

Can PeppyMeter be setup to display rotated 90degrees?

rpi · 2022-06-30 3:33 am

There is no such functionality out of the box. Though you can control rotation of your display/touchscreen for example using /boot/config.txt file.
But the meter has a fixed resolution it's not responsive/adaptive resolution. So it will not occupy the whole screen with vertical orientation. It will occupy fixed horizontal area 320x240, 480x320 etc.

Search

Amplifiers

Source & Line

Loudspeakers

Design & Build

General Interest

Live Sound

Member Areas

Site

Featured Vendors

Members Market

Vendors Market

Vendors

Search

PeppyMeter

fdealexa

rpi

fdealexa

ambrits

rpi

ambrits

ambrits

rpi

ambrits

rpi

ambrits

ambrits

rpi

lifewater

rpi

lifewater

rpi

rpi

akasaka

rpi