PeppyMeter

Jump to Latest
#383
First Step on Installing PeppyMeter on moOde

Hi everybody, as you probably know, I am trying to integrate PeppyMeter in the moOde environment.
I have succesfully installed PeppyAlsa and it seems that is running:
please see attached:
PeppyAlsa OK.jpg.
I am, now, working on the PeppyMeter: please find attached the config.txt, the list of the fb* devices and the command I am trying:
PeppyMeter test 1 of 2.jpg
PeppyMeter test 2 of 2.jpg
and the result, on the touchscreen is:
PeppyMeter no OK.jpg

Please, be so kind to give some suggeastions to me.
Thanks in advance and best regards,
Francesco
 

Attachments

  • PeppyAlsa OK.jpg
    PeppyAlsa OK.jpg
    45.8 KB · Views: 193
  • PeppyMeter test 1 of 2.jpg
    PeppyMeter test 1 of 2.jpg
    72.2 KB · Views: 191
  • PeppyMeter test 2 of 2.jpg
    PeppyMeter test 2 of 2.jpg
    82.5 KB · Views: 191
  • PeppyMeter no OK.jpg
    PeppyMeter no OK.jpg
    81.4 KB · Views: 198
#384
Hello again,
after some test I discovered that it seems those errors disappered if the command is launched from /home/pi/PeppyMeter but the result is that on the display it appears only:

pygame 1.9.4.post1
Hello from the pygame community. Contribute - pygame wiki

Does make it sense for anybody?
Help me, help me, help me, please!

Thanks and best regards,
Francesco
 
#387
rpi said:
Hi Francesco,

I'm not familiar with Moode.
Where are you trying to start PeppyMeter? I hope you know that you cannot start it in the SSH session (e.g. putty) as there is no graphical context.

Best regards
Click to expand...

Thank you so much for your answer.
Yes, I know: I tried with "openvt -s" from SSH, but the best result I got was with the keyboard direcly connected to the Rpi but the result was just two small rectangles at the bottom of the screen which changed a little colors as the music changes .
If I stop the music the rectangles remain stable. Those little rectangles were like an analog TV display when you're not tuned.
I will keep trying.
Any help will be highly appreciated.
Best regards and thanks again,
Francesco
 
#388
So, I believe you are trying to display PeppyMeter in some display. Do you use Raspberry Pi or some other system? What is display model? How is it connected to the computer (HDMI, SPI, DSI)?

Did you modify the PeppyMeter source files? If not, you can start the program this way (from the folder /home/pi/PeppyMeter):
openvt -s -- python3 peppymeter.py
no need to specify pipe name in this line. It should be defined in the file /home/pi/PeppyMeter/config.txt:
PeppyMeter/config.txt at 994b00888c32e7e173dcb650719daac1fa36719b * project-owner/PeppyMeter * GitHub
You can also define framebuffer in the same file. In your case it should be fb0:
PeppyMeter/config.txt at 994b00888c32e7e173dcb650719daac1fa36719b * project-owner/PeppyMeter * GitHub

Best regards
 
#389
Thanks a lot "RPI",
I am using a rpi 4 b with 4 gB, the output is the original 7" touchscreen. The config.txt and some other info has been reporter on the attachments in the post #383. I am using fb0
I will try without the pipe name in the command line.
A question: the commad openvt -s is needed only of I use the SSH or even if I start directly from the keyboard?
I don't have any words to thank you for your kind cooperation.
Best regards and thanks again,
Francesco
 
#390
Indigent Audio said:
So moode is mostly headless but the moode output /track/title/spectrum analysis/volume level can be piped out to a small format led screen by using the 40 pin on the pi and a little code.

LCD/OLED display using pydPiper

I am looking to pipe the peppymeter out to a led screen in the same way.
Click to expand...

Thanks a lot for your information.
I will follow that thread to see it any suggestione.
Thanks again and best regards,
Francesco
 
#392
Hello "rpi", thank you very much.
I think we are closer to "make it happen".
I just tried with the modification and the meter appared. I saw some garbage on the screen and it seems that something happened on the sound.
Tomorrow I will try with a clean installation (Now it is 01:20 am here).
Thanks again and best regards,
Francesco
 
#394
Hello rpi, thanks a lot,
with the modification of the exclusion of the double buffer, it is running.

