Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Watermark in scenes after the latest update #5

Closed
Kinsmir opened this issue Jul 27, 2023 · 4 comments
Closed

Watermark in scenes after the latest update #5

Kinsmir opened this issue Jul 27, 2023 · 4 comments

Comments

@Kinsmir
Copy link

Kinsmir commented Jul 27, 2023

After updating to the latest version there is a watermark in every scene generated. This is with either models mm_sd_v14 and mm_sd_v15.

See also included gif as an example;
AnimateDiff_00011_

When checking out revision 8849369ce0839dc9a3ee563e56aef9e451e9c421 this problem is no longer present and generated without any watermark.

@Kinsmir
Copy link
Author

Kinsmir commented Jul 27, 2023

Probably is related to this continue-revolution/sd-webui-animatediff/issues/31

@artventuredev
Copy link
Contributor

I guest I'll revert the change until the original author identifies the root cause.

@artventuredev
Copy link
Contributor

I played around with both version and found that the watermark only present in some models, not always.

Old revision New revision

As mentioned in the issue thread, it seems to be due to the training dataset. The new version is the correct implementation and produces smoother GIFs compared to the older version. However, I've brought back the old method and also created a new node with the new method, so you can try both to find the best fit for each model.

@Kinsmir
Copy link
Author

Kinsmir commented Jul 28, 2023

Good to know it isn't a major regression in that case and I think the solution of providing a node with the old functionality is the perfect solution.

Hopefully, we see soon a newer model/dataset that doesn't causes the watermarks to appear. Anyway, I think we can close this issue for now, and thank you very much for checking it out so quickly.

@Kinsmir Kinsmir closed this as completed Jul 28, 2023
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

No branches or pull requests

2 participants