Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Vocalpoint]

"Skipped 1 file previously determined to be bad."

Just saw this for the first time on my first "manual" import of some new tracks this morning using 16.0.178.

MC does not list the file that is "bad"... can I somehow find out what it might be so I can check it?

Cheers,

VP

[Matt]

Create a smartlist: ~d=b

You can Library Tools > Update Library From Tags to reanalyze a file and move it out of the bad location if analysis succeeds.

[Vocalpoint]

Create a smartlist: ~d=b

You can Library Tools > Update Library From Tags to reanalyze a file and move it out of the bad location if analysis succeeds.

Where (what field) do I place ~d=b within the Smartlist?

VP

[Matt]

Add a smartlist (F9) > Import / Export > ~d=b > OK > OK

[Vocalpoint]

Add a smartlist (F9) > Import / Export > ~d=b > OK > OK

Worked great.

EDIT: Even more troubling is that MC sees this file (a flac file) as "bad" yet - it plays fine in MC. Tags are fine...I am a bit confused on what it's seeing as "bad".
EDIT 2: I copied the entire album (11 tracks) to my local drive and completely deleted the enter from the MC db. Then I recopied the album (via Explorer) back out to my music share and rescanned the library - MC added all 11 tracks correctly - and it not reporting any files as bad. Gremlins? Oh well...it's all good now.

Request: Please consider listing any bad files right on that dialog (along with what exactly MC is determining to be "bad") that appears after Run Auto Import now is pressed.

Would be of much more value to instantly see and deal with bad files quickly and efficiently.

Cheers,

VP

[BryanC]

You might want to check your disk health. Weird file errors like that are usually the beginning of the end.

[Vocalpoint]

You might want to check your disk health. Weird file errors like that are usually the beginning of the end.

Doubt it. These drives are enterprise class and reside on a dedicated Windows Server - and all my server logs are indicating nothing critical, no errors and no warnings of any kind.

Out of 50000 tracks - MC was reporting a mysterious "problem" with just this one single file. If it was a server disk problem - I am sure I would see much more than a single file giving me the stink eye and the server would be barking out all kinds of warnings.

Nope - I am leaning toward MC and some sort of "false positive" from whatever it's using to determine a file is "bad". When I copied the problem file locally - MC was able to read it's tags and play it just fine. On the server tho - it wouldn't even catalog or include the copy of this file in it's db. And then when I recopied the entire album back to the server (after deleting the entire old copy)...it read all files - including the problem one just fine.

VP