mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 23:25:52 +03:00
[GH-ISSUE #546] Exporting 1531-frame project results in corrupted video #449
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#449
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 @mtlynch on GitHub (Nov 4, 2019).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/546
I've successfully exported shorter videos I recorded with ScreenToGif, but I recently tried recording a longer one (1,531 frames) and ScreenToGif seems to have trouble exporting it as an .avi. It corrupts the colors and shows frames out of order.
Here's the project file:
If I Save as "Vdieo" @ 30 fps, with "Flip the video (vertically)." checked, then select the .avi extension with System encoder (100% quality), the result is a video that doesn't match the captured frames.
Original
Exported
Environment
@NickeManarin commented on GitHub (Nov 4, 2019):
I recommend using FFmpeg and exporting as MP4 instead.
The inbuilt AVI encoder is not optimal, also it really depends of which compressor you used.
Some work, some don't. :/
I tested creating an uncompressed video and a video using the Intel IYUV compressor and both worked normally, just the file size was big.
@mtlynch commented on GitHub (Nov 4, 2019):
Good to know. Thanks!
@NickeManarin commented on GitHub (Nov 4, 2019):
Which compressor did you use, btw?
@mtlynch commented on GitHub (Nov 4, 2019):
I chose "Full Frames (Uncompressed)" when I hit this bug.
I just tried with a different encoder and it did output the video successfully. Thanks for your help!