You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When the "Export partially" option is selected during the save process, the custom frame order provided in the "Expression" field is ignored. For example, an input such as 50-100,0-49 is rendered sequentially as 0-100, disregarding the specified swapped order.
To Reproduce
Steps to reproduce the behavior:
Go to 'Save as'
Click on 'Export partially'
Scroll down to 'Partial export'
Select 'Expression' under the dropdown menu
Type a custom frame order, e.g., 50-100,0-49
Click on Save
Observe that the output GIF renders sequentially (0-100), ignoring the custom frame order.
Expected behavior
The exported GIF should respect the custom frame order specified in the "Expression" field. For example:
Start with frame 50
End with frame 49
Jump in the middle as specified
This behavior is especially important when the thumbnail (derived from the first frame of the GIF) should represent a visually appealing frame located later in the sequence.
Desktop (please complete the following information):
OS: [e.g. Windows 10 PRO]
Version: [e.g. 2.41.1]
Additional context
This feature is important for workflows where the thumbnail of a GIF (derived from the first frame) should represent a visually appealing frame located later in the sequence.
Attempts to reproduce this behavior using custom FFmpeg parameters have shown that frames are united in sequential order regardless of the input, potentially overridden by ScreenToGif.
The workaround could be implemented in various ways, potentially offering better flexibility than directly fixing this bug. For example:
Option to select a split frame: Allow users to define a specific point where the sequence is divided.
Option to select a specific frame for the thumbnail: Enable users to choose a specific frame to be copied and used as the first frame, ensuring the desired thumbnail is delivered.
Describe the bug
When the "Export partially" option is selected during the save process, the custom frame order provided in the "Expression" field is ignored. For example, an input such as
50-100,0-49
is rendered sequentially as0-100
, disregarding the specified swapped order.To Reproduce
Steps to reproduce the behavior:
50-100,0-49
Save
0-100
), ignoring the custom frame order.Expected behavior
The exported GIF should respect the custom frame order specified in the "Expression" field. For example:
This behavior is especially important when the thumbnail (derived from the first frame of the GIF) should represent a visually appealing frame located later in the sequence.
Desktop (please complete the following information):
Additional context
This feature is important for workflows where the thumbnail of a GIF (derived from the first frame) should represent a visually appealing frame located later in the sequence.
Attempts to reproduce this behavior using custom FFmpeg parameters have shown that frames are united in sequential order regardless of the input, potentially overridden by ScreenToGif.
My ffmpeg param for example:
The text was updated successfully, but these errors were encountered: