mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #694] Cinemagraph feature "smears" its result #2251
Labels
No labels
copy cats
duplicated
future feature
pull-request
⬜ Accepted
⬜ Completed
⬜ Help Wanted 💪
⬜ In Progress
⬜ Missing Details
⬜ Pending
⬜ Waiting For Answer ⏳
🆕 feature preview
🔷 Bug 🐛
🔷 Out Of Scope
🔷 Out Of Scope
🔷 Question
🔷Enhancement
🔷Enhancement
🔷Invalid / External
🔷Knowledge Base
🔷Won't Fix
🕑 High
🕑 High
🕑 High
🕕 Medium
🕙 Low
🕛 Critical
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ScreenToGif#2251
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SJT1988 on GitHub (Jul 22, 2020).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/694
Originally assigned to: @NickeManarin on GitHub.
The "ScreenToGif" saving option (default) that finds unchanged pixels works great sometimes, not-so-great other times. I commonly throw up image sequences where almost half of the pixels are unchanged but it can't detect them. Comparable gifs that are barely 8mb are sometimes 20mb because of this.
I wanted to paint-in an inverted chroma key using the Cinemagraph feature. This is supposed to literally highlight pixels in an image that are changing over the sequence. When you activate this tool, the image preview force-zooms to 100%. After painting, the program thinks for a bit and SMEARS the zoomed-out image within the painted area over the 100% area. I have not verified any kind of workaround for this. This is an important feature and I hope it gets fixed?
