buh why? Why aren't the shots just going back into an edit that already has the sound? Why does the sound need to be in the MOV or whatever wrapper?.
Randy S. Little http://www.rslittle.com/ http://www.imdb.com/name/nm2325729/ On Wed, May 25, 2016 at 8:37 AM, Michael Hodges <mhod...@morganfalls.com> wrote: > I’m creating a series of automation tasks using Nuke to append a series of > image sequence clips (along with some predetermined image manipulations) > whose sources may change depending on the artist's environment. > > These would automatically be written out on the farm and processed for > review. > > The only issue is that some of the clips may have corresponding .wav audio > which can’t be written out within nuke for the final render. > > > My solution is to offset any pre-existing audio .wavs (located in the Read > paths with the same base name as the image sequences) by the corresponding > Append lastFrame count and then run a ffMpeg render-time callback to merge > those wavs (based on the offsets and descriptions generated by the script) > to a new file that is read by the farm > > > > Before I start from scratch I thought I’d see if there were any existing > FFmpeg nodes/gizmos/code out there that assists with FFmpeg manipulation or > writes within Nuke. I didn’t see anything on Nukepedia but I figured that > it would be good to check here > first._______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
