Moode Audio Player for Raspberry Pi

null characters in worker.php

Tim:

//sorry I clicked the wrong button and sent this too soon. Now edited//

Did you look closely at this message?

As an aside, my editor was choking on 4 non-ascii characters so I commented them out, seemingly to no effect. Caveat: I'm no php expert and my experience comes from several years ago therefore is likely very outdated.

Code:
//MYEDIT
//sysCmd('ln -s /mnt/NAS /var/lib/mpd/music/NAS^@^@^@');
//sysCmd('ln -s /mnt/SDCARD /var/lib/mpd/music/SDCARD^@');
sysCmd('ln -s /mnt/NAS /var/lib/mpd/music/NAS');
sysCmd('ln -s /mnt/SDCARD /var/lib/mpd/music/SDCARD');

It took me a while to figure out he is talking about the Moode file /var/www/command/worker.php

Out of all the PHP files in /var/www, only this one is identified by the linux file command as file type "data".

Lines 142/143 have apparently spurious null characters preceding the closing right-paren, shown as ^@ in the above. Remove the nulls and the file command says the file type is "PHP script, ASCII text executable" as it should be.

Regards,
Kent
 
Last edited:
Tim:

//sorry I clicked the wrong button and sent this too soon. Now edited//

Did you look closely at this message?



It took me a while to figure out he is talking about the Moode file /var/www/command/worker.php

Out of all the PHP files in /var/www, only this one is identified by the linux file command as file type "data".

Lines 142/143 have apparently spurious null characters preceding the closing right-paren, shown as ^@ in the above. Remove the nulls and the file command says the file type is "PHP script, ASCII text executable" as it should be.

Regards,
Kent

Hi Kent,

I wasn't sure how to interpret that particular post but after reading your analysis and turning on "show invisible characters" in my code editor I see the weirdness. It also shows up in nano editor as ^@.

Practically speaking even if the cmds bombed it shouldn't have any effect since the symlinks are established during the OS build recipe and they persist.

I've removed the odd binary chars from these two lines.

Many thanks for figuring this out 🙂

-Tim
 
Tim:

//sorry I clicked the wrong button and sent this too soon. Now edited//

Did you look closely at this message?



It took me a while to figure out he is talking about the Moode file /var/www/command/worker.php

Out of all the PHP files in /var/www, only this one is identified by the linux file command as file type "data".

Lines 142/143 have apparently spurious null characters preceding the closing right-paren, shown as ^@ in the above. Remove the nulls and the file command says the file type is "PHP script, ASCII text executable" as it should be.

Regards,
Kent

Thanks for elaborating that for me, I kind of figured it was a non-issue but thought I'd let ya'll know anyways. It was annoying me as my editor saw it as "binary" and asked me "are you sure?" every time I went into it.

Chris
 
Thanks for elaborating that for me, I kind of figured it was a non-issue but thought I'd let ya'll know anyways. It was annoying me as my editor saw it as "binary" and asked me "are you sure?" every time I went into it.

Chris

Hi, Chris.

Yeah, obviously this would have been found sooner if it had been causing operational errors. It's been around at least since r25 (perhaps foolishly, I've deleted earlier versions from my local archive) but, thanks to you raising your hand, it's now gone. If only every software developer were as responsive to users as Tim is. Quite remarkable, actually.

Regards,
Kent
 
hello, i have one idea. can you change radio logo dir to same dir as *.pls and displaying logos automaticaly when logo and *.pls have same name 🙂 no gui needed...

Hi,

There really is no way to do this because when a radio station is added to the Playlist MPD does not maintain a reference to the pls file name. The only unique identifier for the station at that point is it's URL and thus a SQL table is needed to maintain a mapping between station url, permalink if any, station name and logo url or path.

-Tim
 
I've mounted my brand new IQaudio Pi-DAC+ on RPi3 with fresh installation of Moode 2.6 TR7 and I was a little bit disappointed. Moode is great and the DAC sounds very well with my Koss Porta Pro connected directly to the DAC but sound quality with default settings was very bad. There was an audible buzzing noise in some tracks (including stereo test provided with Moode) in default software volume control mode. It vanished when I switched to hardware volume control but output volume was very low and I had to use setting about 60 - 70. It was improved by switching logarithmic volume control to yes. Do you have any recommended Moode settings for Pi-DAC+ to get its best?

There is the last problem that was present in all settings and I can't get rid of - unpleasant audible crack when I start playing music or manually skip to different part of a track and some more silent but audible pops in right channel between tracks in a playlist. No popping happens when I push pause/resume button. It could be caused by opening/closing I2S DAC between tracks. Do you have any idea how to get rid of those annoying pops? It could be caused by some kernel settings or MPD since Moode/Pi-DAC+ are not the only one combo with such problems:
Click/Pop/Crack when changing tracks : Raspberry Pi • RuneAudio Forum
https://support.hifiberry.com/hc/en-us/community/posts/201492992-DAC-clicks-between-tracks

Thank you.

