You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently HDR/DV etc are parsed into Codecs and it would make more sense for at least my use case to have it separate in its own field like HDR.
Example use case:
autobrr parses a release and the filters check for eg Match HDR. If it matches, good - but if not the rejection will have both the actual video codec and the hdr in the rejection message like hdr not matching. wanted: [HDR] got: [DV, x265].
This is in the case of using the Match HDR filter in autobrr. It has the reverse as well, Except HDR to skip certain types or all HDR variants.
It's a minor thing but would be a nice improvement.
The text was updated successfully, but these errors were encountered:
Currently HDR/DV etc are parsed into Codecs and it would make more sense for at least my use case to have it separate in its own field like
HDR
.Example use case:
autobrr parses a release and the filters check for eg
Match HDR
. If it matches, good - but if not the rejection will have both the actual video codec and the hdr in the rejection message likehdr not matching. wanted: [HDR] got: [DV, x265]
.This is in the case of using the Match HDR filter in autobrr. It has the reverse as well, Except HDR to skip certain types or all HDR variants.
It's a minor thing but would be a nice improvement.
The text was updated successfully, but these errors were encountered: