[jim bachalo] “Is this considered a ‘normal’ workflow?
ie as a best practice should you normally use Resolve for ingesting source files and creating your offline media for editing?”
Best practice is to adopt an E-E workflow that makes everybody’s job seamless. That will vary, depending on everyone’s preferences — what camera you are shooting with, what codec it produces, where the dailies are going and what the best format will be for storage, data throughput, and re-conform in the edit process. If we could do everything RAW/unconverted with a native camera codec, that would be the most straightforward, but we seem to be actually going in the opposite direction to that, because we need different data densities at different stages to cope with up- and down-scale platforms, where codecs that are fine in one instance are non-starters in others. Easy to say “4K”, but that’s without doing the math.
Resolve is one of the most platform-agnostic solutions available at the moment, dealing with most codecs, coughing up all kinds of edit descriptors — XMLs, EDLs, AAFs… Mostly where things go off the rails is when someone decides to get creative and is either ignorant of, or ignores the rules about the interchange and pass-through conventions. Not everything works the way “they” say it does in the brochure, but leaping off a cliff with an umbrella (because, in theory, its not that different from a parachute) is not going to be without its own set of adventures.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.