Nuke can read R3D but I find them to be much slower to work with than just regular old dpx's or exr's. If you have a Hiero -> Nuke workflow, I'd recommend just making dpx files from your R3D's.
On Thu, Sep 18, 2014 at 6:01 PM, John Coldrick <john.coldr...@gmail.com> wrote: > In the past we had experimented using quicktime files directly in Nuke as > source plates and it was pretty much a disaster, unstable, inexplicitly > slow at times, and checking around that was a concession from a number of > shops. Fine in theory, seemed OK, but inevitably when you got to a real > shot, trouble. > > I'm just curious if anyone has had any experience with using R3D files like > this. We'd be working at 4K from a Red Dragon, I'm thinking on the plus > side the compression would make for faster interaction, but potentially on > the negative side some of the snappy scanline efficiencies might be lost, > and of course, stability is key. I've also noticed that the firmware in the > camera can be a real issue in getting successful reads in Nuke, so there's a > thing... > > We're going to do some testing, but just curious if anyone had any war > stories. > > Thanks in advance! > > J.C. > > _______________________________________________ > 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 -- John Mangia 908.616.1796 j...@johnmangia.com _______________________________________________ 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
