I will try it with PI but then what i thought is that for security if we are having the feature were we do not have a default user id. and Pi would be similar to old one. - please let me know if i am going wrong with my open thought.
Your best bet is to follow the discussions in our Forum at moodeaudio.org, and view the thread about upcoming moOde 8.3.1. The issue of removing the remaining hard coded instances of /home/pi has been posted. Info on registering for the Forum is in the Support section at moodeaudio.org.
Hi,
The ProtoDAC section at http://moodeaudio.org has been added 🙂
Visit the Forum for more information. https://moodeaudio.org/forum/showthread.php?tid=5488&pid=46081#pid46081
The ProtoDAC section at http://moodeaudio.org has been added 🙂
Visit the Forum for more information. https://moodeaudio.org/forum/showthread.php?tid=5488&pid=46081#pid46081
Hi,
moOde 8.3.1 is available for download. Visit the Forum for more information. https://moodeaudio.org/forum/showthread.php?tid=5510&pid=46234#pid46234
moOde 8.3.1 is available for download. Visit the Forum for more information. https://moodeaudio.org/forum/showthread.php?tid=5510&pid=46234#pid46234
Hi,
moOde 8.3.2 bugfix release is in the works. Visit the Forum for more information.
https://moodeaudio.org/forum/showthread.php?tid=5525&pid=46323#pid46323
The fixes mainly address a moOde startup fail on Pi-Zero (arm6) platforms.
moOde 8.3.2 bugfix release is in the works. Visit the Forum for more information.
https://moodeaudio.org/forum/showthread.php?tid=5525&pid=46323#pid46323
The fixes mainly address a moOde startup fail on Pi-Zero (arm6) platforms.
So guys, just for my curiosity, has anyone experienced a lower (way lower) output volume on flac files than in radio ?
This issue is really bothering me, i tried setting anything and then resetting but it doesn't work.
Strangely, the same FLAC files played on my Fiio DAP have an output volume way higher. I don't think it was like this with previous Moode versions, but to tell the truth I don't remeber.
Thank you.
This issue is really bothering me, i tried setting anything and then resetting but it doesn't work.
Strangely, the same FLAC files played on my Fiio DAP have an output volume way higher. I don't think it was like this with previous Moode versions, but to tell the truth I don't remeber.
Thank you.
Hi Tim,
I would like to send a donation, but you use paypal and that's a no-go for me.
Are there alternatives (for the donation, not for moOde 🙂 )?
I would like to send a donation, but you use paypal and that's a no-go for me.
Are there alternatives (for the donation, not for moOde 🙂 )?
EDIT: Solved! I don't know why, normalization was "on"... Turned it off, sounds super again!!!
Thanks for your patience, sorry for bothering you!
Hi,
moOde 8.3.2 is available in the Raspberry Pi Imager, Media Player OS section or as a direct download at http://moodeaudio.org. Visit the Forum for more information https://moodeaudio.org/forum/showthread.php?tid=5526&pid=46330#pid46330
moOde 8.3.2 is available in the Raspberry Pi Imager, Media Player OS section or as a direct download at http://moodeaudio.org. Visit the Forum for more information https://moodeaudio.org/forum/showthread.php?tid=5526&pid=46330#pid46330
It's a little moot, but I'm just curios. I've been trying Moode on a Pi4 I already had which I mounted in my new Okto Dac8 Stereo.
When I first installed it, it was 8.3.0. I normally just run it headless and use BubbleUpnp to stream to it, but the other day I went through the interface and saw that 8.3.2 was available, so initiated the update.
After about 10 minutes, I went in again to check the settings. Everything seemed normal, and I entered CONFIGURE to check the SYSTEM settings. I changed the WiFi to off, and saved it. Then it hung. I tried rebooting, after which I could get in to the CONFIGURE screen, but selecting anything did nothing - Moode would just sit there thinking.
I could close the Configuration screen to get back to the home screen, and could consistently bring up the Configuration screen, but selecting anything would just hang.
Thinking I might have just been a borked update, I manually updated the SD card using Raspberry Imager - note that I chose "Other custom" since I downloaded the actual image to my laptop.
Behavior was the same - I could get into the configuration screen but it would just hang thinking. I tried about 3 or 4 times, and once I could get into the SYSTEM configuration, but once I got out, same thing.
FINALLY, I decided to create a new 8.3.2 SD via the Raspberry Imager's "direct" section (in the Media options), and lo and behold, everything works fine.
Any ideas why this would have been? Note - I did download the most recent version of Imager when I tried creating the SD directly through "other custom OS."
When I first installed it, it was 8.3.0. I normally just run it headless and use BubbleUpnp to stream to it, but the other day I went through the interface and saw that 8.3.2 was available, so initiated the update.
After about 10 minutes, I went in again to check the settings. Everything seemed normal, and I entered CONFIGURE to check the SYSTEM settings. I changed the WiFi to off, and saved it. Then it hung. I tried rebooting, after which I could get in to the CONFIGURE screen, but selecting anything did nothing - Moode would just sit there thinking.
I could close the Configuration screen to get back to the home screen, and could consistently bring up the Configuration screen, but selecting anything would just hang.
Thinking I might have just been a borked update, I manually updated the SD card using Raspberry Imager - note that I chose "Other custom" since I downloaded the actual image to my laptop.
Behavior was the same - I could get into the configuration screen but it would just hang thinking. I tried about 3 or 4 times, and once I could get into the SYSTEM configuration, but once I got out, same thing.
FINALLY, I decided to create a new 8.3.2 SD via the Raspberry Imager's "direct" section (in the Media options), and lo and behold, everything works fine.
Any ideas why this would have been? Note - I did download the most recent version of Imager when I tried creating the SD directly through "other custom OS."
I forgot to mention - yes, I did check the checksum of the downloaded file before I created the SD (for whatever that's worth).
With the firmware update, I also got this behavior of the program. I tried many ways to solve the problem and this problem was solved after writing the bootloader through the Raspberry Imager. After updating the bootloader, I flashed the firmware and the behavior of the program became correct.
I just ran a quick test using the 64-bit download from moodeaudio.org and no issues whatsoever booting up the image written to uSD card using the Pi Imager. An in-place update from 831 to 832 also worked without any issues.
That's the weird part. Auto update and using the custom OS function in Pi Imager (for me, and apparently for @SensoR2x) gave the weird result.
For me, it was multiple tries using both methods (I can't speak for SensoR2x, but I made sure I had the latest version of Imager and made sure the hash was correct before attempting). Only when using Imager's "direct" method through the Media option did it work, and it appears SensoR2x experienced the same (or at least similar) software issue/behavior. I almost resorted to doing a rescue SD before I tried using the direct method.
Also - the problem wasn't in booting up. It appeared to boot up fine all the time. The problem only reared up when trying to change a configuration - specifically for me the SYSTEM and/or NETWORK settings. Sometimes I couldn't even get in to the page, and sometimes I could get into the page, it would appear to change, but when I got out and tried to get back in, I could get into the main configuration page, but clicking on System (for example) would just hang it, but I could always just close the configuration page to get back to the home page.
Another anomaly that was happening, was when I tried to reboot or shutdown through the menu, and it would indicate it was rebooting or shutting down, but it wasn't ACTUALLY going through the process - maybe because the configuration process was still hanging?
For me, it was multiple tries using both methods (I can't speak for SensoR2x, but I made sure I had the latest version of Imager and made sure the hash was correct before attempting). Only when using Imager's "direct" method through the Media option did it work, and it appears SensoR2x experienced the same (or at least similar) software issue/behavior. I almost resorted to doing a rescue SD before I tried using the direct method.
Also - the problem wasn't in booting up. It appeared to boot up fine all the time. The problem only reared up when trying to change a configuration - specifically for me the SYSTEM and/or NETWORK settings. Sometimes I couldn't even get in to the page, and sometimes I could get into the page, it would appear to change, but when I got out and tried to get back in, I could get into the main configuration page, but clicking on System (for example) would just hang it, but I could always just close the configuration page to get back to the home page.
Another anomaly that was happening, was when I tried to reboot or shutdown through the menu, and it would indicate it was rebooting or shutting down, but it wasn't ACTUALLY going through the process - maybe because the configuration process was still hanging?
You could try posting in our Support Forum to see if anyone else has similar symptoms or if a dev is able to repro the issue. I normally only post announcements in this thread.
Be sure to include the startup log from the affected system in your post otherwise troubleshooting is not possible. The log is available via the SSH command moodeutl -l or it can be downloaded from the Logs section of System Config.
The Support page at moodeaudio.org has information on requesting a Forum account.
Be sure to include the startup log from the affected system in your post otherwise troubleshooting is not possible. The log is available via the SSH command moodeutl -l or it can be downloaded from the Logs section of System Config.
The Support page at moodeaudio.org has information on requesting a Forum account.
I'll post there if it comes up in the next update. As stated, it's a moot issue at this time because it's now working after using the direct method so never saved the log (I was just trying to get it working), and I don't want to putz with it at this point because I would have to open up the Okto to get to the Pi/SD card.
I was actually going to post directly in the moode forum, but saw a blip about not allowing new subs so never went further to register, etc. (don't remember what I saw).
I was actually going to post directly in the moode forum, but saw a blip about not allowing new subs so never went further to register, etc. (don't remember what I saw).
I had the same problem. After 3 tries of a fresh install, a few moments without problems, I had to go back to 8.3.0
I was successful only after using Imager's direct method - using Media Player option. When you click that option, Moode 8.3.2 is one of the OS in the list (I don't know if you HAVE to have the latest version of Imager in order for 8.3.2 to be in the list).
When I was having the problems, I contemplated going back to 8.3.0, and using the Custom OS function and downloaded image, created an SD of 8.3.0 with none of the problems/issues, but I decided to give 8.3.2 another shot using the Media Player option, and it worked fine.
When I was having the problems, I contemplated going back to 8.3.0, and using the Custom OS function and downloaded image, created an SD of 8.3.0 with none of the problems/issues, but I decided to give 8.3.2 another shot using the Media Player option, and it worked fine.
I had the exact same problem and even the image direct method in the Raspberry Pi Imager tool failed to solve it, so I tried again using good old Balena Etcher and that very same downloaded image from Moode's repository that had failed previously went off without a hitch, and everything is fine.
So something is up with using that RPi Imager Tool.
So something is up with using that RPi Imager Tool.