yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

TV size bands are movie-sized; single episodes fall below the floor #95

New Issue
Closed
opened 2026-08-23 01:34:58 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-23 01:34:58 +01:00
Owner
Copy Link
Copy Source

The TV policies seeded in migration 0005 reuse the movie size bands: 2160p floor 8 GiB, 1080p floor 3 GiB. §5.5 makes below-floor a hard filter, so a typical 1080p single-episode WEB-DL (1-2 GiB) is rejected outright, which starves the per-episode path added by #38 for 1080p content.

Either the seeded TV bands need episode-scale numbers (the §5.5 placeholders are tuned by hand anyway), or size bands need to understand that a season pack and a single episode of the same resolution have different targets.

Found while implementing #38; tests there use 2160p sizes above the floor to sidestep it.

The TV policies seeded in migration 0005 reuse the movie size bands: 2160p floor 8 GiB, 1080p floor 3 GiB. §5.5 makes below-floor a hard filter, so a typical 1080p single-episode WEB-DL (1-2 GiB) is rejected outright, which starves the per-episode path added by #38 for 1080p content. Either the seeded TV bands need episode-scale numbers (the §5.5 placeholders are tuned by hand anyway), or size bands need to understand that a season pack and a single episode of the same resolution have different targets. Found while implementing #38; tests there use 2160p sizes above the floor to sidestep it.
naps62-yolo added the area/dbdifficulty/easyphase/6-tvtype/bug labels 2026-08-23 01:35:04 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No Label area/db difficulty/easy phase/6-tv type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#95
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?