Files
CinemaTrailers4Jellyfins/build.yaml
Martin 4145e1f1dd
Some checks failed
Publish Release / release (push) Failing after 8s
feat: yt-dlp prefers H.264, falls back to built-in, no pipe hang (v1.0.0.13)
- Format string prefers avc1 video + m4a audio, then any codec. The RTX 2070
  host can hardware-transcode H.264 but not AV1.
- Pass Jellyfin's ffmpeg via --ffmpeg-location instead of relying on PATH.
- If yt-dlp fails, retry with the built-in YoutubeExplode downloader.
- Read stdout/stderr while yt-dlp runs (and add --no-progress); before,
  stdout was never read, so a full pipe buffer could block yt-dlp forever.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-05 18:01:33 -04:00

25 lines
994 B
YAML

---
version: 1.0.0.13
name: CinemaTrailers4Jellyfins
guid: b581493e-1046-40ed-b6dc-cb8027624984
description: >
Automatically downloads trailers for upcoming and recently released movies
not in your library from TMDB/YouTube, and packages each one as a fake-movie
folder (placeholder video + NFO + trailer) ready for a Cinema Mode / trailer
pre-roll plugin.
overview: Builds a self-contained trailer library for Cinema Mode pre-roll plugins
category: General
owner: 514mart
targetAbi: 10.11.0.0
changelog:
- yt-dlp now prefers H.264 + AAC (plays or hardware-transcodes on every
client; VP9/AV1 often needed a CPU transcode) and uses Jellyfin's own
ffmpeg for the merge
- If yt-dlp fails, the built-in downloader is tried instead
- Fix a possible hang: yt-dlp's output is now read while it runs, so a
full output buffer can no longer block it
dotnetProjects:
- name: Jellyfin.Plugin.CinemaTrailers4Jellyfins
artifact: Jellyfin.Plugin.CinemaTrailers4Jellyfins.dll