Brendan Dillon
Forum Replies Created
-
Resolve has an option to split the single clip into multiple clips based on EDL when you do a pre-conform. If this process could also apply the source timecode from the EDL to the clips then c-mode would be possible.
-
[Dean Manion] “I cannot figure out how to get Resolve to recognize and assign the source timecode to the edits.”
Yeah I was hoping Resolve would do this too but apparently not, so the only way to use ‘Source’ (or C-mode) is to conform the EDL, using multiple source clips, in Resolve rather than using a single ‘baked’ clip.
-
You need to add the clips to the ‘AvidMediaFiles’ folder on your media drive then launch Avid. It will scan and index the new media on startup. Then use the ‘Media Tool’ in Avid to find the new clips and drag them into a bin.
-
Not sure why this isn’t working for some, or why the Color workflow is better. I just tell my client to media manage the project to a drive, bring it to my suite – I open the FCP project and export an EDL, add the clips to Resolve, import EDL and start grading.
The FCP project is then linked to the graded footage and all supers, effects (including motion effects) etc are preserved.
It even works with multilayered sequences – layer one will be all the clips in the EDL – grade that sequence first and then any clips left ungraded in the Master Session will be clips from the other layers so grade them in the Master Session and render from there.
-
In FCP media manage your sequence then make an EDL with ‘EDL Notes – File Names’ checked.
In Resolve make sure ‘Extract Reel Names from EDL Comments is on then set “Assist using reel numbers from the source clip file path name’ to */#R
Add all your clips to the media pool – the reel column should show the file name.
Load your EDL and grade the sequence then load the Master Session and Render in ‘Source’ mode.
Relink to the rendered clips in FCP and your sequence is as it was with all motion effects, resizes etc but now, hopefully, with nicer looking pictures.
-
Resolve seems to want Avid MXF as opposed to Avid quicktime. You don’t need the update if you are doing 1:1 – the update only adds DNxHD.
In avid do a ‘Videomixdown’ and select the new clip in the bin, then choose ‘show in finder.’ Take this file into Resolve and off you go.
-
[Blase Theodore] “You mentioned that you got the clip names to work? How did you accomplish that?”
Did I? No – I haven’t had clip names working.
This should not be an Avid ‘Relink’ function. When the rendered files are placed in the Avid MediaFiles folder Avid will scan the drive and the .new clips and the .exported sequence created when exporting the AAF will come online automatically. This can be proven by putting the source files (from the AAF) onto your Avid media drive and instantly Avid will scan the drive and the .exported sequence will come online.
But as I mentioned this is not working with the Resolve files because some metadata has changed – I’m not sure what missing metadata Avid wants – it could be clip name or tape or both or maybe something else.
‘Relink’ will not work because the tape names are gone and ‘key number’ refers to key code on film projects.
For now you may just have to render in ‘Target’ mode. Or, if your project isn’t too big, you could add your rendered MXF clips to the AvidMediaFiles folder and open the Media Tool in Avid, find your new clips and drag them to a bin and start manually cutting them into your sequence. This is probably just as laborious as trying to use an app to manually modify clip metadata and at least manually cutting in the clips will actually work!
I’m sorry but I can’t think of any easy solution to this at the moment.
-
[Blase Theodore] “The actual cause of the import problem is more likely:
– Resolve is creating the wrong “name” metadata, (as you noted)
– Resolve doesn’t seem to want to import Reel names from the EDL or AAF.”Yes I would be guessing this is the problem. The rendered files are similar to the source files but have enough metadata changes for Avid to know that they are not the same file. If these files were the same as the ones generated when exporting the AAF then the .exported sequence would relink automatically once Resolve’s rendered files are placed into the Avid MediaFiles folder.
All the functions are there – Resolve reads the AAF and the MediaFiles folder and renders Avid MXF files but it just doesn’t quite work. This would be such a great workflow and would allow Avid and Resolve to work so well together as a finishing system. I really hope this is looked at for future software updates.
For now I’ve gone back to a ‘Preconform’ workflow.
-
No duration glitch here. Could it be a 29.97 – 30 issue? I notice one of your clips is 29.97 fps and the other is 30. All my material is at 25 and there is no problem with duration and yes I am using the “use prefix, suffix… from source clip”
Regarding getting the clips back into Avid this is how it should work:
Export an AAF and this creates an AvidMediaFiles folder with MXF Media. Also, it creates a new sequence in the bin with .exported and a whole bunch of clips are added to the bin.
As a test If you take the new MXF files and move them into Avid’s ‘AvidMediaFiles’ at the root of the drive, the drive will scan and the .exported timeline will no longer be offline.
Now if the files from Resolve were identical and you instead put the new rendered Resolve files into Avid’s original AvidMediaFiles folder the drive will scan and the .exported sequence would be automatically linked to the graded footage.
Unfortunately the files are close – mine have the same file name, same duration, timecode .. it all looks good but the clip names are always totally different from the original.
In your example ‘071510 g02.02.new.01’ has become ‘TFS071510V01.’ More has changed than just ‘.new’
It appears that instead of keeping the clip name it replaces it with he first 10 characters of the tape name and adds a V01 to the end.
-
I don’t have the frame rate discrepancy that you have but the files still don’t relink in Avid. I’m working at 25fps.
I notice that when the files come out of Resolve the ‘Clip Name’ metadata has changed. In your example ‘071510 g02.02.new.01’ has become ‘TFS071510V01.’ I am guessing that Avid wants to see the same clip name for it to really believe that this is the same file.
I would love to get this workflow happening …