, 2011 10:09 AM
Subject: Re: [Nuke-users] LUT global location, variable(s)???
Yes, that is the module that you need to override. By setting RV_SUPPORT_PATH
to a location of your choosing, and copying the same structure that the
rvPackages file structure has, with an overriden source_setup.mu
discussion nuke-users@support.thefoundry.co.uk
Sent: Saturday, October 8, 2011 2:28 AM
Subject: Re: [Nuke-users] LUT global location, variable(s)???
I don't recall the software that wrote them in the past but I have a mistrust
of the metadata from DPX. We also do things like log/logc/panalog jpegs
, October 8, 2011 2:28 AM
*Subject:* Re: [Nuke-users] LUT global location, variable(s)???
I don't recall the software that wrote them in the past but I have a
mistrust of the metadata from DPX. We also do things like log/logc/panalog
jpegs for quick reviews where the file type or metadata might
. And obviously
being able to roll your own extensions is a huge benefit for review tools,
LUT repositories, etc.
-Nathan
From: Dan Walker
Sent: Thursday, October 06, 2011 10:52 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] LUT global location, variable(s)???
Not too sure what else
:52 AM
*To:* Nuke user discussion nuke-users@support.thefoundry.co.uk
*Subject:* Re: [Nuke-users] LUT global location, variable(s)???
*Not too sure what else you were looking for really. *
Being able to control configuration settings on a piece of software (eg.
FrameCycler) without having
I was under the assumption that the GS file needed to stay local to the
system nuke/framecycler resided on. If this isn't the case then the docs
weren't clear on putting this file in a network configured location.
Care to share your flipbook code?
:-)
Thanks,
Dan
On Oct 7, 2011 12:44 PM, Lewis
user discussion
Subject: Re: [Nuke-users] LUT global location,
variable(s)???
Not
too sure what else you were looking for really.
Being able to
control configuration settings on a piece of software (eg. FrameCycler) without
having to copy something to the software's native location (per
/Administrator (which hopefully you have).
-Nathan
From: Dave Goodbourn
Sent: Tuesday, October 04, 2011 3:28 PM
To: Nuke user discussion
Subject: Re: [Nuke-users] LUT global location, variable(s)???
Now that all depends on your definition of quick! Once you have a software
distribution system setup
06, 2011 10:52 AM
*To:* Nuke user discussion nuke-users@support.thefoundry.co.uk
*Subject:* Re: [Nuke-users] LUT global location, variable(s)???
*Not too sure what else you were looking for really. *
Being able to control configuration settings on a piece of software (eg.
FrameCycler
things like in-line modifications to the
built-in menus (which is still a pretty clunky process).
-Nathan
From: Dan Walker
Sent: Thursday, October 06, 2011 7:25 PM
To: Nuke user discussion
Subject: Re: [Nuke-users] LUT global location, variable(s)???
Yeah, we use RV to and I've already
There are many different approaches:
Here is one:
- you will probably want to have you software installed in a central location
in the networks, so you only modify the settings once
- put the luts in a location all software can see. (ie: ../luts/nuke/
../framecycler ../rv)
- generate the
Have you looked at software deployment software like WPKG http://wpkg.org/ at
all? You can very easily deploy all the settings and environmental variables
to all your machines from the comfort of your own seat! Works well for us.
It's only Windows based but there's plenty of *nix solutions like
Wow, no quick solutions? That just sucks now don't it! :-)
On Oct 4, 2011 10:27 AM, Dave Goodbourn dave.goodbo...@u-fx.co.uk wrote:
Have you looked at software deployment software like WPKG
http://wpkg.org/ at
all? You can very easily deploy all the settings and environmental
variables
to all
Now that all depends on your definition of quick! Once you have a software
distribution system setup, making any change to 100+ workstations and render
nodes can only take a matter of minutes!
You can always do it with scripting to copy config files and setup variables
on each machine. Not too
14 matches
Mail list logo
