+- 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)
(9.0.2) moOde always crashes when i try to scan my library - Iacov - 06-13-2024
hey
i use a pi 3b+ (1gb ram) and it worked flawlessly with moode8
since moode 9 i have the issue that the device crashes when i try to scan my library (via smb)
i first migrated from moode 8 to 9.0.1 but didn't investigate the issue when it happened, as i still had issue with my touchscreen orientation
the orientation-issues are fixed with 9.0.2 but the library-scan-crash is happening again and the device crashes repeatedly
my library is not very large (roughly 6000 files in roughly 1000 folders) and moode 8 didn't have an issue with the library scan
i had a look at htop during the last scan
the image/device froze at 806/907m memory with a load average of 13.85 5.01 2.08
is there a known issue or am i doing something wrong?
i don't know what i might be doing differently than with moode 8
thank you for your help and advice
RE: (9.0.2) moOde always crashes when i try to scan my library - Tim Curtis - 06-13-2024
To troubleshoot try the following
1. Monitor the MPD log
tail -f /var/log/mpd/log
2. Menu, Configure Library
Regenerate the Library database
In the MPD log see if its stopping on a particular file.
RE: (9.0.2) moOde always crashes when i try to scan my library - Iacov - 06-13-2024
(06-13-2024, 06:48 PM)Tim Curtis Wrote: To troubleshoot try the following
1. Monitor the MPD log
tail -f /var/log/mpd/log
2. Menu, Configure Library
Regenerate the Library database
In the MPD log see if its stopping on a particular file.
well i'll be damned...i don't know if it worked because i tailed the log or if i just should have had more patience, but it worked smoothly this time...taking ages, but smoothly
the only thing i'm wondering (and a bit contradicting the "just be patient" theory) is, why my device froze up the last times and even my nas went silent (in terms of, you could hear no hdd acitivity)
i also hat a kernel panic one time after reboot, don't klnow what this is and if it could be related...
for now the scan is finished, but i will reinstall 9.0.2 tomorrow and have a look if it works flawlessly if i'm just patient
thanks for the help, @Tim Curtis!
RE: (9.0.2) moOde always crashes when i try to scan my library - Tim Curtis - 06-14-2024
A kernel panic suggests a hardware issue.
I would also swap in a new, high quality uSD Card.
RE: (9.0.2) moOde always crashes when i try to scan my library - Iacov - 06-14-2024
(06-14-2024, 10:17 AM)Tim Curtis Wrote: A kernel panic suggests a hardware issue.
I would also swap in a new, high quality uSD Card.
it's a sandisk sdhc...hope i get more life than a year out of it xD
i'm still investigating, but i think i have found a culprit...there are hidden .ds_store and "._filename" files in one of my folders
i don't own a mac, but they have come with the original files as i still have the zips from the purchase and they have the files, too
at first i though deleting them would suffice...but the device froze up again...as far as i can tell because it tried to scan the .zip's, too (which unforunately contain the aforementioned files)
i basically have no other choice than to move or delete the zips (i will delete them...because honestly, for what occasion am i keeping them?) but i'm wondering why mpd scans zips :/
will report back if deleting the zips, too, brings a solution
RE: (9.0.2) moOde always crashes when i try to scan my library - Iacov - 06-14-2024
nah, it fails again and again, always in the same folder that contains several sub folders
one error displayed in the latest mpd log says:
ffmpeg/png: chunk too big
ffmpeg/flac: invalid sync code
ffmpeg/flac: invalid frame header
ffmpeg/flac: decode:frame() failed
for the record, these files have not changed since i succesfully catalogued them with moode 8 (even the aforementioned zip and ._ and .ds_store files)
edit: the embedded cover art ist 3200x3200...could that be an issue?
RE: (9.0.2) moOde always crashes when i try to scan my library - steve4star - 06-14-2024
Have you tried dropping a .mpdignore file into the sub folders you want to skip ?
I am away from home, so can’t reference the format.
A search of the forum should tell you what the file spec is.
RE: (9.0.2) moOde always crashes when i try to scan my library - Iacov - 06-14-2024
(06-14-2024, 08:37 PM)steve4star Wrote: Have you tried dropping a .mpdignore file into the sub folders you want to skip ?
I am away from home, so can’t reference the format.
A search of the forum should tell you what the file spec is.
i thought about it, but i want those files actually scanned, they are not albums i want to skip
i'm just wondering why it worked with moode 8.x but not anymore with 9.x :/
if there's something about the files i can fix, i will do it, but still the question would remain why it worked before
RE: (9.0.2) moOde always crashes when i try to scan my library - Nutul - 06-14-2024
Some of your files for sure are wrongly tagged. Refer to the LOG offending lines to identify and fix them.
Then, a 3200 x 3200 pixels album art is indeed unnecessarily big... extract it, resize it to a more acceptable, for instance, 1000x1000 to maintain some high original resolution, and replace the one in the file.
I have a close-to-20K tracks library (well, that's a 1300 single-disc FLACs + CUE, which is slightly different from a 20K single files, although not so much, really, from a MPD-library-scanning POV).
Each of them contains the elementary TAGs (artist, album, date, genre and comment, and the album art at 500x500 pixels in JPG format.
No weird tagging, no errors scanning files, unrecognized pictures etc. etc.
HTH
RE: (9.0.2) moOde always crashes when i try to scan my library - Tim Curtis - 06-14-2024
Zip up one of the files and PM a download link to myself, @TheOldPresbyope and @Nutul and one of us will analyze the file and see if the issue can be reproduced.