Moode Audio Player for Raspberry Pi

When I go to bed, or are not at home during the day, I switch off the whole system with the on/off switch on a 220V power strip. I first shut down the rpi with Moode oof course.
So I would like to activate the speakers only when the whole system is stable. A relay, activated by a gpio pin a couple of seconds after the rpi is booted would be perfect.
 
When I go to bed, or are not at home during the day, I switch off the whole system with the on/off switch on a 220V power strip. I first shut down the rpi with Moode oof course.
So I would like to activate the speakers only when the whole system is stable. A relay, activated by a gpio pin a couple of seconds after the rpi is booted would be perfect.

Hi Ron,

As @philrandal mentioned, the Pi is designed to be an always-on device. It consumes tiny amounts of power and is very robust. Try leaving it on all the time unless a non-switched outlet is not handy.

-Tim
 
When I go to bed, or are not at home during the day, I switch off the whole system with the on/off switch on a 220V power strip. I first shut down the rpi with Moode oof course.
So I would like to activate the speakers only when the whole system is stable. A relay, activated by a gpio pin a couple of seconds after the rpi is booted would be perfect.


I've just done a quick google and found this thread

https://www.raspberrypi.org/forums/viewtopic.php?f=35&t=41457

If you look at the last post by the OP, he/she seems to be able to do what you want (all be it with LMS and not MoOde) so it does seem as though it is possible).

I run MoOde v3.1 on a rpi3 with an Audiophonics dac and I have a power switch to control the on/off.

Good luck with your search

Ronnie
 
Hi Tim,

I just did a test, leaving the RPI on and only switching the preamp and amp on and off.
I still have the turn on thump in my speakers. So I am pretty sure the power amp is the problem.
I can off course make a small time delay circuit with relay (powered by the amplifier PS at turn on) to activate the speakers after the amplifier turns on but since I have the RPI I thought that doing it with a gpio pin would be neat.
And off course thank you all very much for your replies and help.
Ron
 
Hello all,

I am a happily using Moode with an old RPI B, TPA6116 class D amplifier and 6N3 preamp.
Thank you very much, the perfect player for me!
When I power on the system (everything goes ON at the same time) I hear a thump in my speakers. Also when turning off but less loud.
I would like to add a 5V relay controlled by one of the GPIO pins of the raspberry pi to isolate the speakers from the system at startup.
Can somebody tell me how to program Moode so that one pin goes high a couple of seconds after boot up?

I really like Moode and the sound of my system. Works very well!!!
I had a little problem in the beginning and maybe it is good to tell others:
I first tried to use an old power supply from an external Hard Drive (12V + 5V) but I did hear a lot of noise from the RPI in my speakers.
Afterwards, I did try a 19V laptop power supply with a DC/DC converter added (to power de RPI with 5 volts). I still had the same noise in my speakers.
So now I use a separate 19V PS for the amplifier and a separate 5V PS for the RPI. That way, I do not have any unwanted noise in my speakers. Very very silent when ON but without music playing.
Oh, and I did also try it without the 6N3 valve preamp and I must say that I did not hear a great difference. So with or without the preamp, the TPA3116 amplifier sounds great (for me). But since I had the preamp lying around, I added it , nice eye candy :)
So if you know how to configure a GPIO pin in Moode, please let me know as I know close to nothing about programming the RPI.
Thanks
Ron

Did you mean TPA3116? If so, you can set the amp to mute for a few seconds at power on quite simply: TPA3130D2 SDZ & MUTE - Audio Amplifiers Forum - Audio Amplifiers - TI E2E Community
 
Hi,

If you know a little Linux ssh then try the cmd below. its a workaround until I can get an in-place update packaged up. Note that the Boss driver only works in the Adv kernels.

sudo sqlite3 /var/local/www/db/moode-sqlite3.db "update cfg_audiodev set kernel='' where id='1’"

-Tim

An externally hosted image should be here but it was not working when we last tested it.



i reboot and nothing happens...
If you can help me
I'm sorry, I'm a newbie.
 
I see the disadvantage is the new user cannot try it out unless they donate. Someone who hasn't used it before is likely to be attracted to runeaudio or volumio as they are free. Slowly over time the user base will diminish and Tim's motivation to update Moode will similarly diminish.

To avoid this happening, I suggest an older version (eg 3.1 currently) remain available to download for free so people can try it out. Those who want to remain on the cutting edge like most of us here will continue to donate.

Version 3.1 is still available on Sourceforge.
Maybe in the future Tim could consider making a 'lite' version available free of charge (e.g. without HiFi DAC support) but that's up to him. I appreciate the enormous amount of work that goes into the product and understand that he needs to pay his electricity bill :)
 
An externally hosted image should be here but it was not working when we last tested it.



i reboot and nothing happens...
If you can help me
I'm sorry, I'm a newbie.

Hi,

