Clipper Setup

← Back to clip generator

1. Configuration status

Enter password and click "Check status"

2. Disk usage & cleanup

Check status above to see disk usage.

0 = delete everything. Successful and failed jobs both use this threshold when triggered manually. The photo library (section 3) is not touched by cleanup.

3. Photo library

Headshots used as starting points for thumbnails. The pipeline matches each clip's thumbnail_subjects against this library and lists any missing photos at the end of titles.txt.

Filename becomes the lookup key — uploading Luka Dončić.jpg stores it as luka_doncic.jpg, which then matches subjects like "Luka Dončić" or "Luka Doncic". Supported: jpg, jpeg, png, webp.

— photos in library
Check status above to load the library.

4. Thumbnail team templates

Brand assets used by the thumbnail compositor, one folder per team. Each team needs bg_<team>.png, banner_<team>.png, logo_<team>.png, reference_<team>.png, and config.json. Filenames must match — the compositor resolves the layer-order template from them.

— teams configured
Check status above to load brand assets.

5. Show layouts

JSON files describing picker geometry per host count — 2_host_layout.json, 3_host_layout.json, 4_host_layout.json. These apply across all teams with that host count. Schema is owned by the picker; uploads only validate that the file parses as JSON.

— show layouts available
Check status above to load show layouts.

6. Shared brand assets

Universal files used by every team: base_config.json, dividers.png, and the font file (e.g. font_pervitina_dex.ttf). Allowed extensions: jpg, jpeg, png, webp, json, ttf, otf.

Currently-uploaded shared files appear in section 4 above under the _shared row.