afriend wrote: 
> May I ask one thing that might help with future troubleshooting: could
> you please include the *file path* in error messages of -Decoder does
> not support file format, code 0-? Since this error won't happen all the
> time it won't clutter the log and still be very helpful in finding those
> files.
Unlikely as that error is LMS noting a report from the player and logged
by the LMS comms protocol module and IIRC doesn't have access to what
created the datastream.  However it should be clear to user the
file/stream that is being played.

> 
> BTW I've looked some more into my AAC/ALAC files and in my scanner log
> there's also a big bunch with the famous "Error: Unable to read at least
> 16 bytes from file (only read xx)." Oddly enough, at least those of them
> I've checked manually do have their metadata properly displayed. They
> are AAC from the iTunes Music Store (either purchased or matched). 
> 
> I have gathered all files who trigger this scanner error message in a
> playlist. Now I would like to have each one of them play for only like 3
> seconds and see if any would also trigger this -Decoder does not support
> file format- error. 
> There are too many to do this manually. Do you know how to automate
> this?

I don't deal with scanner but I know MP4 which I why I picked the
initial problem up.

I've seen this 16 bytes error - I think it is the scanner trying to read
part of a file to determine its type and there isn't enough data - part
of scanning is a bit of guesswork .  If you are really concerned -
create a new thread especially with this topic as it will not be seen if
buried in a different topic such as playback aborting.


------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=110737

_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter

Reply via email to