Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Verify treatment-directed music-video renders keep the typography region clean

Chiusa
  • Qualcosa non va?
#9,003 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
content, testing

Direzione di ricerca

Start with the synthetic Example Song workflow through compile, Apply, frame and clip generation, then run a composed render using the approved test budget. Inspect a subtitle shot and the hero shot for clean reserved typography regions and readable composited text, then record each provider and model's result in a short fidelity note and file or fix any prompt regression with a test.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

effort:medium model:medium needs-input plan planner:opus-5-5

What

Check that music-video renders directed by the treatment leave the reserved typography region clean, and that composited text over it is readable. This is the remaining manual check from #8992. The prompt change shipped in #8996.

Why it needs a human

It calls paid image and video providers on a real render. An unattended agent run is not authorized to spend on that. Remove needs-input once an operator has approved a test budget, or run the check yourself.

Steps

  • Take one synthetic project (Example Song) through compile, Apply, frame and clip generation, and a composed render.
  • Look at at least one subtitle shot and the hero shot. Check whether the reserved region (upper third, center or lower third) stayed free of generated text, and whether the composited text is readable.
  • Report the result for each provider and model separately.

Acceptance criteria

  • A short fidelity note on this issue. It names the providers and models tried, what passed and what failed, and uses synthetic, redacted content only.
  • Any prompt regression you find is filed or fixed, with a test.

Dispatch: model:medium, because the work is judgment about rendered output and the code change is small. effort:medium, because the verification is bounded.

Refs #8992

Lingua principale
JavaScript
Stelle
38
Fork
32
Merge medio
48m
PR unite (30g)
987

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di atomantic/PortOS

Tutte le issue di atomantic/PortOS

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.