Cool, thanks for all the feedback, guys. Just what I needed... J.C.
On Fri, Aug 9, 2013 at 1:54 PM, Howard Jones <[email protected]>wrote: > I get plenty of errors with QTs with bbox not set etc. I would convert > once and be done with them. > > > Howard > > ------------------------------ > *From:* Nathan Rusch <[email protected]> > *To:* Nuke user discussion <[email protected]> > *Sent:* Friday, 9 August 2013, 18:17 > *Subject:* Re: [Nuke-users] Quicktime prores 4444 as source > > In spite of any perceptual performance comparisons, I have to agree > that avoiding Quicktimes is still the best policy. On both OSX and Windows, > Nuke relies on a separate “helper” process to (presumably) handle > encoding/decoding, and I cannot count the number of times this helper > process has gone off the reservation and frozen Nuke (presumably while it’s > waiting for a response of some kind). There are even certain combinations > of upstream nodes that can be used to reliably break the helper when > executing a Write. > > More often than not, 10-bit DPX is still the better choice for plates > (especially if they’re coming through a ProRes intermediate). EXR doesn’t > compress noise/grain well in ZIPS mode (since the compressed blocks are so > narrow), so the file size difference is usually fairly negligible, and > you’re still looking at the CPU decompression overhead on top of that. > > -Nathan > > > *From:* John Coldrick <[email protected]> > *Sent:* Thursday, August 08, 2013 3:56 PM > *To:* Nuke user discussion <[email protected]> > *Subject:* [Nuke-users] Quicktime prores 4444 as source > > Hey all - we typically pull our plates from the above files and output > to dpx files for compositing. Someone here has been pushing for just using > the original quicktimes directly in comp(we've gotten a fix from the latest > release notes that addresses a subtle colour shift between nuke and > compressor). Apart from the arguments about speed(we found in the end it's > actually pretty similar) and workflow(head in and out and the rest we can > probably handle), it struck me that stability is a potential problem. > We're running windows here(win7 64 bit), and I was able to make some > quicktime crashes pretty trivially with Nuke 6.3v4 through 7.0v8(same > triggers, same crash, which suggests the issue is with quicktime). > > I'm arguing no for stability reasons, but I can see the benefits if it > works - just wondering if anyone here has done this with any success or > wildly wave their hands saying 'nooooooo!'. > > Thanks in advance > > J.C. > ------------------------------ > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
