#Quicksync async depth movie#

keyframes are tiny jpegs inserted in a movie preferably when a scenery change happens that is greater than what a motion codec would be able to morph the existing screen into. I would say not long from here we'll see encoders doing video parallel encoding by loading pieces between keyframes. With that said, only the CUDA videos from Badaboom and MediaConverter demonstrate poor motion prediction in areas we haven't see with MediaEspresso. This would indicate that there is something problematic with the implementation of CUDA in the first two apps. Overall, CUDA does look better in MediaConverter than it does in MediaEspresso, but Badaboom's output looks the best.

It is particularly pronounced in some smooth panning scenes, and when there is a slow fade into another scene.

The issue in MediaConverter is more puzzling, though, since we used the retail edition to get CUDA functionality (the latest beta inexplicably doesn't recognize our GeForce GTX 580).Īside from tracking issues, this time we are looking at poor quality output from MediaEspresso. Given that Elemental is still in alpha, we readily expected some errors, and entropy-related issues that affect the reassemble process are usually a quick fix. This is something specific to using CUDA in MediaConverter and Badaboom. This screen capture is not the result of human error, as we used the batch function to track and output specific frames. Both programs generate a file that doesn't properly track, which means during the reassemble process, something is off-kilter. As you might notice, the light on Doug's collar is slightly brighter in MediaConverter, and the frame is off in Badaboom (it's not the same frame at all).

Quicksync async depth