Moode Forum
[SOLVED] (9.0.2) moOde always crashes when i try to scan my library - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: [SOLVED] (9.0.2) moOde always crashes when i try to scan my library (/showthread.php?tid=6602)

Pages: 1 2 3


RE: (9.0.2) moOde always crashes when i try to scan my library - Perhaps - 06-15-2024

(06-15-2024, 12:10 PM)Tim Curtis Wrote: I would turn Samba off on the Pi since it's not being used as a file server. You will still be able to connect to your other file servers (PC and the NAS) from the Pi.

If I understand correctly, the issue is:

When PC file server is off MPD automatically removes all database entries when the Pi starts and then adds only the NAS entries but not all of them?

Hi Tim,

right ! And the spinner is running and running ...
Same files and structure only copied to the SSD, without the SSD defined as source Reorg Database
from PC is done in minutes.

I tried a new Moode installation because of the Bump to Linux kernel 6.6.31 (ISO image only),
I have not activated System -> Filesharing -> SMB Samba.

I also tried in Preferences -> Cover Art -> Audio Formats -> All+

... and the prob is still the same, but not on a second Pi (same type)
with Modde 8.3.9. There is all done in minutes.


RE: (9.0.2) moOde always crashes when i try to scan my library - Tim Curtis - 06-15-2024

If your PC and your NAS have the same music files only specify one of them as a Music Source in Library Config.


RE: (9.0.2) moOde always crashes when i try to scan my library - Perhaps - 06-15-2024

(06-15-2024, 01:19 PM)Tim Curtis Wrote: If your PC and your NAS have the same music files only specify one of them as a Music Source in Library Config.

Hi Tim,

this I tried also.
Only with running PC - working.
Only with SSD on USB of FritzBox - Crash.
Used the same settings in Library Config as in Moode 8.3.9

By the way an other appearence:
After a restart of Moode I have to close the Browser Window and open a new one.
Otherwise I get an Alert:
JSON.parse: unexpected end of data at line1 column 1 of JSON date


RE: (9.0.2) moOde always crashes when i try to scan my library - Iacov - 06-15-2024

(06-15-2024, 10:59 AM)Tim Curtis Wrote: You won't be infringing on copyright because any files provided to our project are only used for troubleshooting your specific issues.

It looks like the flac gaming files are broken so no need to provide any of them.
I'd be interested in testing the file with the huge cover.

Files with special characters or punctuation should not be an issue. I have many in my collection. There was an issue poster recently though that files with tags containing URL's can cause problems.

You can get more info by turning on verbose logging in MPD Config but the log will be ginormous.

the large image is one of those damaged flac files
if the flac file is missing duration etc...is it "safe" to delete it or could i somehow repair it?

i found others files as well that hat 7mb embedded cover art (don't know what i was thinking back in those years) but they scanned without issue

i did a complete reinstall again and importing all my files worked, but unfortunately i did a troubleshooting whoopsie
i changed two things at once: i switched from sd card to usb boot and i left the display off for the imports
if the first did help, it would indicate a hardware failure of the older sd card
if the second helped, it could be a RAM issue...once the display has loaded up, the ram usage increases from 150 to 400 mb from the available 900

i have the feeling that the system boot time has become slower, so i might reinstall again with a fresh sd card and will test the display hypothesis


RE: (9.0.2) moOde always crashes when i try to scan my library - Tim Curtis - 06-15-2024

Ok this thread is getting way too messy and confusing for me.

@Iacov, @Perhaps and others. Please each post a separate thread for your Library ssue and list the exact configuration you are running and the exact set of steps needed for me or others to try if possible to reproduce the issue. If these issues can't be reproduced on our end there is little hope for a solution.