Grug
Veteran
Interesting comments, Grug. It is always good to hear from people who have actually been hands-on with what they are talking about. I'm not surprised that there was more leeway in the RAW during grading, but like you say, is it worth it? And I still wonder if it really makes a noticable difference in the final graded output of footage that was shot pretty well in the first place. Nothing but some well-shot side-by-side, split-screen testing, that shows a significant difference is going to win me over. I already went through all this with the FS5 and I'm not going to assume anything about the "advantages" of RAW ever again. Just to be clear, I'm not against RAW in general. 99% of everything I shoot with my F55 is 16-bit RAW or XOCN-ST and there is defiintely a difference with those files.
I think you pretty much nail it on the head there Doug. If you've shot (whatever it is) well, and there's no significant grading needed (no secondary correction required at least), then I really don't think it's worth the pain of the Prores Raw workflow.
If the camera offered XAVC Class 480, I don't think I'd even consider the pain of the raw workflow, it would be "good enough" for everything. But the Class 300 is painfully thin. It's okay, but it really is riding the line of being JUST good enough for most things, 300Mbps just isn't enough data to get a thick 4k frame unfortunately. So it breaks down sooner than I can really trust for a high-quality master.
We've been recording XAVC as a backup to the raw files the whole shoot, and have had a couple of shots where the 10-bit files have broken up into some plainly visible banding in smooth gradients like sky, or plainly-painted walls. At the same time, we've had a couple of shots were we have some unusable moire in clothing fabrics in the raw footage, but the XAVC versions of those same clips don't show up the moire... so you almost want to have both running at all times, just in case - it's pretty irrating.
If you're on FCP, why is the workflow horrendous and awful?
Because FCPX is just to transcode the raw footage into Prores4444 to then send on to our post house. One of the great horrors of the Prores Raw workflow at present, is that some (possibly most) of the trancoding options for the footage, can't actually do accurate transforms to SLOG3/Sgamut3.cine - Compressor being the most obvious culprit. Also the metadata on E.I. values only partially travels through with the footage. So the risks of an assistant editor possibly processing a clip incorrectly, and assigning the wrong ISO value to the exported Prores4444 master is too high to risk.
It's one of the real head scratchers with Prores Raw. It works fine in some NLEs, but it's godawful for any traditional post workflow unless your post house is using Assimilate Scratch (and there's not a single post house I know of in my city that does). So you've got this raw codec that works well for people shooting and editing their own material, but not for conventional workflows - and projects that are shot and edited by the same person, are (generally) the kinds of projects that have the least-demanding final deliverables - and therefore have the least need for the higher overall image quality that the raw recordings can offer.
I really don't get it.
Every other raw codec I've worked with, we're able to open in Davinci, export proxies, and call it a day (the raw files coming back into play just for the colour grade) - no need to strike new masters, and then transcode the new masters into proxies just to get a smooth workflow for post.
