thanks for the work. this has replaced runeaudio for my home use because you actually update. also, props for including udlna-- i had to add that manually on rune. 🙂
quick *minor* bug report. my setup is interesting as i have an i2s device (iqaudio dac pi-dac+) and a usb output to an external dac (audio-gd nfb-11) that runs my speaker setup. mostly i use the usb out to speakers.
anyway, after updating to 2.7, under configure->mpd->audio device, both devices are labeled "i2s audio device". the setup still works with my USB device, so it appears that this is entirely aesthetic. but it makes swapping between the two slightly more confusing.
anyway, thanks again.
Hi,
NFB-11 is nice 🙂 I've never tested both I2S and USB audio device connected at same time and then switching between the two. I'll have a look at the code.
-Tim
Hello Tim,
I ran the manual update this afternoon, and the kernal went up to 4.4.19-v7+, but the info panel and mpd -V both show mpd at 0.19.15. All aspects of the update ran perfectly to my eye, followed by a hot reboot, and a full power-off shutdown cycle. An mpd database update ran marvelously fast. Happy to run any tests you would like to see.
Skip
I ran the manual update this afternoon, and the kernal went up to 4.4.19-v7+, but the info panel and mpd -V both show mpd at 0.19.15. All aspects of the update ran perfectly to my eye, followed by a hot reboot, and a full power-off shutdown cycle. An mpd database update ran marvelously fast. Happy to run any tests you would like to see.
Skip
Hello Tim,
I ran the manual update this afternoon, and the kernal went up to 4.4.19-v7+, but the info panel and mpd -V both show mpd at 0.19.15. All aspects of the update ran perfectly to my eye, followed by a hot reboot, and a full power-off shutdown cycle. An mpd database update ran marvelously fast. Happy to run any tests you would like to see.
Skip
Hi Skip.
Did u run "CHECK for software update" from System config and then INSTALL ?
-Tim
No. I just ran the commands in your update message. Will I still be in sequence if I run the update via the interface now?
thanks,
Skip
thanks,
Skip
Hi,
NFB-11 is nice 🙂 I've never tested both I2S and USB audio device connected at same time and then switching between the two. I'll have a look at the code.
-Tim
yep, thanks.
just because i forgot to say this explicitly earlier, in 2.6 the devices were correctly enumerated as usb and i2s. so you can probably concentrate your investigation on diffs.
No. I just ran the commands in your update message. Will I still be in sequence if I run the update via the interface now?
thanks,
Skip
Hi Skip,
Yes definately run the in-place update!! This is what will provide the 2.7 code base update plus MPD 0.19.19 🙂
-Tim
yep, thanks.
just because i forgot to say this explicitly earlier, in 2.6 the devices were correctly enumerated as usb and i2s. so you can probably concentrate your investigation on diffs.
Hi,
I'm able to repro and can see where the logic is not designed to handle switching between I2S and USB connected at same time.
Whats the general usage scenario for this?
-Tim
Hi,
im new to moode and have a question.
How can i move the "GENRES" tab to the bottom in the "Library" view or better remove it?
Thanks
puxxi2003
im new to moode and have a question.
How can i move the "GENRES" tab to the bottom in the "Library" view or better remove it?
Thanks
puxxi2003
Tim
Feedback from UK user
pi@moode:~ $ sudo rpi-update 818a860cf690d64c62d3227ad9c36d5867a671c2
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
!!! Failed to download update for rpi-update!
!!! Make sure you have ca-certificates installed and that the time is set correctly
I'll try a full img to an SD card later.
Feedback from UK user
pi@moode:~ $ sudo rpi-update 818a860cf690d64c62d3227ad9c36d5867a671c2
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
!!! Failed to download update for rpi-update!
!!! Make sure you have ca-certificates installed and that the time is set correctly
I'll try a full img to an SD card later.
I ran mine last night. Just went back through the command stack. Same command as yours exactly. It seemed to work fine.
Tim
Feedback from UK user
pi@moode:~ $ sudo rpi-update 818a860cf690d64c62d3227ad9c36d5867a671c2
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
!!! Failed to download update for rpi-update!
!!! Make sure you have ca-certificates installed and that the time is set correctly
I'll try a full img to an SD card later.
I should also say
CHECK for software update
Available
None
Last installed
Package date: 2016-07-28
😕
Also a gentleman MartinT on http://theaudiostandard.net/ has never heard from Tim about Spotify with Moode
Last edited:
I should also say
CHECK for software update
Available
None
Last installed
Package date: 2016-07-28
😕
Also a gentleman MartinT on Home | ???The Audio Standard has never heard from Tim about Spotify with Moode
Hi,
Symptom suggests resetting the updater files is in order.
1) In System config, turn off debug logging if it is on
2) Reboot
3) Try "CHECK for software update" again in System config
If the 2016-08-28 update does not appear under "Available" then perform the steps below and try #3 above again.
1) ssh pi@moode (pwd=raspberry)
2) sudo rm /var/www/update-r26*
Btw, I generally don't check for forum PM's because I already post my email address at moodeaudio.org and welcome user emails 🙂 Please mention to MartinT that he can send me an email with his ? about Spotify.
-Tim
Hi,
Some questions came up so I thought I'd mention there are 2 ways to in-place update Moode 2.6 to Moode 2.7.
First step is to TURN OFF debug logging in System config then reboot, otherwise Moode will be looking for test updates rather than the production update.
Method 1
Bootstrap the in-place updater onto Moode 2.6 and manually run it by following the instructions below. This will also install the UI version of Updater on System config.
Download and install updater.sh via ssh
1) cd ~/
2) sudo wget -q "http://moodeaudio.org/downloads/updater.sh.zip" -O updater.sh.zip
3) sudo unzip -q -o updater.sh.zip
4) sudo mv updater.sh /var/www/command
5) sudo rm updater.sh.zip
Run Updater for first time (can take several minutes to complete). This will install the latest (2016-08-28) software update for Moode 2.6.
1) sudo /var/www/command/updater.sh r26
2) sudo reboot
Method 2
Click "CHECK for software update" in System config and INSTALL the 2016-08-28 update, then reboot.
Final step
Update to Linux kernel 4.4.19 by executing the cmds below from an ssh session.
sudo rpi-update 818a860cf690d64c62d3227ad9c36d5867a671c2
sudo reboot
sudo rm -rf /boot.bak
sudo rm -rf /lib/modules.bak
sudo rm -rf /lib/modules/4.4.8+
sudo rm -rf /lib/modules/4.4.8-v7+
Resetting Updater
If u ever need to reinstall latest software update, reset Updater by running the cmd below, then on System config, "CHECK for software update".
sudo rm /var/www/update*.txt
Regards,
Tim
Some questions came up so I thought I'd mention there are 2 ways to in-place update Moode 2.6 to Moode 2.7.
First step is to TURN OFF debug logging in System config then reboot, otherwise Moode will be looking for test updates rather than the production update.
Method 1
Bootstrap the in-place updater onto Moode 2.6 and manually run it by following the instructions below. This will also install the UI version of Updater on System config.
Download and install updater.sh via ssh
1) cd ~/
2) sudo wget -q "http://moodeaudio.org/downloads/updater.sh.zip" -O updater.sh.zip
3) sudo unzip -q -o updater.sh.zip
4) sudo mv updater.sh /var/www/command
5) sudo rm updater.sh.zip
Run Updater for first time (can take several minutes to complete). This will install the latest (2016-08-28) software update for Moode 2.6.
1) sudo /var/www/command/updater.sh r26
2) sudo reboot
Method 2
Click "CHECK for software update" in System config and INSTALL the 2016-08-28 update, then reboot.
Final step
Update to Linux kernel 4.4.19 by executing the cmds below from an ssh session.
sudo rpi-update 818a860cf690d64c62d3227ad9c36d5867a671c2
sudo reboot
sudo rm -rf /boot.bak
sudo rm -rf /lib/modules.bak
sudo rm -rf /lib/modules/4.4.8+
sudo rm -rf /lib/modules/4.4.8-v7+
Resetting Updater
If u ever need to reinstall latest software update, reset Updater by running the cmd below, then on System config, "CHECK for software update".
sudo rm /var/www/update*.txt
Regards,
Tim
I tried the update, but during the rpi-update I saw messages that my disk was full (I'm using a 16GB microSD card). I cleaned the old modules (last 2 "rm -rf" commands). This was enough to restart the rpi-update. After the reboot I could not see /boot.bak
This is my About Moode contents:
Release: 2.7 2016-08-28 release notes
Update: (None)
Setup guide: setup guide
Coding: Tim Curtis © 2014
License: GPL, Warranty: NONE (see below)
Platform Information
ver: 1.0
Linux kernel: 4.4.19-v7+
Architecture: ARMv7l
MPD version: 0.19.19
Hdwr rev: Pi-3B 1GB
Seems to be in order 🙂.
Next update will possibly again a problem since my root-disk is 92% full.
This is my About Moode contents:
Release: 2.7 2016-08-28 release notes
Update: (None)
Setup guide: setup guide
Coding: Tim Curtis © 2014
License: GPL, Warranty: NONE (see below)
Platform Information
ver: 1.0
Linux kernel: 4.4.19-v7+
Architecture: ARMv7l
MPD version: 0.19.19
Hdwr rev: Pi-3B 1GB
Seems to be in order 🙂.
Next update will possibly again a problem since my root-disk is 92% full.
I tried the update, but during the rpi-update I saw messages that my disk was full (I'm using a 16GB microSD card). I cleaned the old modules (last 2 "rm -rf" commands). This was enough to restart the rpi-update. After the reboot I could not see /boot.bak
...
Next update will possibly again a problem since my root-disk is 92% full.
Just to be clear, you have expanded your SD card storage to fill that 16GB card, right? Just burning the .img file to a uSD card gets you a minimal 1.6GB root file system of which nearly 1.2GB is occupied by MoodeOS1.0 and MoodePlayer. This leaves less than 0.5GB for stuff you add, like music files, and stuff you generate during operation, like log files. The update process gets to work in what little space is left over.
If you have expanded, then I infer you have some 14+GB of music files on yours. In the good old Unix days, we'd use separate partitions for logs, user files, print spools, etc., to avoid accidentally locking up the system by filing the root file system. Hardly anyone does this these days with the humongous disks available. I'm a big fan of using a separate "disk" for music, e.g., a USB drive, a NAS, etc., for music.
Note that you can regain a little space by clearing out the system logs before updating. Look in the Maintenance section of the System Configuration page.
Regards,
Kent
Tim
I wanted to report back on some issues I was having with my system (RPi B, USBDAC Schitt Modi2). Some radio stations refused to load and play, these seemed to be the higher resolution streams like Audiophile. I was using a 2.5 amp Switching PS that I had laying around.
I just received an IFI 5v iPower PS and installed it. Wow, what a difference in sound AND I now can stream the problematical radio stations. I now wonder how many weird problems people are having might be due to crappy power supplies especially with USB DACs. Just thought I'd offer it up. Anyway, great software Tim. I continue to be amazed at your effort.
I wanted to report back on some issues I was having with my system (RPi B, USBDAC Schitt Modi2). Some radio stations refused to load and play, these seemed to be the higher resolution streams like Audiophile. I was using a 2.5 amp Switching PS that I had laying around.
I just received an IFI 5v iPower PS and installed it. Wow, what a difference in sound AND I now can stream the problematical radio stations. I now wonder how many weird problems people are having might be due to crappy power supplies especially with USB DACs. Just thought I'd offer it up. Anyway, great software Tim. I continue to be amazed at your effort.
Has anyone tested crossfeed?
Does it work fine?
When crossfeed is on "Output Stream" pass from 16bit to 32bit....File is 16bit 44 kHz.
Does it work fine?
When crossfeed is on "Output Stream" pass from 16bit to 32bit....File is 16bit 44 kHz.
Last edited:
I have this scenario although it's not problematic for me in the grand scheme of things.
Rpi2b with a Chinese hifiberry clone I2S (coax and optical out to sound system) board attached, however it comes with a pretty attractive case, so when I decided I preferred the sound from my USB hifimediy sabre 9023 device (async USB, headphone, line and digital coax out to sound system) I hit this problem.
I could probably remove I2S support via software. Although both sound sources show up as I2S, you can still select either, although there is no description to differentiate the two.
Also custom chip settings for i2S devices still show on the USB device.
I believe some chips have a software volume boost defined? I wonder if this would carry over to a USB device and wrongly amplify the signal causing distortion.
Probably easier for the end user to disable I2S support than programmatically fix but obv a "fix" would be an enhancement to the the code base
LTF
Rpi2b with a Chinese hifiberry clone I2S (coax and optical out to sound system) board attached, however it comes with a pretty attractive case, so when I decided I preferred the sound from my USB hifimediy sabre 9023 device (async USB, headphone, line and digital coax out to sound system) I hit this problem.
I could probably remove I2S support via software. Although both sound sources show up as I2S, you can still select either, although there is no description to differentiate the two.
Also custom chip settings for i2S devices still show on the USB device.
I believe some chips have a software volume boost defined? I wonder if this would carry over to a USB device and wrongly amplify the signal causing distortion.
Probably easier for the end user to disable I2S support than programmatically fix but obv a "fix" would be an enhancement to the the code base
LTF
Hi,
I'm able to repro and can see where the logic is not designed to handle switching between I2S and USB connected at same time.
Whats the general usage scenario for this?
-Tim
Just to be clear, you have expanded your SD card storage to fill that 16GB card, right? Just burning the .img file to a uSD card gets you a minimal 1.6GB root file system of which nearly 1.2GB is occupied by MoodeOS1.0 and MoodePlayer. This leaves less than 0.5GB for stuff you add, like music files, and stuff you generate during operation, like log files. The update process gets to work in what little space is left over.
If you have expanded, then I infer you have some 14+GB of music files on yours. In the good old Unix days, we'd use separate partitions for logs, user files, print spools, etc., to avoid accidentally locking up the system by filing the root file system. Hardly anyone does this these days with the humongous disks available. I'm a big fan of using a separate "disk" for music, e.g., a USB drive, a NAS, etc., for music.
Note that you can regain a little space by clearing out the system logs before updating. Look in the Maintenance section of the System Configuration page.
Regards,
Kent
You're absolutely right !!! I forgot to expand my root-filesystem !! I re-created the image last week but this step I failed to do 😀
The output of "df" showed me the actual non-expanded size, but I interpreted it wrong. Thanks for pointing this out to me.
This I won't forget anymore from now on .... 😉
- Home
- Source & Line
- PC Based
- Moode Audio Player for Raspberry Pi