-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thoughts about new Quality implementation #1266
Comments
File size ranges as a propriety. So i could make like |
From Slack:
|
Here is the list that I gathered (not all values) from guessit, knowit and Medusa, probably the properties and values for a new quality design should take them into consideration:
Can you all take a look at this initial list and make comments. I can edit it as we go And below a proposal for the quality profiles. The way it works is quite simple: it continues to snatch until it reaches the last item of the list:
|
Would probably probably be more advantageous to have the video encoder rather than the codec |
can you put a list of the video encoders? |
I think we should also allow users to set the allowed range for resolutions in an advanced page. Should we add the interlace versions of the resolutions? Can any tools we use right now detect that? |
I found this: I think i shouldn't need to list the most popular, ie x264, hence the links. |
Afaik the only encoders used or tagged as such are x264 and x265. The rest we can happily forget about. |
@medariox what about people that don't want DivX for example but they're getting an old show that was mainly released with that codec? |
@OmgImAlexis
DivX is there (it's a codec, not an encoder). |
Ah, read your comment wrong. |
Hi, for example, I'd like to have 720p HDTV replaced by 1080p HDTV and then by 1080p webdl and then 1080p bluray. I think it was done like this befor, nearly 2 years ago. |
Yeah it'll be nice to have the qualities weighted so we have to I'd like this one, then this and then this but if any of them are found just grab the highest in the list first and then replace. I think right now it's too complicated and doesn't really make much sense even for myself who's been using it for years and years. |
Guessit rules to follow quality standards #1266
Hi, is there a |
@trohnjavolta |
@medariox ok, thx. in sickrage I just see ignored and required words. |
@medariox Ok, I put x265, hevc in preferred words but what's the purpose of this? Medusa dl's a x264 file anyways and it doesn't show up in backlog. |
@trohnjavolta please move this to another issue. |
All the information that we have (before downloading and investigating closer) only states something about the source, the codec and/or the resolution. I can get a 1080p that is compressed harder than a 720p so I also need to look at the file-size in order to infer something about quality. CouchPotato has an excellent file-size filter, but one that can be improved upon: The problem with the current CP implementation is that it does not work with different codecs, e.g. h264 vs h265, so in reality we need such a table for each codec (or just a default, common table and the option to add new tables in order to override for specific codecs, e.g. h265 vs everything else). Such a filter would be an immense enhancement to Medusa. |
CouchPotato builds on the file-size filter by allowing us to configure Quality Profiles. You configure a Quality Profile by providing a name, e.g. "BestQ". As with the CP file-size filter, this feature was not designed with codecs in mind, so it would require some thought in order to get to something that works better for Medusa |
Scene formats:
TV:
Required properties: File Resolution, Source Format, Encoder
Optional properties: Extra
P2P formats:
TV:
Required properties: File/Source Resolution, Source Format, Audio, Codec/Encoder
Optional properties: Episode Name, Extra
Proposed properties:
Required: File/Source Resolution, Source Format, Audio, Codec/Encoder
Optional: Extra
@pymedusa/contributors @pymedusa/developers
The text was updated successfully, but these errors were encountered: