Skip to content

Add animated WebP from video guidance to video-transformations reference#19

Open
carlevison wants to merge 3 commits into
mainfrom
improvements
Open

Add animated WebP from video guidance to video-transformations reference#19
carlevison wants to merge 3 commits into
mainfrom
improvements

Conversation

@carlevison

Copy link
Copy Markdown
Contributor

Summary

  • Adds animated WebP from video documentation to references/video-transformations.md (progressive disclosure, not top-level)
  • Documents both valid delivery paths: f_auto:animated (Path A) and fl_animated,fl_awebp + WebP signal (Path B)
  • Explicitly calls out invalid combinations that silently produce wrong output
  • Updates the reference pointer in SKILL.md to mention animated images

Test plan

  • Promptfoo test T07 (animated WebP from video clip) should now pass — skill covers both valid paths and the failure cases the rubric checks

🤖 Generated with Claude Code


To deliver an animated WebP from a video, use **one** of these valid combinations:

**Path A (simplest):** `f_auto:animated` — sufficient on its own; no extension or fl_ flags required.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

f_auto:animated delivers WebP only when the client sends a WebP Accept header. It falls back to GIF otherwise. Worth adding a note here so it's clear this isn't a guaranteed WebP delivery path.

**Path A (simplest):** `f_auto:animated` — sufficient on its own; no extension or fl_ flags required.
```
du_5/f_auto:animated/q_auto # First 5 seconds as animated WebP (or GIF where unsupported)
du_5/e_loop/f_auto:animated # Looping animated WebP

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The looping example omits q_auto but the non-looping example above includes it. Is this intentional? If not, worth adding for consistency so it doesn't imply quality optimization doesn't apply when looping.

du_5/e_loop/f_auto:animated # Looping animated WebP
```

**Path B:** `fl_animated,fl_awebp` together, **plus** a WebP delivery signal (`f_webp`, `f_auto`, or `.webp` extension):

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The top of this file (line 12) says "Always use f_auto:video or a specific video format plain f_auto may return an image thumbnail." Path B on line 78 uses bare f_auto as a valid WebP signal. These two rules look contradictory without explanation. Something like "bare f_auto is valid here because fl_awebp already constrains output to animated WebP"

**WRONG — these do NOT produce animated WebP:**
- `fl_animated` alone (missing `fl_awebp`)
- `fl_animated,fl_awebp` with no format parameter and no `.webp` extension
- `f_auto` alone with a `.webp` extension (returns a still frame, not animated)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

f_auto appears as valid in Path B (line 78) and invalid in the WRONG list here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants