Interesting and could very well be. I had issues with the latest Pi imager last week trying to get a RPi working with an old OS image (not moOde). Good old Balena Etcher worked for me.
Member @Jim Creek appears to have had the same problem in this thread regarding Moode APPARENTLY booting fine, but attempts at configuration hangs the program
https://www.diyaudio.com/community/threads/new-to-moode-got-questions.398863/#post-7340803
https://www.diyaudio.com/community/threads/new-to-moode-got-questions.398863/#post-7340803
no luck with this
even Fing can't find moode
i am trying to find the IP...consulting Dr. Google
btw, i am using pi imager to configure ssh, ssid, pswd, etc. nothing
now, the moode os shuts down right after it boots up, or after like 5 seconds. I flashed my card several times, wiped it a couple of times, used different apps that you guys are using. But no luck.
I must be doing something wrong as nothing seems to be working. Yet, Volumio pops right up!
I will report when/if I figure this out.
Hello all. I'm building my first dac. Now all the hardware part have been done and I'm configuring the buttons. That's ok, but for one I would have te same behavior as the star on the web interface (load a random album and play it). I find a way with a script, but there IS a lot of commands and it is working only with one directory. There is a way to do that simpler with on 1 or 2 lines? Thanks.
That feature is implemented entirely in Javascript in the Front-end. Have a look in scripts-library.js at event handler $('.ralbum').click(function(e) {...
I suppose the options are to (1) recreate the functionality in a back-end script if WebUI is not to be involved or (2) modify the front-end code that handles custom commands sent from the back-end. In this case the code would simulate a click on the * icon. It would require that the WebUI is running on a client.
I suppose the options are to (1) recreate the functionality in a back-end script if WebUI is not to be involved or (2) modify the front-end code that handles custom commands sent from the back-end. In this case the code would simulate a click on the * icon. It would require that the WebUI is running on a client.
RADIO CONNECT ISSUE
Hello all, not sure how this post will fit into the entire thread as there seems to be 1 single thread for all moOde questions
I finally decided to move form standard mpd to moOde and dedicate my Rpi2 B for this purpose.
I use a USB bluetooth dongle as well as a USB DAC to stream from my NAS.
Let me try to describe my issue
Step 1: NAS audio works fine - radios work fine
Step 2: try to add some radios. 1st radio works fine, 2nd radio not (but the address works fine)... and for whatever reason no radio can stream anymore - NAS audio not working (no sound, and when I drag the song cursor, i hear music for a fraction of a second then silence...everytime)
Step 3: reboot (error message pops up over and over, on moode-local interface during boot
Step 4: enable bluetooth - pairs properly and works fine
Step 5: disconnect - NAS audio DOES NOT work anymore !! - radio still showing the same problem - but able to stream connect/disconnect with the bluetooth without problem
(I realized that for whatever reason the Volume type was setup to software (which was at 0) while I usually use hardware)
So finally NAS audio OK, Bluetooth audio OK....radio audio NOK
Any idea what could be the problem with the radios (even the pre-installed ones do not work) ?
Hello all, not sure how this post will fit into the entire thread as there seems to be 1 single thread for all moOde questions
I finally decided to move form standard mpd to moOde and dedicate my Rpi2 B for this purpose.
I use a USB bluetooth dongle as well as a USB DAC to stream from my NAS.
Let me try to describe my issue
Step 1: NAS audio works fine - radios work fine
Step 2: try to add some radios. 1st radio works fine, 2nd radio not (but the address works fine)... and for whatever reason no radio can stream anymore - NAS audio not working (no sound, and when I drag the song cursor, i hear music for a fraction of a second then silence...everytime)
Step 3: reboot (error message pops up over and over, on moode-local interface during boot
radios still do not work (error message below)
NAS audio works fine
Step 4: enable bluetooth - pairs properly and works fine
Step 5: disconnect - NAS audio DOES NOT work anymore !! - radio still showing the same problem - but able to stream connect/disconnect with the bluetooth without problem
(I realized that for whatever reason the Volume type was setup to software (which was at 0) while I usually use hardware)
So finally NAS audio OK, Bluetooth audio OK....radio audio NOK
Any idea what could be the problem with the radios (even the pre-installed ones do not work) ?
Thank you very much Tim.
I finally kept my python script which, associated with a button, work fine for me.
Here is what I use if it can be usefull for others. As I'm not developer I have done that with many lines.
Small update all the ? marked URL stations are the ones that don't play anymore.... while the OK ones work just fine. What could have happened so that these ? stations are not working anymore ?
Quick update: I managed to make it work (= add radio URLs without compromising with the Curl error most of them). It seems like setting a static IP was the issue. If I keep it as DHCP, then no problem...if static, then it fails and I need to re-flash. I'm happy as I have it working at least.
@TimCurtis, maybe something to look at (and thanks for the nice piece of software)
@TimCurtis, maybe something to look at (and thanks for the nice piece of software
)I'm assuming this is the one-stop-shop for Moode support/bug reports as my userID for the Moode forum appears to have been deleted and the site is not open for new registrations..........
Been a very happy trouble-free Moode user for years until the last week, when I encountered two issues:
I am using a Pi 3B on which a test instance of volumio is working just fine.
The current, and last working, Moode Build is the most recent 32 Bit version.
I have tried to login via SSH, but I have no idea what the username and password should be and any suggestions google has provided are not working.
If anyone can help me, I'd be really, really grateful as I much prefer Moode to Volumio and would like to continue using it.
many thanks
Been a very happy trouble-free Moode user for years until the last week, when I encountered two issues:
- I cannot remount network drives after unplanned power outages (of which we have a had a few recently) on both 32 and 64 bit versions.
- I cannot access any configuration tools on a new 64 Bit install created using raspberry pi imager either through the automatic install or using the custom mode and a manually downloaded and unzipped version.
I am using a Pi 3B on which a test instance of volumio is working just fine.
The current, and last working, Moode Build is the most recent 32 Bit version.
I have tried to login via SSH, but I have no idea what the username and password should be and any suggestions google has provided are not working.
If anyone can help me, I'd be really, really grateful as I much prefer Moode to Volumio and would like to continue using it.
many thanks
You need to set a user and password when creating the initial image using the Raspberry Pi Imager.
see the MoOde set-up guide.
https://github.com/moode-player/moode/blob/master/www/setup.txt
and pay attention to..
The OS image does not contain the userid pi, SSH service, WiFi SSID or Access
Point password.
- Use the official Raspberry Pi Imager to choose a moOde OS image, enable SSH,
create the pi userid and password and optionally a WiFi SSID and password.
The moOde OS images are listed in the "Media Player OS" category or if they
were downloaded directly via the Download page at http://moodeaudio.org they
can be selected via the "Use custom" category.
This is a requirement by the RPi Latest release for added security.
https://www.raspberrypi.com/news/raspberry-pi-bullseye-update-april-2022/
You need to reimage your uSD card using the RPi Imager app and follow the instructions to set a user and password.
see the MoOde set-up guide.
https://github.com/moode-player/moode/blob/master/www/setup.txt
and pay attention to..
The OS image does not contain the userid pi, SSH service, WiFi SSID or Access
Point password.
- Use the official Raspberry Pi Imager to choose a moOde OS image, enable SSH,
create the pi userid and password and optionally a WiFi SSID and password.
The moOde OS images are listed in the "Media Player OS" category or if they
were downloaded directly via the Download page at http://moodeaudio.org they
can be selected via the "Use custom" category.
This is a requirement by the RPi Latest release for added security.
https://www.raspberrypi.com/news/raspberry-pi-bullseye-update-april-2022/
You need to reimage your uSD card using the RPi Imager app and follow the instructions to set a user and password.
Hello team,
Hope you can assist,
I am adding Bourns PEC11R rotary encoder volume control to the RPi4 + Pi-DigiAmp+ combination. Using moode audio release 8.3.1
Rotary encoder is connected to pins 14, 16, 18 on the DigiAmp 40 pin connector (middle pin on the encoder to pin 14 (Ground), and side pins on the encoder to pins 16, 18 (GPIO 23,24).
It seems to work, but it's really unreliable, lots of skips, and sometimes the volume setting even goes backwards a couple steps when trying to increase or up when trying to decrease. Sounds like the GPIO pin state changes are not detected consistently. Wondering if I am missing something important - do I need to add a hardware filter (RC chains to the side pins) as per Bourns datasheet?
https://www.farnell.com/datasheets/2360546.pdf
Any help is appreciated.
Cheers,
-Victor
Hope you can assist,
I am adding Bourns PEC11R rotary encoder volume control to the RPi4 + Pi-DigiAmp+ combination. Using moode audio release 8.3.1
Rotary encoder is connected to pins 14, 16, 18 on the DigiAmp 40 pin connector (middle pin on the encoder to pin 14 (Ground), and side pins on the encoder to pins 16, 18 (GPIO 23,24).
It seems to work, but it's really unreliable, lots of skips, and sometimes the volume setting even goes backwards a couple steps when trying to increase or up when trying to decrease. Sounds like the GPIO pin state changes are not detected consistently. Wondering if I am missing something important - do I need to add a hardware filter (RC chains to the side pins) as per Bourns datasheet?
https://www.farnell.com/datasheets/2360546.pdf
Any help is appreciated.
Cheers,
-Victor
Are you using the Audio Config section of the moOde UI, under the "Volume options" section ?
https://moodeaudio.org/forum/showthread.php?tid=5505&highlight=rotary+encoder
https://moodeaudio.org/forum/showthread.php?tid=5505&highlight=rotary+encoder
Yes, rotary encoder is enabled via Volume options. Like I said, it actually works, but a little unpredictable, like I described above. People from Core Electronics (I got the encoder from them) suggested HW filter from the Bourns datasheet. I will try it, but thought potentially someone else on the forum had similar issue...Thanks for your help.