There's still a little functionality missing in the exchange between Fusion and Resolve. I think there's already some efforts going on in the community to script some solutions to that. I've got my hands a bit full, but here are some script snippets:
- Code: Select all
for i, tool in ipairs(composition:GetToolList(false, "Loader")) do
dummy = composition:AddTool("Fields")
dummy:SetData("filepath", tool.Clip[fu.TIME_UNDEFINED])
end
- Code: Select all
-- This is untested. Resolve is quite crashy for me on Win7, so I didn't even try.
for i, tool in ipairs(composition:GetToolList(false, "Fields")) do
filein = composition:AddTool("MediaIn")
filein.Clip = tool:GetData("filepath")
end
I'm not sure what the actual clip field for a MediaIn node is, and it's possible you'd need to add it to the Media Pool somehow rather than adding it directly to the Fusion Flow.
You'd also want to connect the Fields nodes into the flow at the appropriate place, just downstream of each Loader and reconnect the MediaIns to them on the Resolve end. I used Fields because it's fairly unlikely to be in use these days, so the script probably won't find any spurious nodes without custom data.
Savers are another story. At the moment, and as far as I am aware (my knowledge is admittedly limited), the only valid output from a ReFusion Flow is the single MediaOut node that leads back into the Edit Timeline, so there's no reason to mess around with converting Savers at this point.
Regarding your second issue, a Fusion Flow can't exist without an associated clip on the Timeline. Put your plate in the Media Pool, and add it to the timeline. Then you should be able to import a Fusion comp, with the previously noted errors on your Loaders and Savers.