mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 23:25:52 +03:00
[GH-ISSUE #37] [Bug] System.AggregateException #35
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#35
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 @Kristinita on GitHub (Nov 20, 2016).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/37
Summary
GIF with several title frames and fade effects not encode for me.
Expected behavior
Actual behavior
Translate:
Click on this message to see full log:
Steps to reproduce
I create GIF 3 Title frames and 3 fade effects →
Save As:LegacyEncoder I get error,ScreenToGIFEncoder I get error,SystemEncoder, 167(!) MB GIF encode for me. No program is open this file.In
E:\Chocolatey\lib\screentogif\content\Logsdirectory I sawlog_20_11_2016.txtfile.Attached file
I save my project file
Environment
Operating system and version:
Windows 32-bit 10.0.14393
ScreenToGif:
2.3.161030
.NET Framework
4.6 Build 394802
Thanks.
@NickeManarin commented on GitHub (Nov 21, 2016):
Looks like at least one of the frames has a different size. Could be related to a bug related to high DPI. Working on it.
@NickeManarin commented on GitHub (May 2, 2017):
With previous fixes (v2.7) this bug got less common. But even if someone tries to manually resize the frames by opening the temp folder, the app will not throw an exception, it will treat the missing pixels as a transparent color.