7.3 release: Scanner warnings, should show involved audiofile

[Moonbase]

On rescans, I keep getting some warnings (with the 2008-12-03 nightly as well as with 7.3 release version):

[08-12-12 23:15:35.5088] MP3::Info::_grab_int_16 (2154) Warning: substr outside of string at /<C:\PROGRA~1\SQUEEZ~1\server\scanner.exe>MP3/Info.pm line 2154, <$fh> line 1.
[08-12-12 23:15:35.5405] MP3::Info::_parse_v2tag (721) Warning: Use of uninitialized value in substr at /<C:\PROGRA~1\SQUEEZ~1\server\scanner.exe>MP3/Info.pm line 721, <$fh> line 1.
[08-12-12 23:15:35.5421] MP3::Info::_parse_v2tag (721) Warning: Use of uninitialized value in substr at /<C:\PROGRA~1\SQUEEZ~1\server\scanner.exe>MP3/Info.pm line 721, <$fh> line 1.
[08-12-12 23:41:51.5602] MP3::Info::_grab_int_16 (2154) Warning: substr outside of string at /<C:\PROGRA~1\SQUEEZ~1\server\scanner.exe>MP3/Info.pm line 2154, <$fh> line 1.

I assume these might be due to defective tags. It would greatly help pinpointing the problem if the path and filename of the involved audio file would be shown in the scanner log as well.

[Wirrunna]

It would greatly help pinpointing the problem if the path and filename of the involved audio file would be shown in the scanner log as well.

I agree completely, it's basic programming technique to identify the data that caused the warning/error (well it used to be when I was cutting code in assembler 40 odd years ago!)

Have you tried the different logging options ?
Settings/Advanced/Logging/(Scan) then pick from Error/Warn/Info/Debug

One of these options once gave me the path and filename. I'll investigate more, only takes 3 minutes for a clear & rescan on my test system with 1200 tracks.

Edit: Just loaded SC 7.3 and after first scan get thousands of these informative messages :
[08-12-13 15:37:39.9782] MP4::Info:arse_file (390) Warning: Argument "\x{0}" isn't numeric in numeric eq (==) at /<C:\PROGRA~1\SQUEEZ~1\server\scanner.exe>MP4/Info.pm line 390.
[08-12-13 15:37:40.0143] MP4::Info:arse_file (390) Warning: Argument "\x{0}" isn't numeric in numeric eq (==) at /<C:\PROGRA~1\SQUEEZ~1\server\scanner.exe>MP4/Info.pm line 390.
[08-12-13 15:37:40.0500] MP4::Info:arse_file (390) Warning: Argument "\x{0}" isn't numeric in numeric eq (==) at /<C:\PROGRA~1\SQUEEZ~1\server\scanner.exe>MP4/Info.pm line 390.

2nd Edit: Tried with Settings/Advanced/Logging/(Scan),(Scan.Import) and (Scan.Scanner) set to Error, Warn, Info, Debug - still same messages without path & filename.

Is this a bug or is there some other setting that turns on full error reporting ?

[Millwood]

AFAIK, its been this way forever. I once hacked an extra message into the scanner to find a bad audio file - but its been a long time so you'll have to reinvent the hack yourself.

[JJZolx]

I assume these might be due to defective tags. It would greatly help pinpointing the problem if the path and filename of the involved audio file would be shown in the scanner log as well.

Try increasing the logging level for scanning. Do this at Settings > Advanced > Logging and set scan.import. I'm not positive which level it would require - either INFO (more information than WARN) or DEBUG (most information) - but I'm pretty certain that eventually it will record the path and name of the file being scanned.

[Philip Meyer]

I've fallen for this several times myself.

In the past, some files/tags have caused the scanner to crash, and it doesn't report the file that caused the crash, so you then have to turn the logging level up and run the scan again to find out the file it was processing. When scans can take 30 mins to run before crashing, that's a little annoying.

Depending where the crash occurs, you may get info on the file that was being processed, but once I only got the last scanned filename, and had to guess what the next file to be scanned was! (actually, I used a SysInternals Process Monitor tool to monitor file access).

I think any error/crash message in the scanner should report the track url at error logging level.

Warning messages should report the track url too.

[JJZolx]

Now that 7.3 has some type degree of log rotation, it might make sense to just increase the logging level of the scanning process to INFO.

[Wirrunna]

Now that 7.3 has some type degree of log rotation, it might make sense to just increase the logging level of the scanning process to INFO.

Agree, but I could not get the 7.3 log to show the path and filename with any setting, see my edited post above.

[Wirrunna]

7.3.3 has dramatically improved the logging in the scanner.
In my system the useless error messages have disappeared and now the few remaining errors give file details of the track causing the error and details of the error so you can easily fix the track in MP3Tag.
Well done.