new version not working with some format

[zenjichen]

cant remove https://drive.google.com/drive/folders/1DwlsXkkyKzdw4Bq6PJm7ZlKRfwNj6dcF?usp=sharing
can u fix

[allenk]

v0.6.3-demo is out and should handle what you ran into on two fronts:

• It now removes the new small "Veo" text watermark that Flow adds to its latest outputs — automatically, no flags.
• Its auto-detection is also smarter about the diamond watermark: even when Google moves it to a new position, the tool finds it on its own.

Just run your video through the latest build — it figures out which watermark is present and cleans the right one:

issue_22_2_1080p_processed.mp4

issue_22_1_720p_veo_processed.mp4

[zenjichen]

awwwwsomeeeee , many tks bro

[zenjichen]

v0.6.3-demo is out and should handle what you ran into on two fronts:

• It now removes the new small "Veo" text watermark that Flow adds to its latest outputs — automatically, no flags.
• Its auto-detection is also smarter about the diamond watermark: even when Google moves it to a new position, the tool finds it on its own.

Just run your video through the latest build — it figures out which watermark is present and cleans the right one:

issue_22_2_1080p_processed.mp4
issue_22_1_720p_veo_processed.mp4

hmmm, I tried it, but it didn't work for everything, though at least it solved part of the problem.

[zenjichen]

here is all bug when I dragged a single file, u can check.

https://drive.google.com/drive/folders/1C24VPTuOUtE1KYS4S5ednC6Nz_EKVZeX?usp=sharing

I reproduced it, and the bug appeared when I dragged a single file into the tool, but if I dragged more than one file, the problem seemed to be solved.

[allenk]

Hi @zenjichen,

I've actually confirmed this issue. The main reason is a parameter handling problem. This issue can be avoided using the -o option. In automatic mode, using explicit parameters will prevent the problem. I will address this issue in the next major version.

[zenjichen]

Hi @zenjichen,

I've actually confirmed this issue. The main reason is a parameter handling problem. This issue can be avoided using the -o option. In automatic mode, using explicit parameters will prevent the problem. I will address this issue in the next major version.

I've been having trouble with these small watermarks. Some work, some don't :(((

[allenk]

Hi @zenjichen,
I tested your videos, and the 720p ones should all be decodable using the --mark veo parameter. However, the 1080p VEO files have many quality issues. The watermark appears very unstable. This is an ad hoc approach. I verified that it only removes about 80% of the watermarks.

issue_22_3_1080p_veo.mp4

issue_22_5_720p_veo_processed.mp4

issue_22_4_720p_veo_processed.mp4

[zenjichen]

many tks