I'm sorry to disturb you but I still have some issue:
1. I can run the program only from the keybord connected to the rpi but not with the command (ssh):
Code: 
sudo openvt -s -- python3 peppymeter.py
of course in the default directory PeppyMeter. The result on the rpi screen is:
Code: 
pygame 1.9.4.post1
Hello from the pygame community. [url=https://pygame.org/contribute.html]Contribute - pygame wiki[/url] - pygame wiki
freezing the screen and the rpi keyboard.

2. when I start the program from the rpi keyboard everything seems ok but if I stop the program ^C on the screen appears a lot of line with the message:
Code: 
libpng warning: iCCP: known incorrect sRGB profile
but the screen remain not freezed and I can go on.

Thank you very much again and best regards,
Francesco
 
Last edited:
#395
Regarding the problem #1 try to read the messages from lintbf starting from the message #366. More likely that's related to blocking/unblocking virtual terminal. He mentioned such commands as 'deallocvt', 'fgconsole', 'chvt'. Check if they can help in your case.

The issue #2 looks like the program just flushes the buffer with regular messages when you stop it. Just ignore those messages if possible.

Best regards
 
Last edited:
#396
Hello "rpi", good evening.
for the first problem i solved by using the standard redirect ">" instead of "openvt". I tried to work with the post commands you suggested but no results.
Unfortunately, now, I am stuck because I added the DAC board and I am no longer able to run peppyalsa ... 🙁
I will continue to try and, just in case, I will try to disturb you for your precious help.
Thank you and good night
Francesco
 
#398
Hello "rpi",
tonight I'm quite disappointed and sad: I've been trying all day to make it work but to no avail.
If you would be very kind to help me again, I apologize, please find some information below

pi@moOde-Sala-Hobby:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: DAC [I-Sabre Q2M DAC], device 0: I-Sabre Q2M DAC i-sabre-codec-i2c.1-0048-0 [I-Sabre Q2M DAC i-sabre-codec-i2c.1-0048-0]
Subdevices: 0/1
Subdevice #0: subdevice #0


pi@moOde-Sala-Hobby:~ $ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
btaplay_dmix
alsaequal
plug_alsaequal
btstream
camilladsp
crossfeed
plug_bs2b
eqfa12p
plug_eqfa12p
invpolarity
peppyalsa
softvol_and_peppyalsa
default
sysdefault:CARD=DAC
I-Sabre Q2M DAC, I-Sabre Q2M DAC i-sabre-codec-i2c.1-0048-0
Default Audio Device
dmix:CARD=DAC,DEV=0
I-Sabre Q2M DAC, I-Sabre Q2M DAC i-sabre-codec-i2c.1-0048-0
Direct sample mixing device
dsnoop:CARD=DAC,DEV=0
I-Sabre Q2M DAC, I-Sabre Q2M DAC i-sabre-codec-i2c.1-0048-0
Direct sample snooping device
hw:CARD=DAC,DEV=0
I-Sabre Q2M DAC, I-Sabre Q2M DAC i-sabre-codec-i2c.1-0048-0
Direct hardware device without any conversions
plughw:CARD=DAC,DEV=0
I-Sabre Q2M DAC, I-Sabre Q2M DAC i-sabre-codec-i2c.1-0048-0
Hardware device with all software conversions
pi@moOde-Sala-Hobby:~ $


Part of /var/log/mpd/log

Jan 14 00:44 : client: [15] opened from 127.0.0.1:34756
Jan 14 00:44 : client: [15] process command "play"
Jan 14 00:44 : playlist: play 2:"http://sj256.hnux.com"
Jan 14 00:44 : client: [15] command returned 0
Jan 14 00:44 : client: [15] process command "close"
Jan 14 00:44 : client: [15] command returned 4
Jan 14 00:44 : client: [15] closed
Jan 14 00:44 : curl: icy-metaint=16384
Jan 14 00:44 : decoder_thread: probing plugin mad
Jan 14 00:44 : decoder: audio_format=44100:24:2, seekable=false
Jan 14 00:44 : client: [8] process command "status"
Jan 14 00:44 : alsa_output: opened hw:0,0 type=HW
Jan 14 00:44 : alsa_output: buffer: size=64..65536 time=1451..1486078
Jan 14 00:44 : alsa_output: period: size=32..32768 time=725..743039
Jan 14 00:44 : alsa_output: default period_time = buffer_time/4 = 500000/4 = 125000
Jan 14 00:44 : alsa_output: format=S32_LE (Signed 32 bit Little Endian)
Jan 14 00:44 : alsa_output: buffer_size=22050 period_size=4410
Jan 14 00:44 : output: opened "ALSA default" (alsa) audio_format=44100:32:2
Jan 14 00:44 : output: converting in=44100:24:2 -> f=44100:24:2 -> out=44100:32:2
Jan 14 00:44 : exception: Failed to open "peppyalsa" (alsa); Failed to open ALSA devic e "peppyalsa": Device or resource busy
Jan 14 00:44 : client: [8] command returned 0
Jan 14 00:44 : client: [13] process command "status"
Jan 14 00:44 : client: [13] command returned 0


pi@moOde-Sala-Hobby:~ $ cat /etc/asound.conf
pcm.!default {
type plug
slave.pcm "softvol_and_peppyalsa"
}

ctl.!default {
type plughw
card 0
}

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

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

pcm_scope.peppyalsa {
type peppyalsa
decay_ms 400
meter "/tmp/peppyfifo"
meter_max 100
meter_show 0
spectrum "/tmp/peppyfifosa"
spectrum_max 100
spectrum_size 30
}

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

pi@moOde-Sala-Hobby:~ $
Click to expand...
Best regards and thanks,
Francesco

P.S.: the command to redirect I used is
python3 peppymeter.py > /dev/fb0
Click to expand...
Thanks again
 
You must log in or register to reply here.
Top Bottom