mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #660] How to remove black frames or prevent them #537
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#537
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 @brunobola on GitHub (May 26, 2020).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/660
Originally assigned to: @NickeManarin on GitHub.
How to remove black frames or prevent them :(
@yarecky1 commented on GitHub (May 26, 2020):
@brunobola, @NickeManarin I see the same error in version 2.24.2. In 5 secs clip (24 frames/sec) I had one black frame! This is new. I've been using this application for a very long time and never had such a glitch.
@NickeManarin commented on GitHub (May 26, 2020):
I can't explain what's happening yet. This isn't new, it happened with a few users a few years ago.
Are you recording with BitBlt or DirectX?
@brunobola commented on GitHub (May 26, 2020):
I always use 60FPS.
@brunobola commented on GitHub (May 26, 2020):
I see it regardless of "BitBlt" or "DirectX".
But, because I've bee using several screens with 4K can't use Direct-X :(
@brunobola commented on GitHub (May 26, 2020):
Perhaps if some function like "remove black/invalid" frames would help a lot.
@NickeManarin commented on GitHub (May 26, 2020):
Can you tell me more about your computer?
Which version of ScreenToGif are you using?
Which windows version + build are you running?
Which graphics card do you have? Are you running the latest driver?
Type Win+R and
winverto get the version.@brunobola commented on GitHub (May 26, 2020):
Here is the info.
@yarecky1 commented on GitHub (May 26, 2020):
Ok, I think I can add two cents to the issue. I tried 4 the same low size clips and all was ok. Then I tried 1 clip with higher resolution (1347 x 688 x 200 frames x 25 fr/sec) and found a black frame in second frame. I use Bitblt.
I switched to DirectX and made 5 high resolution clips (1347 x 688). All was ok.
Then I switched back to BitBlt and again second frame in 217 frames clip was black.
@yarecky1 commented on GitHub (May 26, 2020):
The same Windows version and compilation. Old built-in graphic card Intel HD Graphics Family. Driver from 10-06-2017, version 20.19.15.4835. I don't think the problem is hidden here.
@generic-user commented on GitHub (Jul 7, 2020):
I had the same issue, but if I turn off compression, when using memory cache, it stops adding black frames to the stack ...
@NickeManarin commented on GitHub (Jul 7, 2020):
I fixed the issue with BitBlt. I can detect, during recording, when the frame was dropped and ignored it later.
With, or without compression.
I'm going to release a new version, v2.26.1.
Now, what about DirectX? For DirectX, it should already be dropping frames when the capture fails.
Are you people still having issues with it?
@NickeManarin commented on GitHub (Jul 7, 2020):
Try out version 2.26.1
@yarecky1 commented on GitHub (Jul 7, 2020):
It seems to work now in all options: BitBlt, DirectX (tested first time now), Memory Cache (also first time now) and Save to file. So far so good :)
@NickeManarin commented on GitHub (Jul 7, 2020):
@yarecky1 Nice :)
@brunobola Can you check on your end?
@generic-user commented on GitHub (Jul 8, 2020):
@NickeManarin I just tried the update, it did not fix it for me.
This Setting
When using these settings it gives me black frames. 60fp/s
Image of settings
@brunobola commented on GitHub (Jul 8, 2020):
I'll test it today and report feedback.
@NickeManarin commented on GitHub (Jul 8, 2020):
@generic-user I tried a few times, without getting black frames.
Version: 2.26.1
BitBlt, MemCache, 200Mb, No compression.
60 fps, fullscreen (1080p).
@yarecky1 commented on GitHub (Jul 8, 2020):
@generic-user I also tried your settings few times and didn't get black frames.
Version: 2.26.1
BitBlt, MemCache, 200Mb, No compression.
60 fps, fullscreen (1080p).
@generic-user commented on GitHub (Jul 9, 2020):
Just tested again, and it appears to add black frames whenever there is nothing happening on the screen.
I attached the project here: black_2.zip.
Version: 2.26.1
BitBlt, MemCache, 200Mb, No compression.
60 fps, area.
@brunobola commented on GitHub (Jul 9, 2020):
Just test it and confirm that it continues to add black frames.
@yarecky1 commented on GitHub (Jul 9, 2020):
@generic-user @brunobola
I don't confirm it. Used the same settings as above and no black frames.
@generic-user commented on GitHub (Jul 10, 2020):
Just tried again, had to make 15 different recordings before getting black frames. So it's not so easy to reproduce it seems ...
Here is the example of that clip.
@brunobola commented on GitHub (Jul 10, 2020):
Even in your gif you got black frames.
Please open it in gimp for instance and see for yourself…
@generic-user commented on GitHub (Jul 10, 2020):
Indeed, that's exactly my point. Sorry if it was not clear. English is not my mother language.
@NickeManarin commented on GitHub (Aug 13, 2020):
An option was added to prevent the insertion of black frames when capturing with BitBlt + frame cache.
It's optional because it adds a little overhead in the capture process.