mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #134] Slow play back #117
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#117
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 @gitmegitme on GitHub (May 8, 2017).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/134
Originally assigned to: @NickeManarin on GitHub.
Hi there,
Thanks for a great product.
The playback in both record and cam, is a little slower than real time. Have I done something wrong, or is there a setting I should change please?
Thanks again.
@NickeManarin commented on GitHub (May 10, 2017):
Unfortunately that's a heavy IO operation (that reads the images/frames from the disk). If your disk is being used by other apps, it will take more and more to load the next image/frame.
@strich commented on GitHub (Jun 3, 2017):
Surely during editing the recording should sit in memory, not disk?
@NickeManarin commented on GitHub (Jun 3, 2017):
Yep. :/
@LovCAPONE commented on GitHub (Nov 26, 2018):
I might have found a solution to this issue. At first, I wanted to do a pull request but later I realized that not only did the solution involved a lot of code, but also that making a separate project for it would be better as some other projects might benefit from the component.
So, my solution is in this repo. The major down side to it is that it has a lot of dependencies, so if you decide not to integrate it to your project, I hope that it can give you insights on how to solve this issue. If you have any questions it will be my pleasure to try to answer them as best as I can.
@mabakay commented on GitHub (May 9, 2021):
#878 just include it here as a suggestion.
@NickeManarin commented on GitHub (Jun 25, 2021):
Closing this as the performance was improved in recent releases.