P - Bandicam MPEG-1 Quality80 'HalfSize' setting O - Bandicam MPEG-1 Quality80 'YouTube720p' setting N - Bandicam MPEG-1 Quality80 'Default' setting L - Playclaw MJPEGcompression (6 threads) J - Bandicam MJPEG Quality80 'Vegas/Premiere/Pinnacle' setting Here is the 4x4 (16-Video/Codec) comparison key (it is in order of largest file size produced to the smallest):ĭ - Playclaw NoCompression In general, the recorded segments in the video comparison are shown in order of largest disk space usage per second to the smallest. Recording Size: Varies, sizes are included in the video for each recording segmentĬodecs utilized: MPEG, MJPEG, UTyuv422, FRAPS1, various quality settings for all Recording Time: 10 seconds or 300 frames, attempt made to record from same location for each segment Resolution: Slightly higher than HD 1920x1096, (Maximized Window 1920x1200 Desktop with doubled taskbar), resized to fit into 1920x1080 (1080p HD) video rendered as final video output for upload Recorded with: Fraps, Dxtory, Bandicam, Playclaw It is mainly a comparison of the file size produced (shown on the right hand side) vs the general quality of the recording (program/codec shown on the left hand side). Also, the sharp edges and movement of groups of pixels, along with solid colors and dark areas, are a good test of compression and will bring out any artifacts that the contending codecs might sweat out. Without taxing the CPU/GPU extensively, more of the power can go towards recording and getting the most 'bang-for-the-buck' from the game recording apps. Yes, MC isn't exactly 'high-end-tessa-shadow-bump-mipped', but that's the point. I do a series of testing called TestRuns and wanted to compare side-by-side, video taken of the same material/game/area.įor this TestRun, the game used is Minecraft. I have recently finished a video comparing recordings from Bandicam (Registered), Dxtory (Trial Verison), Fraps (Registered) and Playclaw (Trial Version).

Dxtory vs bandicam vs fraps