INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Identifying files previously determined to be bad  (Read 1443 times)

steveoat

  • Recent member
  • *
  • Posts: 7
Identifying files previously determined to be bad
« on: May 03, 2012, 08:25:28 am »
I just ran the import file feature in the Library.

I got the following message: Skipped 5129 files previously determined to be bad.

How do I identify these "bad" files?
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42388
  • Shoes gone again!
Re: Identifying files previously determined to be bad
« Reply #1 on: May 03, 2012, 08:29:20 am »
Welcome.

Hopefully this will help:
http://wiki.jriver.com/index.php/Bad_Files
Logged
Matt Ashland, JRiver Media Center

Vincent Kars

  • Citizen of the Universe
  • *****
  • Posts: 1154
Re: Identifying files previously determined to be bad
« Reply #2 on: May 04, 2012, 07:19:17 am »
THis quenstion has been ask before.

Why don't you add the list of bad files to the import log?
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42388
  • Shoes gone again!
Re: Identifying files previously determined to be bad
« Reply #3 on: May 04, 2012, 10:37:14 am »
Quote from: Vincent Kars on May 04, 2012, 07:19:17 am
THis quenstion has been ask before.

Why don't you add the list of bad files to the import log?

It was added to 143:

17.0.143 (5/1/2012)
Changed: The in-depth summary for an import lists files skipped because they're marked as bad or that have been previously deleted (only a count was shown before).
Logged
Matt Ashland, JRiver Media Center

Vincent Kars

  • Citizen of the Universe
  • *****
  • Posts: 1154
Re: Identifying files previously determined to be bad
« Reply #4 on: May 04, 2012, 12:21:36 pm »
Missed that one.

Thanks
Logged
Pages: [1]   Go Up
« previous next »