Official moOde 7.0.1 support thread

[TheOldPresbyope]

@Alaini93 

No, that's not what I'm saying. I made a conjecture that enabling the local display combined with a large library might cause this issue. Making a run with a large-memory RPi4B would just be a way to test the strength of that conjecture.

However, 8500 tracks is not a large library. It's just 30 percent larger than my test library with which I was unable to reproduce the issue.

As it happens, I've now been able to reproduce the issue on my player, so my conjecture is false. With luck I'll be able to make some headway on the problem this weekend.


And with that, I'm signing off so I can mellow out before the ball drops in NYC. Happy New Year everyone.

Regards,
Kent

[fdealexa]

Hello everybody,
first of all thanks for the wonderfull new version: it is very nice.
I have imported the old user radios (thanks to Kent for the "loadmyradios7") but, unfortunatelly, thanks to new default radios and the new bigger record layout, the exported file (stations.zip) become larger than 90MB.
Would you please so kind to help me to modify the parameters and the import function to solve my problem?
Thanks in advance and best regards,
Francesco

Hi everyone,
sorry for the inconvenience again but, in addition to the above questions, I also noticed that I am no longer able to use the folders in the RADIO folder, probably I'm in trouble but I don't know where.
Would you be kind enough to help me with these matters?
Best regards and thank you very much,
Francesco

The Radio feature currently has a 75MB limit for the size of a stations.zip import. How many stations are you importing?

The new Radio feature is based solely on metadata. There is no support for Folders. You should be able to use the Genre field to group stations.

Thanks for everything, Tim,
in reference to:
First point: I haven't been able to modify the IMPORT function yet. I will follow it.
Second point: I did it, as you suggested, and I'm happy with it: TIP: it could be useful to integrate a new logic of "SORTING AND GROUPING" also using that of a free field as TAG.

NEW POINT:
thanks to the "-u" option of the MOODEUTL utility I discovered some issues and tried to solve them as follows:

Station                                                                     New URL
Kanal K | http://stream.kanalk.ch:80                           http://stream.kanalk.ch
RadioActive FM 88.6 | https://streaming.rad...              http://falcon.shoutca.st:8640
smooth Chill | http://streaming.novaen...                     http://streaming.novaentertainment.com.au/smooth953
UCFM 87.8 - Canberra's Alternative | http://strea...       http://ucfm.out.airtime.pro:8000/ucfm_a

I sincerely hope that this little help will contribute to the continued growth of the moOde project.

Kind regards and many thanks to you and the whole team for dedicating to the project.
Francesco

[Alaini93]

As it happens, I've now been able to reproduce the issue on my player, so my conjecture is false. With luck I'll be able to make some headway on the problem this weekend.


And with that, I'm signing off so I can mellow out before the ball drops in NYC. Happy New Year everyone.

Regards,
Kent

Happy New Year Kent, Best Wishes for 2021.

That's good news, I mean that you can reproduce and will try to fix.

Thanks for all your work and all the "Tim" work for this cool software.

Alain

[pizzaparty]

Hi!

I'm experiencing some weird stuff with this new release: Tracks that played fine now skip every few minutes, sometimes it goes silent for a minute until the song continues (no matter the format or quality, WIFI or LAN). I tried to activate the precaching function (128mb), because that's something I wanted to have for a long time and it broke my install. Twice. (at first I thought it was just a bad SD Card)

Did anyone else have this Problem? And, if it worked properly, would it preload the whole cache before playing or start playing and then fill the cache?

My setup is a Pi3B with an Audiophonics 9038 DAC and I play mostly from my network drive.

Thank you for the great work,

Martin

[AlexTee]

The session id is a static value in cfg_system and thus would always be returned but what I think is happening is the sql query is failing because the database is busy processing an update. It's due to an order of execution issue in worker.php. See the code snippet below.

Code:

// Start watchdog monitor
sysCmd('/var/www/command/watchdog.sh > /dev/null 2>&1 &');
workerLog('worker: Watchdog started');

//
workerLog('worker: Ready');
$result = sdbquery("UPDATE cfg_system SET value='1' WHERE param='wrkready'", $dbh);
//

//
// BEGIN WORKER JOB LOOP
//

The fix would be to start watchdog after the update query for "worker: ready".

If you cold revert your change to watchdog and test this fix I'd be interested in knowing the results.

-Tim

Reverted the watchdog changes, applied only the fix you suggest in worker.php. After reboot I don't observe the errors anymore. So, we can conclude, this fix also works, however, I highly suggest to add another check to watchdog.sh similar to what I've proposed in PR to make an additional session file existence check before ever testing its permissions. Alternatively, rewrite the permission check test to be more rigorous (do not accept empty string). Otherwise there's still a small chance for the test to erroneously evaluate to True, which is something, we want to avoid.

BTW, what is the command (or set of commands) to restart all the Moode related services, to avoid rebooting in case of testing something? moodeutl -r?

[Tim Curtis]

Yes, in most cases moodeutl -r can be used when testing changes instead of rebooting.

Given the root cause of the session permission issue has been identified and fixed, watchdog prolly doesn't need to do the permission check anymore.

[AlexTee]

Yes, in most cases moodeutl -r can be used when testing changes instead of rebooting.

Given the root cause of the session permission issue has been identified and fixed, watchdog prolly doesn't need to do the permission check anymore.

You mean, there is no need to check the session file permissions? Why would that do it before, then? Just curious to know.

[Tim Curtis]

It was done at the time because the cause of the occasional permission issue after reboot was not known. But in fact the test itself was operating under a false assumption that the sql query that returns the sessionid constant would always succeed.

[vmirmow]

After updating to 7.0.1 from 6.7.1 on an Allo USBridge Signature and generating the library from the same folder of music shared from a NAS as before the update Moode now appears to be processing .cue files as folders and interpreting the contents of these files as additional tracks to be included in the library. They show up as 00:00 duration duplicates of the actual .flac tracks in the same album view in some cases and as separate albums as others. Is this intended behavior caused by improper .cue files or tags, or a new bug? Generating a library using 6.7.1 from the same share worked correctly, displaying only the actual audio tracks and not the phantom ones from the .cue files.

[AlexTee]

vmirmow, noticed same behavior.