mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-26 15:46:00 +03:00
[GH-ISSUE #562] GIF feature: Paint over "changed" pixels #461
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#461
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 @TheJaredWilcurt on GitHub (Dec 5, 2019).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/562
It would be nice if you could have a view where all "unchanged" pixels are replaced with bright green or red in a frame. This would spotlight any pixel data that is being stored as a "change" that shouldn't be. Then you could paint over these pixels with the same green or red color. Effectively deleting the "change" in the current frame compared to the prior frame.
An example of this being done can be seen in GIF Construction Set Professional. Although the workflow is horrendous, as the application was originally designed for Windows 95, and doesn't have a great UX. It allows editing of a frame by opening it in MS Paint. Which works, but the app won't update until you close MS Paint. Paint doesn't retain your settings, so if you have a lot of frames to clean up, you'll be manually selecting the eye dropper to set the correct green, then changing the fill/stroke values of the rectangle tool at the start of every frame edit.
In the above frame the only change was from where the mouse was in the previous frame to where it is in this frame. The rest of the noise is MPEG artifacts (cleaning up someone else's screen recording that was saved as an MP4, converted to GIF, MP4 was deleted, and the GIF sent to me). So far gotten it from 43MB down to under 2MB. Chipping away.
@NickeManarin commented on GitHub (Dec 5, 2019):
Right now, this detection of changed pixels happens right before the encoding, after the user presses to save the file.
When editing the animation, you'll see the full frames, not only the pixels that changed.
I'm not sure how to add this functionality to the app...
@TheJaredWilcurt commented on GitHub (Dec 5, 2019):
From what I can see, the way GIF Construction Set does it, is they load in the GIF data one frame at a time and show just the pixel data that is stored for the frame. Then they have a tool in the menu bar to "rebuild" where it updated each frame to show the full data.
So maybe the same idea could be done here, but it would save a temp version of your project to a file, then load in just the frame data to display the "only show changes" view?
Then re-build it before saving?