Jamie LeJeune wrote:If the file frame rates of those clips were reinterpreted in the Premiere browser (usually done to conform files that were shot over or under crank), you'll need to manually set the same frame rate interpretation on those clips in the Resolve media pool. I can't say that's the cause of your error message, but that was the solution for me the last time I had that message.
None of those clips were over or under cranked, so in theory that shouldn't be a problem... but this isn't what I'd call high grade software. This process just seems to get worse with every Premiere iteration.
I'd say the FCPX to Resolve interchange isn't just a little bit better, it's actually light years ahead of where things are at with Avid and Premiere. I kicked out an XML from a FCPX sequence delivered to me the other day, and it came into Resolve completely intact -- speed changes, text, stills, transitions, even the compound clips came across. It was flawless. I've never once even come close to that experience with an XML from Premiere or an AAF from Avid (and that's assuming Avid will even allow an AAF to be exported, as many times it simply won't, but that's another story...)
I have yet to get any export from Premiere that wasn't hosed in some fashion in the process. Even a baked edit ended up being a royal pain, since the colors were so totally hosed in the render that there wasn't enough left to recover them... I've been forced to retrieve and restore the original files into the conformed timeline because entire scenes were mangled, even though the originals look fine. And it's random; some clips translated from original to render without a hitch, and others are so far off that at least one channel is clipped rather badly. I don't get it.