mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-26 07:35:54 +03:00
[GH-ISSUE #380] BUG: Capture image quality loss when Progress bar added #315
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#315
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 @dsanalytics on GitHub (Oct 2, 2018).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/380
Originally assigned to: @NickeManarin on GitHub.
Symptom: Once progress bar is added (either with text or without), image quality deteriorates with every apply in that dialog. You have to apply it around 5 times in order to make it easy to notice, but it's present with every apply. Can you make it lossless apply? I have not checked whether other modifications (like adding transitions) do the same.
Env: S2G v2.14.1 + Win7 SP1 64bit Home Premium
Thanks for this great utility and for your work.
@NickeManarin commented on GitHub (Oct 10, 2018):
What's written under Statistcs > Frame DPI and Scale?
Also, do you mind sharing your project?
Thanks. :)
@dsanalytics commented on GitHub (Oct 10, 2018):
Everything is default - I just captured couple of frames as an example for posting and added progress bar and text.
Project: example-project.zip
@dsanalytics commented on GitHub (Feb 19, 2019):
Any updates/fixes for this bug?
@NickeManarin commented on GitHub (Sep 1, 2020):
Sorry for the delay, this was a bit of an edge case.
It was fixed. I tested applying the same feature x10 times or more.
No loss of quality.
@dsanalytics commented on GitHub (Sep 1, 2020):
Thanks - appreciated.