Page 1 of 1

Premier to Resolve 16.2.8

PostPosted: Thu Feb 11, 2021 1:41 pm
by lushretouch
Hi,

Im importing an xml into Resolve from Premier.
And its doesn't work this time, all the media is in wrong place/timecode.
Checking against the reference, its a different movie...
I change the timecode to match Premier but it doesn't work either. :(
Anyone else got the problem?

Only roundtrip is to receive a proresfile and do cutscene detection.

Re: Premier to Resolve 16.2.8

PostPosted: Fri Feb 12, 2021 3:08 am
by Uli Plank
Do your originals have proper TC? Are they mp4?

Re: Premier to Resolve 16.2.8

PostPosted: Fri Feb 12, 2021 3:27 am
by Marc Wielage
Our Premiere -> Resolve methodology:

1. Project must be “flattened” to no more than 2 video tracks, if possible. Use the minimum amount of tracks and delete all empty tracks.

2. Remove any color effects, LUTs, or tints from the timeline.

3.​ (OPTIONAL)​ Feature-length projects (greater than 1 hour) should be broken down by 20-minute timelines (“virtual reels”), split according to logical scene changes (day/night, different locations, etc.). This will help minimize delays and issues with possible editorial changes.

4. Project must be set to “​Default Scale to Frame Size​” prior to XML export.

5. Speed changes may not be correctly handled – notes (via markers) should be provided indicating if speed ramps or changes have to manually done per shot. Another option - You can use the ​“Render & Replace”​ functionality to “burn in” the speed ramp, using the select “include video effects” option.

6. Any compound, subsequences, subclip or clips must be committed or rendered down to a single clip. “Render & Replace” can also be used here.

7. Composites should be provided as uncorrected ProRes 422HQ files or as background plates for later compositing by the VFX artist. LUTs can be provided to give the VFX department guidelines for overall color.

8. Multicam clips must be “flattened” / reduced to a single clip. Premiere’s “Render & Replace” functionality can also be used here.

9. Audio tracks must be removed from the timeline. Colorist will need a single flattened stereo track as reference only; this can be provided with the reference video.

10. Reference video burn-in windows should be set up as follows:

Upper Left: source file name + source timecode.
Center top = production co.
Upper right = Version.
Lower left = record timecode.
Lower center = Project name / version # / date.

All windows small (approx. 25pt), black boxes, white fonts.

Embedded record timecode must be identical to displayed vis timecode. Acceptable file formats for the reference file include ProRes 422 LT or DNxHD36, NOT H.264.

12. The reference movie should reflect the intended framing and cropping/reframing of every shot. We will need an email in writing that notes the expected framerate, composition, aspect ratio, and pixel size (HD / 2K / 4K) of the delivered project.

13. The reference movie should also reflect the temporary color of the film as determined during editing or production. LUTs or looks can give the colorist a general idea as to the direction of final color. A rough scratch mix (mono or stereo) can be included if possible.

-------------------------------------------------------

H.264 and other non-timecoded sources are problematic for post because of filename conflicts and lack of reliable timecode.

Re: Premier to Resolve 16.2.8

PostPosted: Fri Feb 12, 2021 7:23 am
by Tero Ahlfors
I'd guess that someone changed the timecodes from the interpret footage settings in Premiere or they are H264 files that have some sort of timecode but it only works in certain programs. AFAIK Resolve doesn't read H264 timecode whereas Premiere does.

Re: Premier to Resolve 16.2.8

PostPosted: Fri Feb 12, 2021 7:39 am
by Uli Plank
Resolve reads TC in MOV and MXF, but not in every MP4. I'd try to re-wrap if that is the case.
(Always test your workflow before starting a project.)