Quality is not reading correctly when adding existing series

Lets use a concrete example, in this release name, what is the qualities of these releases?

  1. Parks.and.Recreation.S01E01.HDTV.XviD-LOL
  2. Parks.and.Recreation.S01E01.720p.HDTV.X264-DIMENSION
  3. Parks.and.Recreation.S01E01.720p.WEB-DL.DD5.1.H.264-CtrlHD

The answers are:

  1. SDTV
  2. HDTV-720p
  3. WEBDL-720p

I mentioned HDTV is the source in the release names because it is, its the source of where the episode came from, its not an indication of quality. If I had a file named Parks.and.Recreation.S01E01.720p.X264-DIMENSION the quality would be detected as HDTV-720p by Sonarr because Sonarr determined its resolution was 720p based on the filename and HDTV-720p is the lowest of the 720p qualities, so we default to the lowest.

If we treated releases coming from indexers and files on disk differently when we parsed the quality its possible that we’d be able to detect this, but then we’d introduce a whole other problem for the people that are using the release names on disk, so I see no reason to change this behaviour.

Ok, I understand what you are saying now. My only question about your example is: Since HDTV is the source and not an indication of quality why is the the file in #1 detected as SDTV? Since there is no quality listed (like there is in #2 and #3) I thought that it would revert to the file extension to determine the quality?

Then for releases the quality would be unknown, not SDTV.

That’s were you lose me…I thought I read somewhere (I can’t find it now) that it goes to the file extension last to determine quality? In that case quality would not be “unknown” it would be the default of whatever the file extension is.

Thanks.

Release is referring to the nzb/torrent name, if we skipped ignored HDTV on its own without a resolution every one of those releases would be considered unknown and not be grabbed without setting up a custom profile. You’re limiting you issue to files where there is an extension and I’m trying to explain that the issue goes beyond files and extends to releases.

Now I understand! I did not know you were talking about the actual “grabbing” of the episodes when you were saying “release”! Makes sense now.

I was going on what you said here and could not understand why it is not falling back to the extension. Now I realize that it must be the same parser that is looking for the “release” (doesn’t have an extension) and also has to parse the file name itself.

Thanks for sticking with me through this…I appreciate it.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.