PeppyMeter and moOde

[TheOldPresbyope]

@fdealexa

Hi, Francesco.

Since you've asked others to post a picture, attached is a poorly composed snap of my 7" Touch Screen with the vintage meter selected. (Aside: it's not unlike the meters on the first stereo console I got to run in a small radio station w-a-y back in the last century.)

This is with moOde 7.0.1 running on a RPi3B+.

Your instructions worked fine.

I have a few minor notes you may find useful:

1. I think you should edit your tutorial post (#5) to explain more carefully what information is to be gleaned from aplay -l and how it's to be used. You explained it in a followup post (#19) but this information should be up front.

2. For your purpose, it is sufficient to clone only the more recent state of the repos

Code:

git clone --depth=1 https://github.com/<whatever>

For the peppymeter repos this doesn't make much of a difference but with major repos it can avoid downloading hundreds or thousands of git objects which won't be used. This is faster and consumes less bandwidth and storage. This is generally best practice if you don't intend to make commits and pull requests.

3. Several places you create or edit files as root (sudo ...) when they could just as well be owned by user pi. In your particular application this causes no harm operationally but in other instances it might and it's not best practice generally. These files include /home/pi/PeppyMeter/config.txt, /home/pi/PeppyMeter/peppymeter.py, and /home/pi/.asound.conf.

4. If you read the ALSA documentation, you'll find that having identical /etc/asound.conf and /home/pi/.asound.conf files is redundant. In my case, I created just /etc/asound.conf but I could have created just /home/pi/.asound.conf.

5. Finally, a heads up! In moOde 7.1.0, the module /var/www/inc/playerlib.php will contain changes which invalidate your instruction for editing it. You can examine its current status in the develop branch of Tim's repo: https://github.com/moode-player/moode.git

ETA

6. That "libpng warning: iCCP: known incorrect sRGB profile" message is just that, a warning. It can be ignored or if it really bothers someone they can edit the image files to remove the offending color profile. I used a utility in the ImageMagick toolbox. Consult your favorite search engine. 


Regards,
Kent

PS - I'm pretty sure I had another point but I stopped to feed the cat and now I've forgotten what it was  Must not have been very important I remembered. See #6.