Its the back tick/quote (`) to the right of the 1 that causing the command to bomb.

Here is the string without setting Currier font.

sudo sqlite3 /var/local/www/db/moode-sqlite3.db "update cfg_audiodev set kernel='' where id='1'"

-Tim
 
Need some advice please

Two days ago I installed 3.1 on my RPI Model B and it is working like a dream, but I have some questions and before I get toasted :shy: I am not lazy and have been reading my way through this forum since yesterday. I am half way through, but I need to plan ahead so here are my questions:

My current set up is a Model B via I2s into a DDDAC DAC, BTW Tim the driver has made such a difference to the SQ compared to other players I have tried.

Planned - New RPI 3 with Kali re-clocker into the DDDAC via I2s.

Questions:

1 I'm happy to pay for 3.5 but will it work with the Model B until I get the new hardware?

2. Is the RPI 3 Wlan OK or is it to be avoided?

3. All my music is FLAC 16bit 44.1 Khz at present. Is there any advantage to upsampling it when playing?

4. NAS is a micro server running Vortexbox software (linux) and LMS. I'm accessing it via the RPI over Homeplugs. Is there a better or more practical solution to this set up or would I be better putting it all on a USB drive and connecting it to the RPI directly?

5. When I get 3.5 do I do a complete new install via a different SD card?

I appreciate any help at this stage as I am about to purchase the hardware to finish the DDDAC and get it in a case before a Decree Nisi is issued ;)

TIA.
 
Kali Micro skipping

Firstly Cracking job well done Tim.

My Build consists of Rpi3B, moode 3.5, Kali reclocker and IQaudio Pro driving two home designed and built 120watt class A mono blocks in dual differential mode (this is why i went for the iquadio pro dac).

Sound is simply awsome. however if i switch on any upsampling or use either advanced kernels the I get a very intermittent micro skip forwards about every 5 mins or so. this also happened with version 3.1.

I also note that with V3.5 the DAC output is now significantly higher than V3.1

on V3.1 my normal volume level was around 65. on V3.5 its now around 27.

Any Ideas ?..

Chris
 
1) mine works fine on a v2.0 model b, not tested on a v1 model b, I think the i2s pinout is different but certainly working on v2.0 model b

2) cannot comment

3) from my understanding, there is no benefit in resampling, the exception might be if you are applying digital effects where applying it at a higher sample rate might theoretically sound better. I assume the different is negligible however

4) either / or, if the bandwidth of the NAS solution is adequate then it's up to you to decide if migrating to a fixed USB drive would bring benefits in terms of convenience

5) yes new install i.e. No upgrade mechanism from 3.1.. as you allude
To it would be sensible to use a different SD card as you can always fall
Back to 3.1 if you experience problems (there are a couple of regressions/bug fixes that tim has noted in 3.5, I would imagine a bug fix release to that is in the works, hopefully via the upgrade mechanism


LTF


Two days ago I installed 3.1 on my RPI Model B and it is working like a dream, but I have some questions and before I get toasted :shy: I am not lazy and have been reading my way through this forum since yesterday. I am half way through, but I need to plan ahead so here are my questions:

My current set up is a Model B via I2s into a DDDAC DAC, BTW Tim the driver has made such a difference to the SQ compared to other players I have tried.

Planned - New RPI 3 with Kali re-clocker into the DDDAC via I2s.

Questions:

1 I'm happy to pay for 3.5 but will it work with the Model B until I get the new hardware?

2. Is the RPI 3 Wlan OK or is it to be avoided?

3. All my music is FLAC 16bit 44.1 Khz at present. Is there any advantage to upsampling it when playing?

4. NAS is a micro server running Vortexbox software (linux) and LMS. I'm accessing it via the RPI over Homeplugs. Is there a better or more practical solution to this set up or would I be better putting it all on a USB drive and connecting it to the RPI directly?

5. When I get 3.5 do I do a complete new install via a different SD card?

I appreciate any help at this stage as I am about to purchase the hardware to finish the DDDAC and get it in a case before a Decree Nisi is issued ;)

TIA.
 
Firstly Cracking job well done Tim.

My Build consists of Rpi3B, moode 3.5, Kali reclocker and IQaudio Pro driving two home designed and built 120watt class A mono blocks in dual differential mode (this is why i went for the iquadio pro dac).

Sound is simply awsome. however if i switch on any upsampling or use either advanced kernels the I get a very intermittent micro skip forwards about every 5 mins or so. this also happened with version 3.1.

I also note that with V3.5 the DAC output is now significantly higher than V3.1

on V3.1 my normal volume level was around 65. on V3.5 its now around 27.

Any Ideas ?..

Chris

Hi Chris,

Could be the re-clocker? What version of the board do you have? I noticed in another forum that there have been revisions to the board and firmware.

Volume implementation has changed dramatically between Moode 3.1 and 3.5 due to MPD 0.20 series used in 3.5 implementing logarithmic volume curve internally. This meant that no longer a need to due to curving outside of MPD although Alan Finnie's curve algorithm was working perfectly.

In Moode 3.1 did you have Logarithmic curve enabled (Customize screen)?

-Tim
 
Last edited: