Skip to content

Content duration range as Override Rule #3031

@c010rb1indusa

Description

@c010rb1indusa

Description

This may sound like a bit of an odd request but I would like to set override rules based on the duration of said content. For instance if a film is between 90-120 minutes long, that could trigger an override rule.

Desired Behavior

If Seerr could extend the override rule to content duration, I could effectively target certain bitrates by directing requests in Seerr to different quality profiles in radarr/sonarr with various min/max size requirements. I've already submitted requests in both sonarr/radarr that custom formats allow you to define bitrate vs raw filesize but they seem reluctant to do anything with custom formats that doesn't strictly involve regex. Then this possible work around popped into my head and I thought it couldn't hurt to ask.

Additional Context

The reason I would like this feature is custom formats in radarr/sonarr allow you to target a min/max filesize but not overall bitrate. They can be set globally with 'Quality Definitions' in radarr/sonarr respectively but that applies to ALL quality profiles and doesn't take into consideration codec being used nor does it allow for any flexibility when parsing through files the way custom formats allow for allow other attributes of a release.

Thanks for all the hard work you guys put in to Seerr.

Search Existing Issues

  • Yes, I have searched existing issues.

Code of Conduct

  • I agree to follow Seerr's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting triageThis issue needs to be reviewed
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions