room for instability by getting third-party
libraries involved.
I would stick with DPXs.
-Nathan
*From:* John Coldrick john.coldr...@gmail.com
*Sent:* Thursday, September 18, 2014 3:01 PM
*To:* Nuke user discussion nuke-users@support.thefoundry.co.uk
*Subject:* [Nuke-users] R3D Live
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
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
: Thursday, September 18, 2014 3:01 PM
To: Nuke user discussion
Subject: [Nuke-users] R3D Live source plates in Nuke
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
@support.thefoundry.co.uk
*Subject:* [Nuke-users] R3D Live source plates in Nuke
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
:* Thursday, September 18, 2014 3:01 PM
*To:* Nuke user discussion
mailto:nuke-users@support.thefoundry.co.uk
*Subject:* [Nuke-users] R3D Live source plates in Nuke
In the past we had experimented using quicktime files directly in
Nuke as source plates and it was pretty much a disaster
*Subject:* [Nuke-users] R3D Live source plates in Nuke
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
