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
Following this question on Discord, I've encountered an issue with ShareX on Windows 10 when attempting to save screen recordings as GIFs. Each attempt results in an FFmpeg-related error, preventing the GIF from being saved correctly. The problem might be linked to the configuration of the complex filters in FFmpeg, particularly around audio stream mixing. Below is the error message received:
Expected Behavior:
The screen recording should be saved as a GIF without errors.
Actual Behavior:
The recording process fails, and the aforementioned error message is displayed.
System Information:
ShareX Version: 16.0.1
Operating System: Windows 10
FFmpeg Version: Included with ShareX
I have tried searching the existing tickets for similar issues but have not found any that address this specific problem. Any insights or recommendations on how to resolve this would be greatly appreciated.
Thank you so much for your help.
The text was updated successfully, but these errors were encountered:
Following this question on Discord, I've encountered an issue with ShareX on Windows 10 when attempting to save screen recordings as GIFs. Each attempt results in an FFmpeg-related error, preventing the GIF from being saved correctly. The problem might be linked to the configuration of the complex filters in FFmpeg, particularly around audio stream mixing. Below is the error message received:
Expected Behavior:
The screen recording should be saved as a GIF without errors.
Actual Behavior:
The recording process fails, and the aforementioned error message is displayed.
System Information:
I have tried searching the existing tickets for similar issues but have not found any that address this specific problem. Any insights or recommendations on how to resolve this would be greatly appreciated.
Thank you so much for your help.
The text was updated successfully, but these errors were encountered: