PeppyMeter and moOde

[snivelfr]

Hello Francesco,

So i've made a test with a fresh install, and Peppymeter only, and it worked.

To understand what could be at the source of the issue, I started to add the Audiophonics scripts about Power Management, and in time, Peppymeter wouldn't show up.

The issue started when I add the line

Code:

    python /home/pi/spc_moode.py shutdown

To the file

Code:

cd /var/local/www/commandw/restart.sh

As per the explanations provided by Audiophonics regarding the Power Management button tool which github is :

Code:

https://github.com/audiophonics/Raspberry-pwr-management/blob/master/README.md

But honestly, i don't understand why this could cause such a difference.

Of course, there is the other program ( https://github.com/audiophonics/Raspberr...c_moode.py ) which is the one called by the restart program. But it is called only when I want to stop the PI.

Any thoughts about it ?

[fdealexa]

Hello Francesco,

So i've made a test with a fresh install, and Peppymeter only, and it worked.

To understand what could be at the source of the issue, I started to add the Audiophonics scripts about Power Management, and in time, Peppymeter wouldn't show up.

The issue started when I add the line

Code:

    python /home/pi/spc_moode.py shutdown

To the file

Code:

cd /var/local/www/commandw/restart.sh

As per the explanations provided by Audiophonics regarding the Power Management button tool which github is :

Code:

https://github.com/audiophonics/Raspberry-pwr-management/blob/master/README.md

But honestly, i don't understand why this could cause such a difference.

Of course, there is the other program ( https://github.com/audiophonics/Raspberr...c_moode.py ) which is the one called by the restart program. But it is called only when I want to stop the PI.

Any thoughts about it ?

Hello snivelfr,
This is a good new.
Today I will try to replicate your problem and I will informe you.
Have a good day,
Francesco

[fdealexa]

@PeterLustig33

Hi Peter,
Please use the following paramenter:

Code:

screen.width = 1600
screen.height = 1200

and let us know.
Regards,
Francesco

Hi Peter,
How are you? I hope better: have you tried the suggested parameters?
Have a good weekend,
Francesco

[fdealexa]

@snivelfr
Hi, would you please be so kind to take some pictures of the internal connection of your RaspTouch? In details the power switch leads, the DAC board, the connection of the switch to the DAC (the cable is probably 4 wires white-black-red-brown).
I have tried to install the software but I hadn't any stop to the PeppyMeter: tomorrow I will continue to work.
Good night,
Francesco

[kuyadreiph]

Hi dev! I do the instructions but it's seems not working with me. I flashed the latest moode os using raspberry pi imager. And boot up and configure using raspberry pi 4 model b 2gb ram.
I run some command as posted here.
It says after i run so I've got stuck with this.

Code:

dell@moodeplayer:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: IQaudIODAC [IQaudIODAC], device 0: IQaudIO DAC HiFi pcm512x-hifi-0 [IQaudIO DAC HiFi pcm512x-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
dell@moodeplayer:~ $ git clone https://github.com/project-owner/peppyalsa.git
cd peppyalsa
sudo apt-get install build-essential autoconf automake libtool libasound2-dev libfftw3-dev
aclocal && libtoolize
autoconf && automake --add-missing
./configure && make
sudo make install
-bash: git: command not found
-bash: cd: peppyalsa: No such file or directory
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
autoconf is already the newest version (2.69-14).
autoconf set to manually installed.
automake is already the newest version (1:1.16.3-2).
automake set to manually installed.
build-essential is already the newest version (12.9).
libtool is already the newest version (2.4.6-15).
libtool set to manually installed.
The following additional packages will be installed:
libfftw3-bin libfftw3-long3
Suggested packages:
libasound2-doc libfftw3-doc
The following NEW packages will be installed:
libasound2-dev libfftw3-bin libfftw3-dev libfftw3-long3
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,155 kB of archives.
After this operation, 12.0 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bullseye/main arm64 libfftw3-long3 arm64 3.3.8-2 [526 kB]
Get:2 http://deb.debian.org/debian bullseye/main arm64 libfftw3-bin arm64 3.3.8-2 [47.4 kB]
Get:3 http://deb.debian.org/debian bullseye/main arm64 libfftw3-dev arm64 3.3.8-2 [1,455 kB]
Get:4 http://archive.raspberrypi.org/debian bullseye/main arm64 libasound2-dev arm64 1.2.4-1.1+rpt2 [126 kB]
Fetched 2,155 kB in 3s (824 kB/s)
Selecting previously unselected package libasound2-dev:arm64.
(Reading database ... 60061 files and directories currently installed.)
Preparing to unpack .../libasound2-dev_1.2.4-1.1+rpt2_arm64.deb ...
Unpacking libasound2-dev:arm64 (1.2.4-1.1+rpt2) ...
Selecting previously unselected package libfftw3-long3:arm64.
Preparing to unpack .../libfftw3-long3_3.3.8-2_arm64.deb ...
Unpacking libfftw3-long3:arm64 (3.3.8-2) ...
Selecting previously unselected package libfftw3-bin.
Preparing to unpack .../libfftw3-bin_3.3.8-2_arm64.deb ...
Unpacking libfftw3-bin (3.3.8-2) ...
Selecting previously unselected package libfftw3-dev:arm64.
Preparing to unpack .../libfftw3-dev_3.3.8-2_arm64.deb ...
Unpacking libfftw3-dev:arm64 (3.3.8-2) ...
Setting up libfftw3-long3:arm64 (3.3.8-2) ...
Setting up libasound2-dev:arm64 (1.2.4-1.1+rpt2) ...
Setting up libfftw3-bin (3.3.8-2) ...
Setting up libfftw3-dev:arm64 (3.3.8-2) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u7) ...
aclocal: error: 'configure.ac' is required
autoconf: error: no input file
-bash: ./configure: No such file or directory
make: *** No rule to make target 'install'.  Stop.
dell@moodeplayer:~ $ sudo nano /etc/asound.conf
dell@moodeplayer:~ $ sudo cp /etc/asound.conf /home/pi/.asoundrc
cp: cannot create regular file '/home/pi/.asoundrc': No such file or directory

[DRONE7]

You may wish to wait for fdealexa to confirm...:-) but this line in your output...
-bash: git: command not found
says you don't have git installed and so the file can't be downloaded.
..fix is to run

sudo apt install git

and when that finishes rerun the code from the beginning.

[fdealexa]

You may wish to wait for fdealexa to confirm...:-) but this line in your output...
-bash: git: command not found
says you don't have git installed and so the file can't be downloaded.
..fix is to run

