Works for me.Īnyway in the professional field, you don't work alone, so it's quite normal that after editing someone else do the sound editing and mixing in pro tools. This also means that if I need to tweak that stereo master for any reason, Nuendo can easily bounce again over the top of the same master if required, Resolve then updates the new mix in the same Timeline. I can also keep Resolve and Nuendo open together. Works perfectly and without any AAF fuss. Duplicate the timeline and drop in the new audio master. Master and bounce back out as a stereo file into the relevant Resolve media dir at whichever LUFS required.
It imports the movie into a video lane & also drops each 'timeline' into separate audio lanes. Then open this multitrack movie in Nuendo.
I tend to use a little of this just for general balance before doing a full mix in Nuendo.
This also prints any audio work that may have been done on each of the timelines in Resolve, including level changes, fader levels, fx, automation, plugins, whichever. I make as many of these as there are tracks in Resolve (eg, music temp, VO, FX, wild, etc). I avoid the AAF debacle all together by exporting a movie from Resolve at the res /codec I want for best Nuendo playback, and adding multi-track audio as part of that export, ie, instead of selecting the 'main output' stereo option, Resolve can also usefully select 'Timeline' audio tracks. In any case, in the case of round tripping from Resolve Studio to Nuendo: Have found this to be inconsistent /buggy depending on exactly what is going from where to where. I went to FCP 7 and exported the original edited project as OMF and Nuendo is happy as Larry, but of course, I can't use that because I've moved the project forward in resolve.Ĭan anyone shed a ray of light on an interchange workflow that will actually work? I really like resolve and have used it entirely to produce, but just want to use an external DAW for this project without having to go back to the original edit and repeat my work.įWIW, I gave up on AAF (mostly)- on these platforms or others. Nuendo has no hope of importing the output from Resolve. start on the clapper board instead of the marked regions). I have even tried transcoding to Prores and exporting fcpx but then some elements vanish, and some have timing issues (i.e. Logic Pro X however, can, but it can't deal with MXF files. Now with fcpx xml, FCPX seems to bring everything in ok, but obviously incapable of any decent DAW export workflow (either AAF or OMF). I have tried the export to protools, avid AAF, file export=>aaf, even to fcpx xml & re-importing as suggested here. I keep going back & forth creating, rendering, importing etc, so I thought it would make sense to switch the sound design to Nuendo for this project. However, for this project, I am creating many sounds and doing sound design which is outside the scope of fairlight, and I have been doing this in Nuendo. I imported the field recorder sound,I setup all the tracks and set to work pairing separately recorded audio with clips where needed and started balancing dialog, adding atmos, spot fx etc in fairlight. This imported perfectly (more or less) in Davinci resolve. The movie files are all MXF format and the field recorder sound are polywavs. Project was edited in FCP7 and delivered as an fcp.xml. I have tried, Cubase 10.5, Nuendo, and Logic Pro X (and FCPX). I have been trying to do this now for 2 days and am at the end of my tether. Why is this standard interchange workflow such a royal pain in the **** (not just resolve I should add).
For the life of me, I cannot get resolve to reliably export to AAF for use in an external DAW.