Moode Audio Player for Raspberry Pi

Hi Bryce,

I see that the Python script needs to perform the text scroll. I thought the LCD firmware did this asynchronously after initializing some sort of scroll bit.

I'm not exactly sure what happens when the LCD update engine runs the script again while its still tied up in one of the scrolling loops.

In any case, since the script itself has to do the text scroll loops the only way it can work with LCD update engine is if the the text scroll loops happen asynchronously via separate threads or via a separate text-scroll-daemon that the main Python script sends text to via a pipe or socket.

Another option is to not use LCD update engine and instead run a polling loop in the Python script.

Btw, in your script you can get play/pause by parsing out 'state' from currentsong.txt file.

-Tim
Thanks for the tip regarding the 'state' in the currentsong.txt file.

I will look into your other suggestions.

Cheers, Bryce.
 
Hi @mhouston,

The only drawback to storing music on SD card is if a future moOde release is whole-image only which wipes the SD card. In this case u would need to reload the SD card with your music files.

U might want to check out one of the super small 128GB USB sticks for example
Amazon.com: SanDisk Ultra Fit 128GB USB 3.0 Flash Drive (SDCZ43-128G-G46): Electronics

-Tim


Mate, I have 128GB and 256GB by the ton. These days on two compact 2T drives powered by a USB 3 powered hub. Thanks for the "write-over" warning though. Easy enough to recopy via the network for visiting days.
 
Hi all,
I tried to make an update from 3.8.3 to 3.8.4 from within the moode software. I gave a few minutes and rebootet moode still says 3.8.3 is running with mpd 20.9. A new check for an update says now the system is up to date.
I assume updateing via website just deletes my library which is no problem...
But does anyone know what causes this update error?
Regards
Heiner
 
Tim, is there a command that will update currentsong.txt on demand ? without restarting or affecting audio ?

Usage would be assigning a remote button in Lirc to trigger currentsong.txt refresh so that caused the lcd display to update and thus it scrolls for reading the full text.

Useful when checking station and now playing for webstreams ;-)
 
Hi, I updated to the latest version 3.8.4. After turning on glb_mlck to activate the Kali re-clocker and changing some other configurations, I lost sound OUT again. I tried to change volume settings in MDP (hardware, software, disabled), checked the volume setting in Playback, installed Standard Kernel again, rebooted Airplay, tried to play directly from MPD, etc. but still cannot get any sound.

Data is streaming, as indicated by the LED's on the DAC but no sound :confused:

I'm not sure when exactly the sound was lost but I think it was just after resetting the Bit Depth / Sample Rate of the Airplay renderer back to 16/44.1. Funny thing is that there is no sound either while streaming directly from a radio station (not over AP).

Greets
 
Advanced kernels no longer work

Hi Ken

With version Moode = Release 3.7, 2017-05-25 and moodeOS = Version 2.0 multi-kernel
And some of the clarifications provided by you, I was able to install the DAC DDDAC1794 NOS in I2S with KERNEL 4.4.39-rt59-moode2 + and got excellent results, Attached the txt file "S Y S T E M P A R A M E T E R S".

With later versions including 3.8.4, I could not install one of two special kernels while the default kernel works.
When I insert a special kernel, with the same settings as version 3.7, I crash the Playback page and I do not get audio output.
For now I use Release 3.7.
What should I do to find out what's not working, do I need a different setting?

Also, as you do to erase all the tracks at one time, log on the Playback page, without having to do one at a time.

Thank you for your work.

My greetings
Jon
 

Attachments

  • System Parameters.txt
    5.4 KB · Views: 71
Tim, is there a command that will update currentsong.txt on demand ? without restarting or affecting audio ?

Usage would be assigning a remote button in Lirc to trigger currentsong.txt refresh so that caused the lcd display to update and thus it scrolls for reading the full text.

Useful when checking station and now playing for webstreams ;-)

Hi Bob,

You could try sudo touch /var/local/www/currentsong.txt

-Tim
 
Hi, I updated to the latest version 3.8.4. After turning on glb_mlck to activate the Kali re-clocker and changing some other configurations, I lost sound OUT again. I tried to change volume settings in MDP (hardware, software, disabled), checked the volume setting in Playback, installed Standard Kernel again, rebooted Airplay, tried to play directly from MPD, etc. but still cannot get any sound.

Data is streaming, as indicated by the LED's on the DAC but no sound :confused:

I'm not sure when exactly the sound was lost but I think it was just after resetting the Bit Depth / Sample Rate of the Airplay renderer back to 16/44.1. Funny thing is that there is no sound either while streaming directly from a radio station (not over AP).

Greets

Hi,

Very odd. Email me the output from System info and I'll take a look.

-Tim
 
Hi Ken

With version Moode = Release 3.7, 2017-05-25 and moodeOS = Version 2.0 multi-kernel
And some of the clarifications provided by you, I was able to install the DAC DDDAC1794 NOS in I2S with KERNEL 4.4.39-rt59-moode2 + and got excellent results, Attached the txt file "S Y S T E M P A R A M E T E R S".

With later versions including 3.8.4, I could not install one of two special kernels while the default kernel works.
When I insert a special kernel, with the same settings as version 3.7, I crash the Playback page and I do not get audio output.
For now I use Release 3.7.
What should I do to find out what's not working, do I need a different setting?

Also, as you do to erase all the tracks at one time, log on the Playback page, without having to do one at a time.

Thank you for your work.

My greetings
Jon

Hi Jon,

The symptom "insert a special kernel, with the same settings as version 3.7, I crash the Playback page" suggests something external to moOde software for example a bad or corrupt SD card, etc.

You can erase blocks of tracks or the all the tracks on the Playback panel by clicking the item menu then "Remove item(s)". Use the >> buttons to set the beginning and ending track numbers.

-Tim
 
Since version 3.8* i have some low volume digital clicks between tracks from the same album. FS or bitdepth is the same. I am using Pi3 with Hifiberry Dac+ pro. Tried LL and RT kernels and different software upsampling options, but the digital clicks are stille there.
Any hint ?
 
Hi @sinski,

Is it just one particular album?
Do the audio glitches occur during playback or only when transitioning from one track to the next?

-Tim

audio glitch appears on 16/44 files between tracks, when playing files from one folder or playlist. It also appears when transitioning to the next track. There is no glitch between tracks on 24/* material. strange.
 
A nice piece of kit

I got tired of using old computers as my NAS and didn't really want to use an RPi or other SBC with an external USB2 drive. Then I saw the new Odroid-HC1 (here in the USA, at ameridroid.com) and couldn't resist.

My order arrived this afternoon. Here's a snap of it + a 250GB SATA SSD sitting on a 2CD case to give you a sense of scale. I set mine up with Open Media Vault on Debian 8 but it can run a fair variety of distros.

Fast, compact, reasonable power (I bought a 5v/4a supply at the same time); Ethernet only but that's what I wanted. I'm not sure where I want it to end up so I'm not worrying about an enclosure yet.
 

Attachments

  • Odroid-HC1.jpg
    Odroid-HC1.jpg
    110.3 KB · Views: 265
in squeezelite audio glitches where sometimes caused by to small in/out buffers. How can i change the in/out buffer for mpd ?
With my USB I2S DIY DAC I get a muted click between tracks. Was worse on Rune and Vol. but it really doesn't bother me. If I go from 24/96 files to DSD64 files there is a more pronounced click. Once more I'm happy to ignore it.