Login

rajivkumar1984 · 07-01-2023, 08:46 PM

@fdealexa @Patolog1964 Any inputs please....Will really appreciate your help.

fdealexa · 07-02-2023, 07:46 PM

Hi Rajiv,
1) this is a reccomendation by Tim Curtis:
"Starting with release 8.3.0 we adopted the RaspiOS Bullseye security enhancements and our release images do not contain default userid/password, SSH or AP mode password.
You can use the Raspberry Pi Imager to easily enable SSH, create a userid/password and optionally a WiFi SSID/password. You can also use dd or any other image writer but the security prep has to be done manually.
Your best bet is to read the moOde Setup Guide".
That means that you have to setup User e password for SSH with the "Raspberry Pi Imager", as I normally use. an alternative is to follow the following thread: HowTo: install moOde without using the RPi Imager tool.
2) I already answered to this question on the DIYAudio forum (link to thread); this is the answer:"Hi, About the second question: the process for version 7.2 is still valid. Take care because Boss 2 has a problem with linux 6.1. On the moode forum there is a workaround to solve it. If any problem do not hesitate to ask. On moode forum there is a dedicated thread."
3) I don't see any problem with the described configuration.

I repeat: If any problem do not hesitate to ask.

Best regards and good luck,
Francesco

rajivkumar1984 · 07-03-2023, 03:41 PM

Thanks @fdealexa I have successfully setup Moode Audio on RPI 4 with an IFI DAC. Now I will try to run install Peppy Meter on the same.

rajivkumar1984 · 07-04-2023, 12:11 PM

(02-10-2021, 06:55 PM)fdealexa Wrote: First of all let us open a putty session on our moOde system and run:

Code:
aplay -l
and take care of the result because it will be useful later.

PeppyMeter needs PeppyAlsa to run: so we need first to install and adapt it to our environment.

Code:
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

Now we have to create 2 files with the same contents (in the third row (slave.pcm) we have to put the default output we had in "aplay -l": normally "hw:0,0" or "hw:1,0")

Code:
sudo nano /etc/asound.conf

Copy and past the following content:

Code:
pcm.peppyalsa { type meter slave.pcm "hw:1,0" scopes.0 peppyalsa } pcm_scope.peppyalsa { type peppyalsa decay_ms 400 meter "/var/tmp/peppyfifo" meter_max 100 meter_show 0 spectrum "/var/tmp/peppyfifosa" spectrum_max 100 spectrum_size 30 } pcm_scope_type.peppyalsa { lib /usr/local/lib/libpeppyalsa.so }

Quote:^o and Enter to save and then ^x to exit.

Let's create the second file:

Code:
sudo cp /etc/asound.conf /home/pi/.asoundrc

At this point we have to patch an important file that create the configuration of moOde MPD:

Code:
sudo nano /var/www/inc/playerlib.php

Quote:^-1994 to go to row 1994 and modify the current content from:

Code:
"name \"ALSA default\"\n" . "device \"hw:" . $device . ",0\"\n",

to the new content:

Code:
"name \"ALSA default\"\n" . "device \"peppyalsa\"\n",

^o and Enter to save and then ^x to exit.

Now reboot the system and try to listen any music (a radio is the simplest way) if it is still alive!!! If not we have to troubleshoot where we made a mistake.

If everything is ok let's continue:

Code:
cd /home/pi/peppyalsa/src gcc peppyalsa-client.c -o peppyalsa-client

At this point let's test all the chain:

Code:
/home/pi/peppyalsa/src/peppyalsa-client /var/tmp/peppyfifo

Listening the music we should see on the putty screen a couple of bar moving with the music intensity, as the following picture:

Now we are closer to the end: we have, now, to install PeppyMeter

Code:
cd /home/pi git clone https://github.com/project-owner/PeppyMeter.git sudo apt-get install python3-pygame cd /home/pi/PeppyMeter

Now we have to configure our PeppyMeter:

Quote:
Code:
sudo nano /home/pi/PeppyMeter/config.txt

modifying the following contents:

Code:
"screen.size = large" "framebuffer.device = /dev/fb0" "mouse.device = /dev/input/event0" "pipe.name = /var/tmp/peppyfifo"

^o and Enter to save and then ^x to exit.

Now we have to modify the program to disable the double buffer:

Quote:
Code:
sudo nano /home/pi/PeppyMeter/peppymeter.py

^-142 to go to row 142 and modify the current content from:

Code:
self.util.PYGAME_SCREEN = pygame.display.set_mode((screen_w, screen_h), pygame.DOUBLEBUF, depth)
to the new content:

Code:
self.util.PYGAME_SCREEN = pygame.display.set_mode((screen_w, screen_h))

^o and Enter to save and then ^x to exit.

At this point we have finished. To see the meter on the default display we have to start listening music and:

Code:
cd /home/pi/PeppyMeter sudo python3 peppymeter.py > /dev/fb0

We should see, on the display, a kind of meter that changes every 20 seconds (time can be changed in the config.txt).
On the Putty screen appears a couple of message every change.
I suggest that, once you have decided what you prefer, we have to stop the meter:

Quote:^c^c

The available type of meter, for the "large" size we have choosen, at the moment, are:

Quote:bar

