mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-26 15:46:00 +03:00
[GH-ISSUE #327] v2 Encoder Green Screen on Twitter #273
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#273
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 @spottedmahn on GitHub (May 25, 2018).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/327
v2 Encoding
v1 Encoding
Is that a browser problem or an encoding problem?
@NickeManarin commented on GitHub (May 26, 2018):
Encoding. The V2 is guessing the wrong color when picking the color that will be treated as transparent. This happens when that color is present in a bunch of pixels on the source frame (It's probably the color whell at the bottom left corner).
Here's where you can change that color to something like magenta:
@spottedmahn commented on GitHub (May 26, 2018):
I will try that and report back, thanks 🙏!
@spottedmahn commented on GitHub (May 26, 2018):
Still no luck...
@NickeManarin commented on GitHub (May 26, 2018):
Oh. :/
Can you share the project with me?
@spottedmahn commented on GitHub (May 26, 2018):
Sure 😊
Gaussin Blur v2 Encoder - magenta test.stg
@NickeManarin commented on GitHub (May 27, 2018):
I was analyzing the recording. There's something strange happening.
Frame # 349 has a different dpi than frame 350.
I think that it's caused by the "Show mouse clicks" option that was turned on. I'll fix this issue.
Anyway, I was going to propose to hide the color wheel with some other color, like black or white. But then I found out the other bug above.
@spottedmahn commented on GitHub (May 28, 2018):
Didn't know about that! Sounds like a cool 😎 feature!
Thanks for debugging it! 🥇
@spottedmahn commented on GitHub (May 28, 2018):
BTW, the DPI change must have something to do w/ my setup.
I have 3 monitors. 2 are ~22" 1080p. The other one is my 15" laptop monitor.
I was probably trying to record the full screen. Maybe from monitor 3:
The stop icon in ScreenToGif was probably in monitor 1.
@spottedmahn commented on GitHub (Aug 16, 2018):
Hi @NickeManarin - FYI, I'm still seeing this problem w/ v2 encoder 😢
How can I help get this fixed? Thanks!
@ParticleCore commented on GitHub (Nov 15, 2019):
To get around this problem use a dummy color that is not present in the original video, otherwise the engine will get confused and mix the dummy color and the same color from the video which leads to the corrupted result.
If you cannot by any means use any color, for example the original post contains a color wheel, disable the use of the dummy color all together, but this will result in a file with a bigger size.
@NickeManarin commented on GitHub (Nov 15, 2019):
@spottedmahn Oh, I totally forgot about this issue. I'm sorry, I can't keep up.
As explained by @ParticleCore, it's the same idea as before, try hiding any color that is marked as the chroma key.
@spottedmahn commented on GitHub (Nov 18, 2019):
I see, thanks @ParticleCore 👍
for reference:
