But the idea is to be able to easily hook up whatever render farm
you have going to extend the off-the-shelve implementation.
On 4/9/14, 12:15 PM, Chris Noellert
wrote:
Damn.
Hi
Gary
At the moment the background render nodes are just on
your local machine so you can saturate your available
resources (frame per core). No external machine support
yet as far as I know.
-deke
On Tuesday, April 8, 2014, Gary Jaeger < g...@corestudio.com>
wrote:
Interesting. I
will be curious to hear how those can be managed to
coexist with, say, our rush render farm so that they
aren’t running into each other.
Not really an actual render farm per
say but what we do is launch a bunch of
background render nodes which lie in wait.
When you open a timeline or modify a comp
they all start rendering frames ahead in the
comp to disk wherever the write nodes are
pointing to. So it's like having an on
demand render farm for your interactive
session.
-deke
On Tuesday, April 8, 2014, Gary Jaeger
< g...@corestudio.com>
wrote:
And
was I imagining things or did the
mention some kind of integrated render
farm solution?
Strikes me that you’re
seeing a pyramid effect of
products where the apex is
Nuke Studio which combines
all the best pieces for the
current editorial/comp
packages. Arguably you have
Nuke and Heiro player on the
bottom row, followed by
NukeX and Heiro on the next
row and toped by NukeStudio.
This is a rather similar
sort of set up that Autodesk
had/has and tends to be one
that facility owners can
quickly grasp. The more
likely you are to have a
client standing over your
shoulder the higher the cost
of the product and the more
all inclusive it becomes.
From the worker-bee
perspective, it’s totally
based on need. Most
compositors aren’t going to
need a full Heiro license
and likewise most effects
editorial folks won’t need a
full Nuke license. From my
perspective Nuke Studio
essentially allows one to
finish a show/commercial in
the same env as your
compositors and using
conventions that just plug
into that environment.
Very clever product.
Very clever.
Best,
Chris
On Apr 8, 2014, at
12:41 PM, Doug Wilkinson
< d...@buck.tv>
wrote:
My INITIAL reaction
is that the
announcement they made
was an upgraded
version of Hiero, with
the ability to run
nukeX as an integrated
engine. This is what
we thought, based on
face to face foundry
meetings, Hiero was
becoming, not nuke. I
think this is a great
announcement, don't
get me wrong! I'm just
very confused by this
announcement and how
The Foundry chose to
label and market this
product.
Some other
questions that I look
forward to being
answered, in time :
Why can't we use
nuke as the engine,
why only nukeX?
(surely only some of
us need the
functionality of nukeX
in this scenario)
What features will
be rolled into Hiero?
What would be the
pricing for current
customers on
maintenance that own
both Hiero and NukeX?
On Tue, Apr 8, 2014
at 7:22 AM, Gary
Jaeger <g...@corestudio.com> wrote:
So
that seems to
overlap quite a
bit with Hiero. Is
Hiero to be
replaced by Nuke
Studio?
We
have the video
up here:
Gary
Jaeger // Core
Studio
249 Princeton
Avenue
______________________________________________
--
--
Deke
Kincaid
Creative
Specialist
The Foundry
Skype: dekekincaid
Tel: (310) 399 4555 - Mobile: (310) 883
4313
_______________________________________________
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
|
