it also dosent work and comes up with ”Skip“

[vincehongsun-code]

Hi, i got some kinds of those videos watermaker can't be removed, it happens to horizontal videos. However works on vertical, even though the watermark logo still kinda "bling bling" a litte bit.

gemini_generated_video_6FD4C6D9_processed.mp4

gemini_generated_video_227A6E5C.MP4

[vincehongsun-code]

Comes up with "Skip" in terminal.
[SKIP] gemini_generated_video_227A6E5C.MP4: no Gemini 3.5 diamond detected at 1280x720 (auto mode)
Auto mode is calibrated for 1080p (1920x1080, 1080x1920) and 720p (1280x720, 720x1280).
For pre-Gemini-3.5 "Veo" text watermarks, try --legacy.

[allenk]

Hi @vincehongsun-code — both issues should be fixed in v0.6.1, just released: https://github.com/allenk/VeoWatermarkRemover/releases/tag/v0.6.1-demo

• Horizontal → SKIP: v0.6.0's auto-detect only looked at frame 0, which is a fade-in on many Veo clips (NCC = 0 → SKIP). v0.6.1 probes 12 frames across the video, so fade-ins no longer cause a false SKIP.
• Vertical "bling bling": the watermark wasn't blinking — v0.6.0's per-frame alpha estimator was producing different removal strengths frame-to-frame on content with foreground motion. v0.6.1 replaces it with an adaptive bisection feedback loop (up to 5 rounds per frame) plus a ±0.05 per-frame change cap that prevents single-frame flashes.

The attached video is v0.6.1's output on your horizontal sample — you can see the result before downloading. Your samples were the main test cases for this release; acknowledged in the release notes. Thanks!

Some clips with heavy foreground motion can still leave residue on a few frames — see the manual touch-up workflow in the README for those. If you hit problem frames on your own files, please reply with which ones.

issue_5_1_720p_capped.mp4

[vincehongsun-code]

Thank you for the feedback and update, mate