Colinelves
Well-known member
Hello all,
How are people handling the round tripping between edit and grade of the 2K Raw footage? I ask because I've just finished editing* a project shot entirely in 2K Raw (regular speed, as it happens) and I'm really struggling to get Resolve to reconnect to the DNGs properly again.
So far I:
1. Imported the footage into the Resolve media pool and relinked the Wav files.
2. Laid the originals all out in a timeline in resolve, applied the right Raw settings and the 709 LUT (corrected the gamma and exposure in a couple of shots), then exported the timeline as individual clips using the original file names to 422 HQ
3. Brought the 422 exports into FCPX**, synced up the audio files from the mixer as we were running 2 system audio and combined each .mov / audio file as a compound clip for editing.***
3. Edited it all in FCPX (that went smooth enough).
4. Exported the project as an FCPXXML and brought into Resolve.
5. In resolve I added all the original DNGS into the Media pool (I dumped the WAVs as I wasn't using them).
6. Imported the FCPXML into Resolve, unchecking 'automatically import source clips into the media pool' and...
It was a mess. Rather than linking to the right DNGs, Resolve seemed to pick one to build the edit out of. In the end I'm having to go through the edit and force conform each of the cuts to the right clip - and that's after taking the FCPXML into FCP 7 (via Xto7) and cleaning it up.
The whole thing is driving me mad! Any ideas what I'm doing wrong/did wrong earlier? I've check the timecode of the .mov transcodes and the DNG originals and they seem to match, I just can't for the life of me work out why Resolve is doing what it is doing...
*I know, me editing it was a bad place to start, since I'm a DP and don't really know too much about editing (it must be a bit like watching a chimp try and use a typewriter) I honestly do try and avoid it as much as possible, but it was a personal project for a friend...
** that was also a mistake as FCPX really doesn't play nice with other programmes.
*** that was another mistake, as it messed up the export to Xto7 - in the end I had to use X2Pro to create an AAF for the sound editor, lord knows if that worked properly!
How are people handling the round tripping between edit and grade of the 2K Raw footage? I ask because I've just finished editing* a project shot entirely in 2K Raw (regular speed, as it happens) and I'm really struggling to get Resolve to reconnect to the DNGs properly again.
So far I:
1. Imported the footage into the Resolve media pool and relinked the Wav files.
2. Laid the originals all out in a timeline in resolve, applied the right Raw settings and the 709 LUT (corrected the gamma and exposure in a couple of shots), then exported the timeline as individual clips using the original file names to 422 HQ
3. Brought the 422 exports into FCPX**, synced up the audio files from the mixer as we were running 2 system audio and combined each .mov / audio file as a compound clip for editing.***
3. Edited it all in FCPX (that went smooth enough).
4. Exported the project as an FCPXXML and brought into Resolve.
5. In resolve I added all the original DNGS into the Media pool (I dumped the WAVs as I wasn't using them).
6. Imported the FCPXML into Resolve, unchecking 'automatically import source clips into the media pool' and...
It was a mess. Rather than linking to the right DNGs, Resolve seemed to pick one to build the edit out of. In the end I'm having to go through the edit and force conform each of the cuts to the right clip - and that's after taking the FCPXML into FCP 7 (via Xto7) and cleaning it up.
The whole thing is driving me mad! Any ideas what I'm doing wrong/did wrong earlier? I've check the timecode of the .mov transcodes and the DNG originals and they seem to match, I just can't for the life of me work out why Resolve is doing what it is doing...
*I know, me editing it was a bad place to start, since I'm a DP and don't really know too much about editing (it must be a bit like watching a chimp try and use a typewriter) I honestly do try and avoid it as much as possible, but it was a personal project for a friend...
** that was also a mistake as FCPX really doesn't play nice with other programmes.
*** that was another mistake, as it messed up the export to Xto7 - in the end I had to use X2Pro to create an AAF for the sound editor, lord knows if that worked properly!