Scanning files on external (USB) drive

[dzollman]

I'm seeing some weird behavior when scanning files on an external (USB) drive.

After I scan my external drive, I have a large number of "Failed to add" files. The error shown for each file is "Error scanning file, error while reading file info". After closing the results dialog, many of those files appear in my library. So it appears the errors were false. However, there's no way to tell which files were added to the library and which errors were actually real.

If I move some of the same files to my local hard drive, they are scanned and added successfully with no errors.

As a separate issue, WMA files trigger a scan error and are not added to the library regardless of location. What is the expected behavior for WMA files?

Edit: Forgot to add that this is build 3515 on M1 Mac 15.7.7.

[PetrCBR]

Hi.

There were an issue in format plugin so recheck that in next build please.

Regards, Petr.

[dzollman]

Hi Petr,

Thanks for the response. I checked this in the most recent build (3516) and I'm still getting errors.

I notice something odd in the error log. For many of these files, the error log shows a period and underscore at the start of the filename.

Error scanning file, error while reading file info: /Volumes/Drive/path/to/file/._01 Song Name.flac

The real path on my system is does not have the period and underscore. Example:
/path/to/file/01 Song Name.flac

This is occurring with FLAC and MP3 files.

If the files are moved to the local drive, the errors do not occur.

I also have "Error scanning file, error while reading file info" errors for WMA files, but I'm still not sure if these are expected to work or not. This occurs regardless of drive location.

Last, following up on a previous issue: Previously, if a dialog box was open, clicks on the background window were not registered. This appears to be fixed for most dialogs, but it still occurs for the following dialogs:
- About
- "Column Settings" dialog for Reports > File List
- "Column Settings" dialog for iTunes XML
- Locate Moved/Missing > "Please select one or more files" dialog
- "Check for updates" > current version dialog
- "Update tags" confirmation dialog
I didn't test the rest of the Tools menu.

Hope that's helpful - thanks!

Edit: "Crash when attempting to save file scan error log" is fixed for me!

[PetrCBR]

Hi.

"._01 Song Name.flac" files are made by system (AppleDouble files ... i suppose you have external disc in exFat ?) and they're used to store additional metadata supported by OSX.
WMA format is not currently supported in OSX version.

Regards, Petr.

Hi Petr,

Thanks for the response. I checked this in the most recent build (3516) and I'm still getting errors.

I notice something odd in the error log. For many of these files, the error log shows a period and underscore at the start of the filename.

Error scanning file, error while reading file info: /Volumes/Drive/path/to/file/._01 Song Name.flac

The real path on my system is does not have the period and underscore. Example:
/path/to/file/01 Song Name.flac

This is occurring with FLAC and MP3 files.

If the files are moved to the local drive, the errors do not occur.

I also have "Error scanning file, error while reading file info" errors for WMA files, but I'm still not sure if these are expected to work or not. This occurs regardless of drive location.

Last, following up on a previous issue: Previously, if a dialog box was open, clicks on the background window were not registered. This appears to be fixed for most dialogs, but it still occurs for the following dialogs:
- About
- "Column Settings" dialog for Reports > File List
- "Column Settings" dialog for iTunes XML
- Locate Moved/Missing > "Please select one or more files" dialog
- "Check for updates" > current version dialog
- "Update tags" confirmation dialog
I didn't test the rest of the Tools menu.

Hope that's helpful - thanks!

Edit: "Crash when attempting to save file scan error log" is fixed for me!

[dzollman]

Hi Petr,
Yes, it would appear the drive is ExFAT. However, having thousands of those errors in the scan error log makes it impossible to tell if there are any real problems in the error log. Perhaps MediaMonkey should either ignore these fields, or not throw errors?
Also, I'm not sure if you saw my comments about the issues with dialog boxes. It's still an issue in the 3520 (9-02) build.

Thank you!

[PetrCBR]

Hi.

Both should be fixed in next build.

Regards, Petr.