I'm not yet sold on any of them, but, if nothing else, I am amused every time I run the Jelly off the screen. Adding the command at the end will crash ffmpeg with an error message that the command has to come earlier in the list 'o commands.Īt any rate, the uploaded video ought to now show of the three basic sound groups that Space Jelly uses.

I originally attempted to use the 'Additional command line Arguments' text box, but, that adds the new command to the end of the giant command string. Note: I had to check the use custom commands box and manually add the above command to the very start of the giant command string. > Screen Recorder -> Screen Recording Options.Ĭommand Line Added: -thread_queue_size 512 Now the only problem at the moment is that the audio out paces the video by a half second or so :-/ Granted, I didn't bother really looking into why the queue size is set so small to begin with, but, I added the following custom line into my capture command and almost everything is recording perfectly. When running with the ShareX test console window, I noticed a message stating that I should up my thread_queue_size. ShareX uses ffmpeg to do all the heavy lifting relating to capture and encoding and, while no longer quite new, my computer should be more than sufficient to process some realtime video.Īfter a bit of Googling, I found an answer that looks to solve 99% of my problem. What little time I did have, I put toward revisiting why ShareX wouldn't capture proper videos.

Due to prior engagements, I won't be dedicating much time to game dev today.

Sharex ffmpeg irror gif recording