Doesnt work with the fresh new OMNI watermark today

[Demodon5bit]

seems like they released new watermark with veo&Omin ，It comes form different place and size

[Demodon5bit]

I tested this in the CLI, specifying the location and new dimensions for the diamond watermark tool; it is now working perfectly.

[adenaufal]

how do you do that?

[Demodon5bit]

how do you do that?

I use the GUI to identify the new watermark's position and dimensions, and then—using the CLI method—I input the new watermark size and position into Codex.

[Demodon5bit]

At 1080P resolution, the new watermark position is (1704, 864)–(1776, 936), measuring 72x72. At 720P, the position is approximately (1160, 600)–(1208, 648), measuring 48x48.

[moltenRice]

I tried:
GeminiWatermarkTool-Video.exe "C:\Users\allan\Videos\Saved Videos\video.mp4" --region 864,1703,72,72 --force --veo
didn't work, got:
[SKIP] video.mp4: no Gemini 3.5 diamond detected at 1080x1920 (auto mode)

My video is vertical 1080x1920p. Using ffmpeg got every frame from the video, then using the image removal feature in the gui, got those coordinates (864,1703,72,72) using the snap function.

I think the CLI is not changing the process method from auto to "manual" thus, not using the given coordinates or not detecting the vertical format correctly.

Also tried the same first command without --veo and same result!

edit 1. Should mention that the GUI for videos on windows 0.6.1 is not working. Only CLI. The GUI just acts as the images app not the videos one.

edit 2. Version correction.
Cheers

[allenk]

Let me verify the test. I just generated a 720p video:

black_theme_20260605.mp4

The results are as follows:

black_theme_20260605_processed.mp4

I wouldn’t say it removes watermark perfectly, but most of it looks acceptable. It would be best if you could provide a sample for direct application. Once my Runner usage has been reset, I'll update to the new version.

[Northbei888]

https://github.com/user-attachments/assets/3a65a18d-2f5c-488d-bcaa-e6ebffa5909a looks like my watermark is not the same place with you

[moltenRice]

https://imgur.com/a/wQSaEQk

Tried with both of these, both were skipped :(
Also tried them with the region flag, still skipped.

edit1. added the processed files:
https://imgur.com/a/EflA8PE

[allenk]

Thanks for the report — you nailed it. Google did move the watermark: it's the same diamond, just relocated to a new position (and on some outputs a slightly different size), so v0.6.1 didn't recognise it and skipped the file.

This is fixed in v0.6.2 (just released). Two changes handle it:

• The new positions are now calibrated, so they auto-detect out of the box.
• A new smart bottom-right search locates the diamond wherever it sits — it matches the shape across several frames and requires them to agree on the spot. So if the position gets moved again in the future, the tool finds it on its own, no update needed.

Please grab v0.6.2 and try again — default mode, no flags:

GeminiWatermarkTool-Video your_video.mp4

One tip: run it on the original-resolution file, not a downscaled copy. I tested on a couple of samples and the full-resolution clip detected and cleaned perfectly, but a heavily downscaled upload (e.g. shrunk to ~480px wide for sharing) can blur the diamond enough that detection misses it. If you still hit a SKIP on the original file, drop the clip here and I'll calibrate that exact case.