Filip
 
I've mounted my brand new IQaudio Pi-DAC+ on RPi3 with fresh installation of Moode 2.6 TR7 and I was a little bit disappointed. Moode is great and the DAC sounds very well with my Koss Porta Pro connected directly to the DAC but sound quality with default settings was very bad. There was an audible buzzing noise in some tracks (including stereo test provided with Moode) in default software volume control mode. It vanished when I switched to hardware volume control but output volume was very low and I had to use setting about 60 - 70. It was improved by switching logarithmic volume control to yes. Do you have any recommended Moode settings for Pi-DAC+ to get its best?

There is the last problem that was present in all settings and I can't get rid of - unpleasant audible crack when I start playing music or manually skip to different part of a track and some more silent but audible pops in right channel between tracks in a playlist. No popping happens when I push pause/resume button. It could be caused by opening/closing I2S DAC between tracks. Do you have any idea how to get rid of those annoying pops? It could be caused by some kernel settings or MPD since Moode/Pi-DAC+ are not the only one combo with such problems:
Click/Pop/Crack when changing tracks : Raspberry Pi • RuneAudio Forum
https://support.hifiberry.com/hc/en-us/community/posts/201492992-DAC-clicks-between-tracks

Thank you.

Filip

Hi Filip,

MPD hardware volume plus Moode logarithmic curve is best for most DAC's with hardware volume controllers otherwise volume output will be low within the 0 - 50% ALSA range. MPD software volume already implements a logarithmic curve so should be plenty of output in 0-50 range.

I think the digital "buzz" that you are hearing when using MPD software volume could be due to bug in the algorithms dithering code. Another user pointed this out a while ago and sent me a set of test files which allowed me to repro the issue. I never noticed it on any of my configs that use software volume control but I could hear it when testing using the perfect silence tracks or when just setting the knob to 1 and turning up the amp. If I get the chance I'll raise an issue in the MPD forum but feel free to do so yourself 🙂 https://forum.musicpd.org

I also was able to repro the audio glitches that u described. I tested on both I2S and USB DAC's which suggests that it's not specific to PCM5122 or I2S interface. They are very subtle to my ear and I don't notice them when listening to a playlist but YMMV due to hearing sensitivity with these types of glitches. I'll have to ask around and see if there is any knowledge or insight on this.

-Tim
 
I'll have to try re-seating the digi+ board, make a fresh install and see if that works.

Alot of people report the dtoverlay to disable bt effective, but it didn't work for me. Would've been better of with a pi2 B+ or whatever the next "best" pi is called than with the pi3 for my purposes I suppose.

Will have a look at the tda1541a dac as well as it was quiet with the SB V3 too after I swapped cables over to test if the Pi3 was the only issue.
But then it was quiet, no white noise either, the last few times I tried with the Pi3 and Digi+...
 
It's playing 🙂

I took the lid of the TDA1541A and swapped the LT1028 opamps that worked well enough in sims to LME49710's.

So, the first part of the problem was the Digi+ config, the second part was that simulations are rarely perfect.

Thanks for all the help!
 
Hi
TR5 is working nicely although there was a minor glitch during setup which didn't occur with TR1, TR2 or TR3

I initially set up TR5 using AP, and when I configured my wireless settings and rebooted I wasn't able to connect via wireless, even by AP. I waited 30 minutes, tried again,then powered off and on and it has subsequently worked fine since.

I have RPi and Hifiberry AMP+

Also Zen FM station just gives quiet white noise but the track title seems to show correctly. This station worked on previous TR releases.

Thanks

Jerry

I've just updated to TR7 and got the same problem during install, and again after powering off and on it came back up fine.

Also, Zen FM still gives quiet static, it did used to work for me on the earlier TRs. All the other stations I've tried are ok.

Everything else working nicely. I have RPi3, Hifiberry AMP+, using hardware volume.
 
I've just updated to TR7 and got the same problem during install, and again after powering off and on it came back up fine.

Also, Zen FM still gives quiet static, it did used to work for me on the earlier TRs. All the other stations I've tried are ok.

Everything else working nicely. I have RPi3, Hifiberry AMP+, using hardware volume.

Zen FM (http://lb.zenfm.be/zenfm.aac) is playing here as I type this.


Regards,
Kent
 
I've just updated to TR7 and got the same problem during install, and again after powering off and on it came back up fine.

Also, Zen FM still gives quiet static, it did used to work for me on the earlier TRs. All the other stations I've tried are ok.

Everything else working nicely. I have RPi3, Hifiberry AMP+, using hardware volume.

Hi Jerry,

Zen is working ok for me right now. I'd suggest pasting the url into iTunes or some other Player and seeing what happens. "http://lb.zenfm.be/zenfm.aac"

Failure to reconnect to Moode using home WiFi SSID after initial reboot from AP mode suggests a client issue possibly a stale DNS resolver cache. In other words maybe the client still had the 172. AP mode address in its DNS cache. Just speculating of course.

-Tim