The Issues –
Dynamic Range, as you can tell quite easily from the screen grabs of the footage transcoded using different tools, the 5DtoRGB largely maintained the dynamic range that the GH2 sensor (using a Flow Motion V2 hacked firmware in this case) captured. While the straight output from FCPX or ClipWrap resulted in a “clipped” dynamic range, losing details in dark areas.
Cropping, scroll through the shots you’ll find the straight output and 5DtoRGB output managed to keep the footage uncropped, while ClipWrap crops the image with different codecs.
Don’t be entangled with the reason why this is happening, it’s a long time glitch in QuickTime codec and Apple hasn’t provided an official solution.
The Solution –
Also this post says ITU-R BT.601 is the correct Decoding Matrix to choose, as comparison, in the 2nd and 3rd pics above, we noticed that the dark area in BT.709 profile are incorrectly exposed and pixelated.
According to 5DtoRGB website —
“5DtoRGB takes a no-compromise approach to quality. 5DtoRGB bypasses QuickTime decoding altogether, works internally at 10 bits and uses your video card’s GPU for its YCbCr to RGB conversion. It also recognizes Canon’s full range 8 bit YCbCr values (0-255), avoiding clipping and the resulting loss of picture information. The resulting files are the absolute highest quality you’ll ever get out of the camera. In fact, you could argue that they’re even better than the camera originals since they’ve undergone high quality chroma smoothing.”