If you do them, the shot imagery is being managed by Resolve and supplied to Fusion, while if you don't, the shot is being loaded directly by Fusion. The impact of doing or not doing the two optional steps is not obvious. If you anticipate doing this repeatedly, you may want to lay out the nodes in Fusion to make this easy.
If you later update the tracking, you can export from SynthEyes again, then delete the SynthEyes-originated nodes, paste again, and re-wire as needed. You'll now be able to see the output of the Fusion comp in Resolve, and you can add elements etc in the Fusion comp. You can then delete the original loader node.ġ0. ( Optional, use if optional step was performed above).Ĭonnect the MediaIn1 node's output to the input of Camera01 (or equivalent). Connect the Camera01Renderer node (or corresponding name from your scene) to the input of the MediaOut1 node.ĩ. In the Fusion Page, right-click and select Paste.Ĩ. (Optional) If the shot being matchmoved is already in the Media Pool, drag it into the Fusion Page, or add it to the Media Pool and drag it into the Fusion Page.ħ. In your Resolve project, create a new Fusion comp by right-clicking in the Media Pool area and selecting New Fusion Composition.Ħ. Turn on the exporter's "Export to clipboard?" checkbox (crucial!).ĥ. Configure its options as described and desired in theģ. In SynthEyes, after you've tracked and solved the shot, start File/Export/Fusion/Fusion Composition.Ģ. Using SynthEyes with Resolve 15 by Andrew Hazelden.ġ. Fortunately, there's a relatively easy workaround: pasting it. ) Because Resolve uses a closed internal database to store projects, instead of files, it's more difficult to get information into the project files. (See the separate section on Fusion for the Fusion exporter controls Blackmagic Design's Davinci Resolve contains an embedded version of Fusion.
0 kommentar(er)
