Congratulations Tim!
Hi Tim, Ive just noticed this forum now has well over a million posts! I think that shows just how much we all value your amazing product, so thanks for working so hard to make Moode one of the best bargains out there. Here's to the next million posts! Regards Adrian
Hi Tim, Ive just noticed this forum now has well over a million posts! I think that shows just how much we all value your amazing product, so thanks for working so hard to make Moode one of the best bargains out there. Here's to the next million posts! Regards Adrian
Hi Mike,
MPD does it internally starting with 0.20.1 so no need for Moode code to do this.
-Tim
I am very pleased to see that amp power control might be coming into Moode. I have been wondering what to do about that (remote control plug sockets seem a trifle inelegant).
I have a suggestion (offered in complete ignorance of how coding works - ask me about clocks and I might be able to help). Could the amp be woken on detection of user activity in Moode, i.e. pre-empting actual playback, to give the amp a few seconds to get out of bed before playback starts?
That's great. Thanks.
One other question - how is date and time handled? I just updated to an advanced kernel and the System Info shows a different date and time from current.
As at right now, the date and time show 2017-04-26 01:19:31, some time ago...
Last edited:
That's what I thought, but four hours later and it's still showing the incorrect date and time.
I can ping the ntp servers in ntp conf, and restarting ntp doesn't seem to make any difference:
Code:
Current default time zone: 'Pacific/Auckland'
Local time is now: Wed Apr 26 03:28:48 NZST 2017.
Universal Time is now: Tue Apr 25 15:28:48 UTC 2017.
pi@moode:~ $ date
Wed 26 Apr 03:30:12 NZST 2017
pi@moode:~ $ sudo restart ntpd
sudo: restart: command not found
pi@moode:~ $ sudo start ntpd
sudo: start: command not found
pi@moode:~ $ sudo /etc/init.d/ntp stop
[ ok ] Stopping ntp (via systemctl): ntp.service.
pi@moode:~ $ sudo ntpd -qg
pi@moode:~ $ sudo /etc/init.d/ntp start
[ ok ] Starting ntp (via systemctl): ntp.service.
pi@moode:~ $ date
Wed 26 Apr 03:32:42 NZST 2017Hardware Volume Control
Hi Tim, im in the process of designing a DAC PCB using the pcm5242. what is the mechanism that you use for the hardware volume control option on moode , do you send the commands over i2s or use i2c or can this still work with the dac in hardware mode.
Been using moode for a good 9 months now, registered and all 🙂. what a cracking bit of software 😉
Chris
Hi Tim, im in the process of designing a DAC PCB using the pcm5242. what is the mechanism that you use for the hardware volume control option on moode , do you send the commands over i2s or use i2c or can this still work with the dac in hardware mode.
Been using moode for a good 9 months now, registered and all 🙂. what a cracking bit of software 😉
Chris
Hi Tim. I've got a question. Yesterday I bought the product key for moodeaudio. I installed it on my raspberry 2 model b.
I didn't have got a wired ethernet connection and pluged in a edimax wlan stick. So after booting i got the accesspoint and was able to configure everything. After a while i changed the wlan configuration to bring the device in the home network. So after reboot i'm not able to connect to this device.
I see in my router that this device (Moode) is connected in my home network but it is not reachable. So i'm not able to get the html site neither with the ip nor the moode.local.
Do you have any tips what i can do or is there any kind of problem with the moode?
Thanks a lot & best regards
Stefan
I didn't have got a wired ethernet connection and pluged in a edimax wlan stick. So after booting i got the accesspoint and was able to configure everything. After a while i changed the wlan configuration to bring the device in the home network. So after reboot i'm not able to connect to this device.
I see in my router that this device (Moode) is connected in my home network but it is not reachable. So i'm not able to get the html site neither with the ip nor the moode.local.
Do you have any tips what i can do or is there any kind of problem with the moode?
Thanks a lot & best regards
Stefan
Hi,
Thun off WiFi of your notebook or mobile phone(not your router), then turn on WiFi. Your moOde back again.
Eric
Hi.
I've change my old rpi B+ to brand new Rpi3. No more clicks or pops or any other problems with advanced kernel. I'm using now advanced kernel with rr scheduler and on demand CPU governor.
Wysłane z mojego 2014811 przy użyciu Tapatalka
Yes I also tried it with the ip adress.
@belt250: Only that I'm understand it correctly. Turn off all the wlan on all the devices in the area and then restart the Moode Player?
I will try it and report it tomorrow.
Thanks a lot & best regards
Stefan
@belt250: Only that I'm understand it correctly. Turn off all the wlan on all the devices in the area and then restart the Moode Player?
I will try it and report it tomorrow.
Thanks a lot & best regards
Stefan
Stefan,
No, if your notebook(or mobile phone) can't connect to Moode player, just turn off notebook's wifi then turn it on again. that's all. You don't need to restart moOde Player.
Eric
Eric,
okay got it.
I will give you a feedback tomorrow
Thanks a lot for your help
best regards stefan
okay got it.
I will give you a feedback tomorrow
Thanks a lot for your help
best regards stefan
Hi Chris,
Sounds like a really cool project 🙂
Moode does several things to enable Hardware volume, they all take place at the application layer as opposed to the device driver layer (I2S, I2C interface).
1) at boot time, run an alsa command and parse its output to determine whether the audio device has a hardware volume controller.
2) if #1 above is yes, then offer "Hardware" as a selection in the Volume control dropdown on MPD config screen
3) If "Hardware" is selected then add a Mixer section to the audio_output blocks in MPD config file to enable MPD volume to control the devices hardware volume controller.
The actual volume commands that are sent to the audio device are handled by the ALSA and I2S driver layers. Moode just sends MPD setvol commands.
I think you would need to get your board to work with one of the existing PCM5xxx I2S driver overlays for example iqaudio-dacplus and then hardware volume would be possible.
-Tim
How about the JustBoom's ?
They have similar Digital Amp HAT for RPI and Zero, have you tried it?
-kitamura_design
Hi Tim, thanks for the quick response. I've already got an iqaudio dac pro working ontop of a pi3 with loads of extra caps tagged onto of it. the improvement in sound is immense hence me going the whole hog. My PCB is now 80% designed and includes onboard multirail PSU regulation, header for pi zero w , header for kali reclocker and the PCM5242 on my board along with dual PSU Dual amp headphone amp. outputs are XLR. I also have a CPLD chip onboard for i2s input switching from either the pi or an xmos usb to i2S board. this is the hardest project I've taken on so far by a long shot. the last one being to 120watt class A monoblock power amps (That one took me a year and is still ongoing) these are destined for my dac to drive instead of my lashed up Pi3.
Will the i2S volume commands still work if I put the dac into hardware mode (this is the simplest for me to implement I think) although I may well implement I2C as well for future learning.
Chris😀