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

Remux playback test on the Shield (DESIGN.md 14) #109

New Issue
Open
opened 2026-08-23 09:37:01 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-23 09:37:01 +01:00
Owner
Copy Link
Copy Source

The §14 open question, now that the pipeline works end to end. Whether a 4K remux streams cleanly to the Shield is untested; the expected failure is audio (TrueHD/DTS-HD MA bitstreaming), not bitrate — Jellyfin transcoding audio makes playback stutter while video direct-plays.

Steps:

  1. Operator: grab one 4K remux (an only_4k title or a manual grab) and play it on the Shield.
  2. Record the outcome on this issue.

Outcomes drive follow-ups:

  • Plays clean: raise/confirm the §5.5 4K size band numbers (currently placeholders) and close.
  • Audio stutters: file an audio-only remux layer (copy video, transcode audio to something the Shield bitstreams) as its own issue — the conclusion is "remux audio needs a downmix", not "remuxes are bad".

The size-band placeholders in the seeded policies stay until this resolves.

Labels: phase/4-movies, area/daemon, difficulty/easy, type/chore

The §14 open question, now that the pipeline works end to end. Whether a 4K remux streams cleanly to the Shield is untested; the expected failure is audio (TrueHD/DTS-HD MA bitstreaming), not bitrate — Jellyfin transcoding audio makes playback stutter while video direct-plays. Steps: 1. Operator: grab one 4K remux (an `only_4k` title or a manual grab) and play it on the Shield. 2. Record the outcome on this issue. Outcomes drive follow-ups: - Plays clean: raise/confirm the §5.5 4K size band numbers (currently placeholders) and close. - Audio stutters: file an audio-only remux layer (copy video, transcode audio to something the Shield bitstreams) as its own issue — the conclusion is "remux audio needs a downmix", not "remuxes are bad". The size-band placeholders in the seeded policies stay until this resolves. Labels: `phase/4-movies`, `area/daemon`, `difficulty/easy`, `type/chore`
naps62-yolo added the area/daemondifficulty/easyphase/4-moviestype/chore labels 2026-08-23 09:37:10 +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/daemon difficulty/easy phase/4-movies type/chore
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#109
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?