premiere generally does very well at reading media metadata correctly. so unless its a specific camera thats causing a problem I'd generally trust premiere.
I take it the edits are done already ? no taking the media, getting it out of that miserable MXF folder / file format via Edit Ready ? in fact what does Edit Ready or even VLC say ?
There is QTchange that will edit MOV metadata and save it back, but that probably doesn't help here.
one weird way to resolve it might be to record TC into a wav file, then match that back to the media files and insert it into the media, then tell resolve to use the TC from the audio ch of that file. would be a long painful process, and the details here would need to be figured out.
if Preimere is giving you good XML that correctly conforms in resolve, I'd not worry so much. it may be possible to take vegas - does it output XML premiere can read ? and conform it in preimere, then output XML from there and into resolve.
another option is to inspect the XML and perhaps manually edit the TC from . to : . any global search and replace will likely not do what you want. however, not having an XML file open there might be other things that can be search and replaced.
no knowing how simple or complex your TL's are, its hard to say whats the least time intense way of fixing this. manual clip slides may still be the easiest way to do it. output a TL from vegas with visible clip TC, lay that into a higher video track in Resolve, shrink it back, then manually slip / slide the live clips in the resolve TL. painful but how I've done stuff like this in the past, indeed from the days of tape editing where youd lay down the original offline edit onto your master tape, then put the shots in.
James Moore wrote:Yes it does look like it could be a drop vs non-drop counting issue and I see no way of getting Resolve to switch between the two for 23.976 fps. If Premiere and Vegas are using a different way of counting nothing could conform properly could it? I've had Premiere XML's conform properly.
I'm wondering if Resolve is using the MXF metadata in the nested directory structure but Premiere and Vegas are not - they appear to be pulling the TC directly from the .mts file. Is there a way, 1.) to see what is in the metadata of a .mts files (outside of Resolve perhaps), and 2.) get Resolve to use the TC in the .mts file itself instead of the separate file?