mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #1053] I was never able to create a smooth loop. #795
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#795
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 @wvxwxvw on GitHub (Jan 11, 2022).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1053
Originally assigned to: @NickeManarin on GitHub.
Describe the bug
Added different sets images, including two identical sets of images and set the minimum possible match threshold. Always the same thing, can't create, he says. But I know there's 100% identical footage. :)
Desktop (please complete the following information):
@NickeManarin commented on GitHub (Jan 11, 2022):
How did you position the frames?
Use the same number for 100% equal frames, like so:
1 2 3 4 5 1
Also, which options did you use?
@wvxwxvw commented on GitHub (Jan 11, 2022):
So he himself is not looking for the same shots?
I arranged them in order.
Frame-1.bmp
Frame-2.bmp
Frame-3.bmp
...
This is how it was extracted from the original gif. And duplicated one of the first frames by placing it closer to the end, while maintaining the numbering order.
And just exported another gif with two identical sequences.
But that's all after I tried a lot of other options and never got a result.
I used any options, I wrote above, and 100% and minimum. With a mimnim, he had to find something anyway. And 50%, etc.
The question is a little off topic. windowsdesktop-runtime-6.0.1 what bit depth (x86 or x64) should I install? I put both, maybe that's the problem? ScreenToGif portable x64 version, but I tried x86 as well.
@NickeManarin commented on GitHub (Jan 11, 2022):
The algorithm tries to find the first similar enough frame from end-to-start or start-to-end depending on settings.
For example:
In this project, the algorithm wil find the frame $4 as the 100% similar as the first one and will delete all next frames ($5).
@NickeManarin commented on GitHub (Jan 11, 2022):
As for the runtime that you need, you just need to download the one for the architecture that you are using. But for Windows 7, you need SP1 and some other updates.
https://docs.microsoft.com/en-us/dotnet/core/install/windows?tabs=net60#additional-deps
@wvxwxvw commented on GitHub (Jan 12, 2022):
I thought so.
sp1 and all major (non-junk) updates are worth it.
Since you show it works, but on more complex images, such as a video series, it does not.
In general, it is clear that the simplest images are needed to use the opportunity. If you want, you can close the thread.
@NickeManarin commented on GitHub (Jan 18, 2022):
I want to leave this issue ticket open, as I need to improve the UX of the tool.
Right now it's not clear how it works and why it fails.
@NickeManarin commented on GitHub (Jan 18, 2022):
As for the runtime, I'm thinking about embbeding .NET 6 along with the app, it just going to increase the file size by a lot.
I may also distribute as a msix (maybe with support for MSIX Core, for Windows 7 and above).
@wvxwxvw commented on GitHub (Jan 24, 2022):
Yeah, that's better. This is what most developers with portable versions of software do. And nothing that will increase the size, it's better than insnalling it in the OS.
@NickeManarin commented on GitHub (Jan 26, 2022):
Fixed a couple of issues with the Smooth Loop feature.
The frames were not being correctly compared, skipping some.
And the warning message was not that great.
If you already have a smooth loop based on the current settings, the app will now tell you.