blue
vintage
dash
gas
rainbow
grunge
royal
compass
gold
black-white
white-red
orange
blue-2
emerald
red
tube

then configure our PeppyMeter:

Quote:
Code:
sudo nano /home/pi/PeppyMeter/config.txt

modifying the following contents. From:

Code:
"meter = random"

to e.g.:

Code:
"meter = emerald"

^o and Enter to save and then ^x to exit.

Then start again:

Code:
cd /home/pi/PeppyMeter sudo python3 peppymeter.py > /dev/fb0

Enjoy listening music... and its graphic

Dear Francesco,

I have just begun to use your tutorial to install Peppy Meter. If you can kindly guide me on the steps please ---

1. To begin this is what I am getting when I type aplay -I. You mentioned in one of the steps that - we have to put the default output we had in "aplay -l": normally "hw:0,0" or "hw:1,0"). I don't find either of them. Can you please advise what is the default output as per the command I ran below ----

rajivkumar1984@moode:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 2: Audio [iFi (by AMR) HD USB Audio], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

2. Also when I typer and run - git clone https://github.com/project-owner/peppyalsa.git, I am getting the below error message

-bash: git: command not found

I have also attached the screenshot for your reference.

https://ibb.co/rmBHb0c

-bash: git: command not found
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 2: Audio [iFi (by AMR) HD USB Audio], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

Nutul · 07-04-2023, 12:57 PM

Quote:card 2: Audio [iFi (by AMR) HD USB Audio], device 0: USB Audio [USB Audio]

note the BOLD numbers above: for you it should be hw:2,0

Quote:2. Also when I typer and run - git clone https://github.com/project-owner/peppyalsa.git, I am getting the below error message

-bash: git: command not found

You need to install git:

sudo apt install git

rajivkumar1984 · 07-04-2023, 01:41 PM

Awesome..let me run it and come back to you

rajivkumar1984 · (This post was last modified: 07-04-2023, 01:50 PM by rajivkumar1984.)

(07-04-2023, 12:57 PM)Nutul Wrote:
Quote:card 2: Audio [iFi (by AMR) HD USB Audio], device 0: USB Audio [USB Audio]
note the BOLD numbers above: for you it should be hw:2,0

Quote:2. Also when I typer and run - git clone https://github.com/project-owner/peppyalsa.git, I am getting the below error message

-bash: git: command not found

You need to install git:

sudo apt install git

Dear @Nutul - I am getting some weird error while running the suggested command - sudo apt install git
can you please look into the below and suggest as what is actually going wrong. I am a non-technical guy new to python/debian

rajivkumar1984@moode:~ $ sudo apt install git
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
git-man liberror-perl
Suggested packages:
git-daemon-run | git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-cvs git-mediawiki git-svn
The following NEW packages will be installed:
git git-man liberror-perl
0 upgraded, 3 newly installed, 0 to remove and 24 not upgraded.
Need to get 7,282 kB of archives.
After this operation, 37.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Ign:1 http://deb.debian.org/debian bullseye/main arm64 liberror-perl all 0.17029-1
Ign:2 http://deb.debian.org/debian bullseye/main arm64 git-man all 1:2.30.2-1+deb11u2
Ign:3 http://deb.debian.org/debian bullseye/main arm64 git arm64 1:2.30.2-1+deb11u2
Err:1 http://deb.debian.org/debian bullseye/main arm64 liberror-perl all 0.17029-1
Could not resolve 'deb.debian.org'
Ign:2 http://deb.debian.org/debian bullseye/main arm64 git-man all 1:2.30.2-1+deb11u2
Err:3 http://deb.debian.org/debian bullseye/main arm64 git arm64 1:2.30.2-1+deb11u2
Could not resolve 'deb.debian.org'
Ign:2 http://deb.debian.org/debian bullseye/main arm64 git-man all 1:2.30.2-1+deb11u2
Err:2 http://deb.debian.org/debian bullseye/main arm64 git-man all 1:2.30.2-1+deb11u2
Could not resolve 'deb.debian.org'
E: Failed to fetch http://deb.debian.org/debian/pool/main/l...-1_all.deb Could not resolve 'deb.debian.org'
E: Failed to fetch http://security.debian.org/debian-securi...u2_all.deb Could not resolve 'deb.debian.org'
E: Failed to fetch http://security.debian.org/debian-securi..._arm64.deb Could not resolve 'deb.debian.org'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
rajivkumar1984@moode:~ $

**TheOldPresbyope** · 07-04-2023, 02:19 PM

@rajivkumar1984

The same command worked on a test host here (eastern USA).

As the error message suggested, try first executing "sudo apt-get update" and then rerunning the "sudo apt install git" command.

Regards,
Kent

rajivkumar1984 · (This post was last modified: 07-04-2023, 05:50 PM by rajivkumar1984.)

I Tried that but even the update is not happening properly, any idea what might be the reason ?

This is the error message I get while running sudo apt update

Code:
W: Some index files failed to download. They have been ignored, or old ones used instead.

fdealexa · 07-04-2023, 10:56 PM

Please follow the documentation on github https://github.com/FdeAlexa/PeppyMeter_and_moOde.
Thanks and best regards,
Francesco

Login
Username:
Password:	Lost Password?
	Remember me