@ttancredi

I believe it depends on your camera settings and what version of 5DtoRGB you use. I use 2.2 and rec709 for both my AF100 and GH2 with 5DtoRGB 1.5.3b, but I always color correct.

Although on the whole 5D2RGB may give you a better starting point (quality wise) I wouldn't go overboard on that claim. In some cases (rare, but not very rare) it does result in highlighting the banding in a shot, and also I've seen it create flicker in the edges of transitions in lighting accross a frame (basically pretty much highlighting another side effect of the 'mosquito noise'. In both thoses cases I've found that working with the original non transcoded footage produces better results.

Is it impossible to queue the files when converting them in 5DtoRGB? I mean, it will take too much time if you'd have to sit and add all files manually and converting them one by one.

Edit: Wtf... "The free 5DtoRGB Lite can process one video file at a time. For processing multiple files, check out 5DtoRGB Batch" And it seems like the batch isn't available for Windows...

@Petee28 - what version of mc5 are you using?

I edit AF101 and GH2 footage in FCP X.

Firstly a warning to those who are letting FCP X import files directly from camera. FCP X ingests the GH2 progressive clips okay, but flags them as interlaced and leaves bad jaggies (aliasing) artifacts on any diagonal lines. These are visible in the interface and on export in 1080p.

So I tried ClipWrap (version 2.4.7). It re-wraps the MTS files fast, flags them as progressive and removes the artifacts, but I found I lose 2 frames of footage and all clips suffer a -4db hit on the sound. The developers were very responsive over e-mail, but haven't fixed the problem and I have therefore been searching for a reasonably priced alternative.

I came across this thread yesterday, tried the trial version of 5DtoRGB and can say I'm very happy with the results. No frame loss, no sound loss. Even though FCP X seems to manage my AF101 footage straight from camera okay I'm going to transcode all clips through 5DtoRGB from now on before I bring them into FCP X.

However, I have 3 questions for those more experienced than me: - I've noticed the colour of the clips is different (flatter) after 5DtoRGB does it's thing. What settings should I use to get the closest match to the original GH2 files? - Secondly, what colour programs are other people using in conjunction with FCP X? (I find the built in colour correction a little clunky) - And if I'm recording on the internal codecs at 24mbps, do I ever need to transcode to anything above ProRes 422 LT? (will I see any picture benefits at the higher rate codecs?)

Thanks in advance.

Great - thanks for the info, Nomad.

@dkitsov Regarding the timecode issues, what do you do for the audio? I sync the clock on my audio and video devices at the beginning. There is some drift, but having all video and audio files with timecode from the date of creation is a great benefit when editing and organizing footage.

These will work for the first edit. Then the audio and video can synced with the clapper. Finally the video timecode can be added to the audio in order to replace the audio TC.

@ghostlayer

There is a free batch Python script that you can run or you can pay for the official batch version. I use the free batch script with 5DtoRGB 1.5.3b.

Has anyone else recently updated to Version 1.5.9 and having issues with some clips freezing near or at the last frame? I purchased the batch version recently and am new to 5DtoRGB. Had no problems with the last batch of clips I processed before this update and then have had a number from a recent shoot that won't process.

Was trying to search this online and read similar problems posted mid last year that seemed to say a similar symptom was a bug that had been fixed in later releases.

(Running 5DtoRGB Batch 1.5.9 64 bit on a Macbook Pro - footage is HBR 25p from GH2 using Quantum X V2 Rocket setting)

Thanks in advance for any tips and will keep looking to see if there's an obvious solution or mistake i'm making.

Hey, it's Thomas. I'm looking into the freezing issue now. This should only be a problem with MTS files. Hopefully I'll have a fix in the next day or so.

I think this needs a bump!

Some say it's useless with Premiere, just use raw MTS instead, some think it grades better. What's everyone's thoughts?

@From_Paris @Brian202020

And for all those, including me, using Final Cut Pro (And since tone doesn't translate well on the web, this is not intended to be angry or snarky, just blunt)

FCPX - When I first got X, I loved the feature of background transcoding so I could begin editing right away, I thought it was the coolest thing ever, till i went to grade the footage. And I have since stopped using the feature, and gone back to transcoding in 5DtoRGB batch. As most of you are aware I'm used to a Logarithmic workflow (a la 35mm film scans) FCP and FCPX cannot deliver this level of quality and color space by itself.

I want a pure image to work with, and while this is exceedingly difficult to get with the AVCHD workflow. 5DtoRGB has consistently delivered high quality, flat gamma images that grade very well. None of the FCP versions have even come close.

If you wanna use the amateur level color correction tools in FCP and FCPX, and will not be doing any external professional level grading, then there is no need for 5DtoRGB. But don't sit there and wonder why your footage can't hang with those using more professional workflows. (Prores, DNxHD, DPX ---> AE or Resolve)

It's your time, your money, your end product, your decision. I'm just here to help you make a more informed one.

@itimjim I can't speak to Premiere, yet. I'll probably go full production bundle on the next upgrade, but the tests I did on unhacked mts files vs. 5DtoRGB produced no discernable difference when using ColorGHear in AFX to grade 5DtoRGB 444 ProRes vs. raw mts. They graded the same.

But with a FCp workflow, 5DtoRGB is the clear winner.