(03-28-2021, 03:02 PM)adrii Wrote: Hi Francesco

If the error is due to an incompatibility between your settings and the equalisers (rather than a direct issue with the mpd_oled configuration) then what is happening next may be that after producing the ALSA error MPD has not restarted correctly, and so you can put good seetings into /etc/asound.conf but MPD does not read them and you end up with the same ALSA error. Try editing /etc/asound.conf to use your device (bypassing the equaliser) and then restart MPD with 'sudo systemctl restart mpd' and then click on MPD Config "SAVE". I don't know all the details of this, it is just something I have noticed.

Do you get the same error with SoX disabled?

If you are still unable to troubleshoot this, then please run the following commands and post the contents of report.txt

Code:

wget http://www.antiprism.com/misc/mpd_oled_moode_audio_copy_report
bash mpd_oled_moode_audio_copy_report > report.txt

Adrian.

(03-28-2021, 04:03 PM)fdealexa Wrote:

(03-28-2021, 03:02 PM)adrii Wrote: Hi Francesco

If the error is due to an incompatibility between your settings and the equalisers (rather than a direct issue with the mpd_oled configuration) then what is happening next may be that after producing the ALSA error MPD has not restarted correctly, and so you can put good seetings into /etc/asound.conf but MPD does not read them and you end up with the same ALSA error. Try editing /etc/asound.conf to use your device (bypassing the equaliser) and then restart MPD with 'sudo systemctl restart mpd' and then click on MPD Config "SAVE". I don't know all the details of this, it is just something I have noticed.

Do you get the same error with SoX disabled?

If you are still unable to troubleshoot this, then please run the following commands and post the contents of report.txt

Code:

wget http://www.antiprism.com/misc/mpd_oled_moode_audio_copy_report
bash mpd_oled_moode_audio_copy_report > report.txt

Adrian.

Hi Adrian,
I created both the configuration (on rpi3 and on rpi4) from 2 scratch (7.1.0), without SoX and with mpd_oled only.
I am sure that you can reproduce it just starting with a clear uSD.
If you need I can do that (Please let me know) but, currently, I am working on another configuration.
Thanks and best regards,
Francesco

Quote:sudo systemctl restart mpd

(04-19-2021, 08:08 PM)jazzaj Wrote: Hi folks,

I can't get peppymeter working on my Moode.

I use 7.1, usb DAC and display on PC browser (FF) or phone browser (FF too)

Everything works fine till seing VU meters on display :

Code:

pi@moOde:~/PeppyMeter $ sudo python3 peppymeter.py
pygame 1.9.4.post1
Hello from the pygame community. https://www.pygame.org/contribute.html
Traceback (most recent call last):
 File "peppymeter.py", line 238, in <module>
   pm.init_display()
 File "peppymeter.py", line 142, in init_display
   pygame.display.init()
pygame.error: Unable to open mouse

Ctrl C

Code:

Exception ignored in: <module 'threading' from '/usr/lib/python3.7/threading.py'>
Traceback (most recent call last):
 File "/usr/lib/python3.7/threading.py", line 1281, in _shutdown
   t.join()
 File "/usr/lib/python3.7/threading.py", line 1032, in join
   self._wait_for_tstate_lock()
 File "/usr/lib/python3.7/threading.py", line 1048, in _wait_for_tstate_lock
   elif lock.acquire(block, timeout):
KeyboardInterrupt

 
I see nothing on display except Moode classical UI.

I also have to use mixer type : Fixed. It's usually set to Hardware but with this setting I can't see the L/R bars under putty. Sofware causes me MPD error.
Another thing, I don't have to change the line

Code:

"pipe.name = /var/tmp/peppyfifo"

under config.txt but create it because it's not in the original file.

I tried to play with Local display on system config but it changes nothing

What's supposed to be wrong in my case ?