![]() ![]() Many capture apps use ffmpeg, which can be fine - just not great for capture. I like Ashampoo Snap because it lets you use any codec you've installed - videohelpcom has quite a few. Note: there are codecs specifically designed to be fast for capture. Since you'll often edit the file, which means re-encoding, your main concern is getting the capture written to disk in the best quality possible - not the final format desired. The faster that file can be written, the less compression you need to use, which lessens the CPU load while increasing quality, and you can also try to use a less efficient codec, e.g., encoding mpg2 require MUCH less CPU than H.264/AVC. a conventional hard disk helps, a very fast NVMe drive helps more. So, you want to be able to write the captured file to disk as fast as possible - a 2nd HDD helps, an SSD vs. Both compression and efficiency are required to create a file small enough that it can be written to disk in real time. ![]() When it comes to encoding the audio & video, generally the more compression used, and the more efficient the codec, the more CPU resources required. If there's audio, depending on the original format, it can take resources to decode too. Displaying what you want to capture can take quite a bit of resources, whether it's making the calculations to display a game onscreen, or decoding AVC video. Your hardware has to do 3 things when you capture video: it has to display what you want to capture, & optionally play audio it has to convert the visual data you see, and optionally the audio you hear, into a format that can be stored in a file and it has to write the resulting file to disk at least as fast as the audio & video are displayed / played & captured. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |