mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #575] Possibility to record only on Pixelchanges #473
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#473
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 @dschiller on GitHub (Jan 6, 2020).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/575
Originally assigned to: @NickeManarin on GitHub.
Don't know how to create a Question here. Is it possible to record only if Pixel changes on Screen ?
@NickeManarin commented on GitHub (Jan 7, 2020):
Right now, no.
With the DesktopDuplication API is possible, but I didn't implement it that way for the next version.
Right now you can record normally and later remove duplicated frames using the "Remove Duplicated Frames" feature.
Why do you ask?
@dschiller commented on GitHub (Jan 11, 2020):
I ask because if recording long sessions to catch Errors for UI Automation it take a long time after stop recording and accessing the recorded Images. Would be much faster if already recording only changed Images.
@NickeManarin commented on GitHub (Jan 20, 2020):
This could be implemented as a new capture mode, by using a feature from DesktopDuplication that tells which screen areas have a pixel change.
@NickeManarin commented on GitHub (Aug 8, 2020):
Done! It will be available with the next version, 2.27.
It can be enabled when using DirectX capture mode.
How does it work?
If something changed (pixels, including mouse cursor updates) within the capture region since the previous frame was captured, another frame will be captured.
Also, the selected maximum framerate will be respected.
@dschiller commented on GitHub (Aug 9, 2020):
Amazing Work! Thanks a lot!!