@valdemar wrote:
1) Do the needful — check that you have flac in your transcode codecs, and that you’ve added the full path to wavstreamer and the flac decoder binary in the transcode script. Run the script by hand to make sure it will output data, and cat that into a file and see if it is a valid wav file.
I didn’t know it was needful :-). The Unslung version ran out of the box, if I remember correctly. Anyway, I appreciate you patience. This part is SOLVED.
Aaaaah… clearly I need to add something to the wiki so folks know it’s needful. 🙂
2) Check permissions. If it scanned the rest but not the new ones, it’s likely permissions.
I thought myself it was a permissions problem, but all permissions are the same. Any other ideas?
Hmm… the best way to debug that I think is to do a full scan at debuglevel 9. Then search through the debug log to find each “component” of the path… like “/mnt/m3”, then “/mnt/mp3/new music”, then “/mnt/mp3/new music/from work”, etc and follow the scanning process of a song that doesn’t appear.
If it doesn’t scan it, it will emit *some* kind of error about it. Whether it’s an error about bad permissions, or metadata it doesn’t understand or whatever. Something will be logged.
Someone had a patch to push up the debugging info for failures to scan, and I might do something like that — throw up more visible errors for scan failures on first run only, so that the logs don’t get swamped with stuff, but problematic files are still visible on low debug levels.
— Ron