Print

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

[Denti]

I removed some custom fields from MC and it automatically re-tagged a vast majority of my files. But then I also got an error message like this:

"Media Center encountered errors while tagging or moving files. Check that the files exist, are not read only, and are not in use by other programs"

Then I got a list of files. A long one. No way for me to access this list. I tried copying the info, but it wouldn't let me.

So how can I re-locate these files? I've tried the "bad file" playlist ([Media Type]=[Audio] ~d=b), but this doesn't pull any of them up.

[glynor]

Your Library did that to me a few times when I was playing with it, when I wasn't even tagging anything at all. I think it is something broken in the Global Variable loading logic in one of your Views.

[Denti]

It's not a view issue. It appears to be corrupt files. I found one, tried to play it, and it won't play. Tried it in VLC, too. No go. So if there are several dozen of these, how do I find them?

[JimH]

What file type are they?

[Denti]

FLAC, as are 99% of my collection. The file I found is one track in an album that otherwise plays fine.

[glynor]

I believe the Log stores the files that generate tagging errors.

[Denti]

I believe the Log stores the files that generate tagging errors.

How do I access the log?

[glynor]

http://wiki.jriver.com/index.php/Logging

[Denti]

My logging was not enabled, so I'd have to reproduce the error, which means selecting all my files and performing something (like update Library from tags) to generate the error. I did this with the one file I know is bad, and the log file was massive. I can't image how big it would be after scanning 240k songs!

Is there an easier way to identify these files?

[Denti]

I'm using AudioTester, which seems to identify the files with problems. Not super fast, but better than nothing.

[blgentry]

I did some testing a while ago with a group of mixed files that included a TON of damaged ones.  The majority of the damaged files showed up with a few different tell tale signs:

1.  Duration field that was empty, or a very short duration like 0:05 to 0:30.
2.  Very strange sample rates.
3.  Unusual bit rates.  Usually really big like 8000 or more.

By sorting by these columns in file view and then going to the bottom or top of the list, I was able to weed out something like 95% of the bad files in a just a few big chunks.  I'm not sure if your bad files will show up like this, but I thought I'd mention it.

Oh one big note:  I imported all of these files *knowing* a bunch of them were damaged.  I'm guessing that during the import process JRiver did something that made the durations, and other fields show up with strange values, thus cluing me in that the files were probably bad.

Good luck to you.

Brian.

[glynor]

I did some testing a while ago with a group of mixed files that included a TON of damaged ones.  The majority of the damaged files showed up with a few different tell tale signs:

1.  Duration field that was empty, or a very short duration like 0:05 to 0:30.
2.  Very strange sample rates.
3.  Unusual bit rates.  Usually really big like 8000 or more.

I've always been able to find broken files with these kinds of clues too.

It is annoying that the Tagging Error warning dialog doesn't have a way to copy the contents to the clipboard easily or save the list or something.

[Denti]

It is annoying that the Tagging Error warning dialog doesn't have a way to copy the contents to the clipboard easily or save the list or something.

Yes! That would solve the problem!