Hi Robert,
FLAC and ALAC encoders default to using VBR encoding. This is ok since lossless compression is being used.
For Airplay streams, Moode assumes that shairport-sync (Airplay receiver) resamples sources to 16/44.1 that are not already encoded at 16/44.1. Airplay stream is similar to to UPnP stream in that there are are no encodedAT metadata tags thus there is no way to know what rate or type of encoding (lossless, lossy) was used to encode the source.
Audio info screen displays "Encoded at: <blank>" for Airplay streams. This has been changed to "Encoded at: Unknown" in upcoming update.
-Tim
Hi,
Correct. Its same for lossy compression. For example if a CD were ripped using 128 kbps VBR MP3 encoder, the snapshot bitrate that is calculated by MPD during playback would vary and not always = 128 kbps.
Its important to distinguish between bit rate and sample rate. Bit rate is a measure of the level of compression used when encoding a source. Sample rate refers to the bit depth, sample rate and number of channels used to encode a source using Linear PCM encoding (LPCM). For song files that contain the "encodedAT" metadata tags, Moode displays the "sample rate" on Audio info screen as "Encoded at:"
-Tim
Hi Tim,
I'm having an issue with Moode 2.6 on my Raspberry Pi model B (26-pin I/O connector) using a "PiFi" DAC. After power up, only the center column of the playback screen appears. I don't see the list of radio stations on the left or any metadata about the active channel on the right. (Sorry I can't figure out how to post a screenshot here.) If I click on the 'Play' tool, the area inside the top circle (which normally shows the time), briefly flashes "Nan:Nan", then playback starts up and the rest of the GUI is drawn as usual. Things seem OK after that. This happens on the 2.6 release code and also after doing the most current update as of today. However this issue doesn't happen on my Raspberry Pi 2 with a Suptronix X400 card.
I've configured my system to start playback immediately upon power up, but it's not doing that. If I start playing a radio station in the list and restart, the system comes back up with just the center column showing as described above. When I click 'Play', it plays the first radio station in the list, not the one that was playing when I did a restart.
Please let me know if I can provide any further information on this. I've turned on debug logging but don't know where I should be looking for clues. I don't see anything suspicious in /var/log/messages.
Thanks and Best Regards,
- Steve
I'm having an issue with Moode 2.6 on my Raspberry Pi model B (26-pin I/O connector) using a "PiFi" DAC. After power up, only the center column of the playback screen appears. I don't see the list of radio stations on the left or any metadata about the active channel on the right. (Sorry I can't figure out how to post a screenshot here.) If I click on the 'Play' tool, the area inside the top circle (which normally shows the time), briefly flashes "Nan:Nan", then playback starts up and the rest of the GUI is drawn as usual. Things seem OK after that. This happens on the 2.6 release code and also after doing the most current update as of today. However this issue doesn't happen on my Raspberry Pi 2 with a Suptronix X400 card.
I've configured my system to start playback immediately upon power up, but it's not doing that. If I start playing a radio station in the list and restart, the system comes back up with just the center column showing as described above. When I click 'Play', it plays the first radio station in the list, not the one that was playing when I did a restart.
Please let me know if I can provide any further information on this. I've turned on debug logging but don't know where I should be looking for clues. I don't see anything suspicious in /var/log/messages.
Thanks and Best Regards,
- Steve
I am still interested why you think there is a sonic difference between the UPNP version and the Airplay version for the same stream.
I have discovered that my UPNP database is foobar'd so I will send you a couple of files tomorrow night.
Basically I have a track that is a flac with no compression and the same track at maximum compression as I am interested if this is where the difference you are hearing is.
Hi Steve,
I just tested Pi-1B with Autoplay and no issues either after reboot or shutdown + power off/on. The DAC board connected to this Pi is a BerryNOS Red and the code base is Moode 2.6 with the latest update and some new code queued up for the next update. Not exactly same as your config but the type of I2S dac should not matter.
The NaN (Not a Number) condition and odd UI can happen if the Pi is rebooted via ssh instead of from the UI. I'm not exactly sure why this is the case.
To troubleshoot:
1) Menu, Restart, Reboot
2) Close all browser sessions connected to Moode
3) Post the output from ./mlog.sh (Moode startup log) after a reboot completes
Regards,
Tim
Hi Tim @.vceo from twiter here:
Im coming at this a week or so late juming from the upgrade via ssh to the web upgrade.
Forgive me if im wrong but we seem to be missing making the update shell script executable, again sorry if this has been discussed in the interim but heres the instructions:
----
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
>> I added this pre-emptively >> 3A) sudo chmod 0755 updater.sh
4) sudo mv updater.sh /var/www/command
5) sudo rm updater.sh.zip
----
..as the updater.sh didn't have executable permissions... in this instance .tar or .tar.gz would be a musch better option IMHO than zip as permissions carry through, whereas they are lost with .zip (I think).
I cant say this with authority, but if the script was invoked by someone running "sudo bash updater.sh {etc etc}" this would - as is - work ok, however would not work with "sudo ./updater.sh {etc etc}"
Unsure if this is the cause of others problems and might be a red herring but Ive always chmod 0755'd my executable bash scripts
Cheers
Im coming at this a week or so late juming from the upgrade via ssh to the web upgrade.
Forgive me if im wrong but we seem to be missing making the update shell script executable, again sorry if this has been discussed in the interim but heres the instructions:
----
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
>> I added this pre-emptively >> 3A) sudo chmod 0755 updater.sh
4) sudo mv updater.sh /var/www/command
5) sudo rm updater.sh.zip
----
..as the updater.sh didn't have executable permissions... in this instance .tar or .tar.gz would be a musch better option IMHO than zip as permissions carry through, whereas they are lost with .zip (I think).
I cant say this with authority, but if the script was invoked by someone running "sudo bash updater.sh {etc etc}" this would - as is - work ok, however would not work with "sudo ./updater.sh {etc etc}"
Unsure if this is the cause of others problems and might be a red herring but Ive always chmod 0755'd my executable bash scripts
Cheers
Hi,
I tested and "sudo /var/www/command/updater.sh r26" works ok. The file has x permission for its owner which is root. Note that the errors in the test below are harmless and simply a result of the update already having been applied.
Regards,
Tim
pi@moode:~ $ cd ~/
pi@moode:~ $ sudo wget -q "http://moodeaudio.org/downloads/updater.sh.zip" -O updater.sh.zip
pi@moode:~ $ sudo unzip -q -o updater.sh.zip
pi@moode:~ $ sudo mv updater.sh /var/www/command
pi@moode:~ $ sudo rm updater.sh.zip
pi@moode:~ $
pi@moode:~ $ ls -l /var/www/command
total 84
-rwxr-xr-x 1 root root 1549 Jul 4 18:53 index.php
-rwxr-xr-x 1 root root 976 Jul 4 18:53 lcdup.sh
-rwxr-xr-x 1 root root 9914 Jul 4 18:53 moode.php
-rwxr-xr-x 1 root root 3675 Jul 4 18:53 resizefs.sh
-rwxr-xr-x 1 root root 1013 Jul 4 18:53 restart.sh
-rwxr-xr-x 1 root root 1703 Jul 4 18:53 spspost.sh
-rwxr-xr-x 1 root root 1038 Jul 4 18:53 spspre.sh
-rwx------ 1 root root 1078 Jun 17 12:55 updater.sh
-rwxr-xr-x 1 root root 5805 Jul 4 18:53 util.sh
-rwxr-xr-x 1 root root 1476 Jul 4 18:53 watchdog.sh
-rwxr-xr-x 1 root root 26243 Jul 4 18:53 worker.php
pi@moode:~ $
pi@moode:~ $ sudo /var/www/command/updater.sh r26-test
Error: UNIQUE constraint failed: cfg_engine.id
Error: UNIQUE constraint failed: cfg_engine.id
rm: cannot remove ‘/etc/php5/fpm/pool.d/www.conf’: No such file or directory
rm: cannot remove ‘/mnt/SDCARD/SDCARD’: No such file or directory
rm: cannot remove ‘/mnt/NAS/NAS’: No such file or directory
Update installed, REBOOT required
pi@moode:~ $
Hi Tim,
I've only rebooted from the web GUI.
Here's the mlog.sh output (I get the same thing whether I do a powerup or reboot):
Looks reasonable to me. What else can I check?
Best Regards,
- Steve
I've only rebooted from the web GUI.
Here's the mlog.sh output (I get the same thing whether I do a powerup or reboot):
Code:
20160704 150354 worker: Startup
20160704 150400 worker: Host (moode-PiFi1)
20160704 150400 worker: Hdwr (Pi-1B 512MB)
20160704 150400 worker: Arch (armv6l)
20160704 150400 worker: Krnl (4.4.8+)
20160704 150400 worker: OS (moodeOS 1.0)
20160704 150400 worker: Rel (Moode 2.6 2016-06-07)
20160704 150400 worker: MPD (0.19.15)
20160704 150400 worker: Session loaded
20160704 150400 worker: Debug logging (on)
20160704 150400 worker: File check...
20160704 150405 worker: File check ok
20160704 150405 worker: Auto-shuffle deactivated
20160704 150406 worker: USB sources ()
20160704 150407 worker: MPD started
20160704 150408 worker: wlan0 does not exist
20160704 150408 worker: Audio (I2S audio device)
20160704 150408 worker: Audio (HIFI DAC)
20160704 150408 worker: ALSA outputs unmuted
20160704 150408 worker: ALSA mixer name (Digital)
20160704 150408 worker: MPD volume control (software)
20160704 150409 worker: Hdwr volume controller not detected
20160704 150410 worker: Volume level (100) restored
20160704 150410 worker: wlan0 address not assigned
20160704 150410 worker: eth0 exists
20160704 150411 worker: eth0 wait 1 for address
20160704 150412 worker: eth0 wait 2 for address
20160704 150413 worker: eth0 wait 3 for address
20160704 150414 worker: eth0 address not assigned
20160704 150414 worker: NAS sources (none configured)
20160704 150414 worker: MPD consume reset to off
20160704 150414 worker: Autoplay on
20160704 150414 worker: Watchdog started
20160704 150415 worker: End startup
20160704 150415 worker: ReadyLooks reasonable to me. What else can I check?
Best Regards,
- Steve
If the things behave as Tim stated, what I assume, the audible differences must have something to do with different signal handling of the relevant Airplay and respective Upnp apps.
Also possible, that Phone or PC signal handling makes a difference.
With testing your tracks I would not be able to create the same reproduceable circumstances for the reason, that Tidal- streaming wouldn't contribute it's part.
The sound differences are very small, just noticeable on a high quality hifi system. With Bubble-upnp on Phone I hear minimum more 'shrillness' and a hair more boxed sound, also the performance is less 'airy' and a little bit more compact in stage than with Airplay via PC. But please notice, that this differences are very, very subtle and you wouldn't complain about the bubble-phone-performance at all- unless you hear the difference by direct comparison- and as a hifi-neurotic it keeps me restless;-)
Greetingz
I realise this just curious whether the increased processing by mpd is noticeable.
Sent from my P01M using Tapatalk
First but not last: thanks to T.C. for this beautiful audio system!
I'd like add some buttons to the raspberry to change sources of music, play, stop, forward, etc. I think this is possible with a program in python than always is running and verifies the gpio status. This is with a loop like 'While True: ....' This program will runs at startup but if I do that the moode don't respond to moode web.
What can I do?
I'd like add some buttons to the raspberry to change sources of music, play, stop, forward, etc. I think this is possible with a program in python than always is running and verifies the gpio status. This is with a loop like 'While True: ....' This program will runs at startup but if I do that the moode don't respond to moode web.
What can I do?
Hi Steve,
Whats odd in the log is that there is no network connection. Its not a config that I test. All my Pi's have at lease one active network adapter.
What happens when u boot with an Ethernet cable or WiFi adapter connected?
-Tim
20160704 150354 worker: Startup
20160704 150400 worker: Host (moode-PiFi1)
20160704 150400 worker: Hdwr (Pi-1B 512MB)
20160704 150400 worker: Arch (armv6l)
20160704 150400 worker: Krnl (4.4.8+)
20160704 150400 worker: OS (moodeOS 1.0)
20160704 150400 worker: Rel (Moode 2.6 2016-06-07)
20160704 150400 worker: MPD (0.19.15)
20160704 150400 worker: Session loaded
20160704 150400 worker: Debug logging (on)
20160704 150400 worker: File check...
20160704 150405 worker: File check ok
20160704 150405 worker: Auto-shuffle deactivated
20160704 150406 worker: USB sources ()
20160704 150407 worker: MPD started
20160704 150408 worker: wlan0 does not exist
20160704 150408 worker: Audio (I2S audio device)
20160704 150408 worker: Audio (HIFI DAC)
20160704 150408 worker: ALSA outputs unmuted
20160704 150408 worker: ALSA mixer name (Digital)
20160704 150408 worker: MPD volume control (software)
20160704 150409 worker: Hdwr volume controller not detected
20160704 150410 worker: Volume level (100) restored
20160704 150410 worker: wlan0 address not assigned
20160704 150410 worker: eth0 exists
20160704 150411 worker: eth0 wait 1 for address
20160704 150412 worker: eth0 wait 2 for address
20160704 150413 worker: eth0 wait 3 for address
20160704 150414 worker: eth0 address not assigned
20160704 150414 worker: NAS sources (none configured)
20160704 150414 worker: MPD consume reset to off
20160704 150414 worker: Autoplay on
20160704 150414 worker: Watchdog started
20160704 150415 worker: End startup
20160704 150415 worker: Ready
Hi,
What is cpu utilization when Py script is running?
Polling loops need to sleep otherwise the cpu will peg, for example
while true
check something
sleep(1)
-Timsleep(1)
The most likely explanation is fluctuating power drain when differing sources are in use, subtly modulating the power supply to the dac, or RF noise from processor. Wonder if extra shielding helps (of no use if using Wi-Fi)
Phil
how to ssh into the moode raspbery pi to install the new in-place software updater?
People,
Sorry if this is a stupid question, but I have been searching for a few hours without finding a hint of how to actually ssh into the moode machine.
I have downloaded moode r26 and installed it in a raspberry pi 2B and connected it to my network switch and and it is running well, and is connecting to my NAS.
I now want to install the in-place updater software (which is a feature I really want!) and I am trying to ssh into the pi using:
ssh root@192.168.1.28 (the pi's IP on my network)
and it then it asks me for a password and "moode" is rejected as is "moodeaudio" as is "raspberry" and every other password I can think of.
I have taken the sc card out of the pi and checked the machine's /etc/ssh/sshd_config file and it is set to PermitRootLogin without-password
so I do not understand why it is asking me for a password, and every one I try gives me "permission denied".
Any suggestions?
Richard
People,
Sorry if this is a stupid question, but I have been searching for a few hours without finding a hint of how to actually ssh into the moode machine.
I have downloaded moode r26 and installed it in a raspberry pi 2B and connected it to my network switch and and it is running well, and is connecting to my NAS.
I now want to install the in-place updater software (which is a feature I really want!) and I am trying to ssh into the pi using:
ssh root@192.168.1.28 (the pi's IP on my network)
and it then it asks me for a password and "moode" is rejected as is "moodeaudio" as is "raspberry" and every other password I can think of.
I have taken the sc card out of the pi and checked the machine's /etc/ssh/sshd_config file and it is set to PermitRootLogin without-password
so I do not understand why it is asking me for a password, and every one I try gives me "permission denied".
Any suggestions?
Richard
Hi Tim,
I do have an Ethernet cable connected! Eth0 is configured to get a DHCP address, and it does, but it looks like the logger gives up waiting before the address is served. I'll configure eth0 for a static IP address and see if that changes anything.
I have a HDMI monitor attached to the Pi, along with a USB keyboard. I ran mlog.sh after the Pi got to the login prompt, then logged into the console directly (no ssh.) So I didn't initiate any inbound network traffic to the Pi.
Best Regards,
- Steve
I do have an Ethernet cable connected! Eth0 is configured to get a DHCP address, and it does, but it looks like the logger gives up waiting before the address is served. I'll configure eth0 for a static IP address and see if that changes anything.
I have a HDMI monitor attached to the Pi, along with a USB keyboard. I ran mlog.sh after the Pi got to the login prompt, then logged into the console directly (no ssh.) So I didn't initiate any inbound network traffic to the Pi.
Best Regards,
- Steve
Hello Richard,
You can't ssh in as root; you need to be 'pi':
ssh pi@192.168.1.28
The password is 'raspberry.'
After you're in, to issue commands as root you will need to preface them with 'sudo.' Or, you can su to root by doing:
sudo su
Hope this helps,
- Steve
You can't ssh in as root; you need to be 'pi':
ssh pi@192.168.1.28
The password is 'raspberry.'
After you're in, to issue commands as root you will need to preface them with 'sudo.' Or, you can su to root by doing:
sudo su
Hope this helps,
- Steve