sudo apt install git

and when that finishes rerun the code from the beginning.

@DRONE7 
Bob,
I think you are right: the git installation has been missed
@kuyadreiph
May I point out a couple of things more:
. The procedure is based on a system where the default user is "pi"
. I reccomend to execute the commands one by one  (to see the single result in case of problems)
Best regards and thanks
Francesco

P.S. I am not the dev of peppymeter: I only installed it in the moode environment

[sorincp21]

Hi all,
I’ve installed PeppyMeter on MoOde 8.3.9 and it’s working great as a standalone VUmeter.
I was wondering if there is a way to overlay/integrate PeppyMeter on moode audio player GUI.
I am only able to see either the PeppyMeter, or the player GUI, never both in the same time.
Thanks!

[fdealexa]

Hi sorincp21,
Welcome on board of the moOde forum.
I'm sorry but, based on my knowledge, I am unable to answer your question.
Maybe someone else will be kind enough to answer you.
Best regards,
Francesco

[TheOldPresbyope]

 was wondering if there is a way to overlay/integrate PeppyMeter on moode audio player GUI.

My grandmother was fond of saying "where there's a will, there's a way." My first boss was more blunt, "if it were easy, it would have been done already."

Anyone can start with moOde's FOSS code---just clone the repo---and integrate these two views on a new branch. 

Things to remember: the display real estate is very limited and both its size and aspect ratio differ from one user device (and orientation) to another. The views have to be aesthetically pleasing whether the Peppymeter option is enabled or disabled.

I'm no front-end developer, so maybe I'm being pessimistic, but this looks like more than a weekend effort.  

There's plenty of folk who'd give the result a test drive.


Regards,
Kent