Hi Everyone,
I was wondering if someone could shed some light on an problem I am having.
Ok so I have tracked a scene in nukex's camera tracker and now I want to
export the camera tracking data along with the pointcloud and various
stationary spheres into maya, using the default settings of the
Is there any plan to qualify other linux versions? RHEL 5.4 is over
2 years old now,
In general I like to keep reasonably up-to-date with OS as we
usually need to run a variety of software.
We're on Fedora15 / XFCE, We've had a certain amount of instability,
Actually -
Since then, I've found lots of causes and made lots of fixes to scripts
that have that problem - usually a busted clone, knobs with {} instead
of {{something}}, or a rotoshape bug. In this case however, if that's
really the attached script, there's no saving it - it's been lopped
We’re in the process of testing the F15/XFCE combo to roll out facility-wide
(currently on Fedora 10). I don’t think we’ve run into those same issues after
probably 3 months of testing, and Nuke has been pretty much stable. If you can
recall, are there certain situations where these crashes
One thing we discovered about Nuke’s script parser is if it finds a knob name
but no value, it will grab the next thing it can find in the script file
(usually another knob name) and assign that to the value of the knob. As you
can imagine, this throws off the rest of the script parsing, since
Hi all,
needing to cam track some Red footage. Anybody knows what the film back is,
and if I should change the focal length to compensate for a different size
film back?
Thanks,
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
+972 (0)54 255 9765 [Israel]
url:
Red One 0.96 in
Red Epic 1.0885 in
-
Misho
On 2011.10.10 8:27 PM, Ron Ganbar wrote:
Hi all,
needing to cam track some Red footage. Anybody knows what the film
back is, and if I should change the focal length to compensate for a
different size film back?
Thanks,
Ron Ganbar
email:
It depends which red and which resolution it was shot at. The Red One
crops the sensor to shoot at different resolutions(4.5k, 4k, 3k, 2k).
If you have 6.3 I have them all in my camera presets here:
http://www.nukepedia.com/gizmos/python-scripts/3d/camera-film-back-presets/
-deke
On Mon, Oct
The Red can capture footage in a variety of ways, 4K 16:9, 2K 16:9 etc, and
they all crop the sensor in different ways. To find out what sensor size you
should use, just multiply the pixels of your image by 0.0054 (the size of
the pixels on the sensor in mm).
For example, if the camera captured
I am trying to get node presets to work over a shared network. I can create the
preset localize and it works fine. I then copy the user_preset.py over to my
shared network location and I can see it and it works BUT it still says [user]
under the menu, I expected it to say [shared] or nothing
just change the python command from nuke.setUserPreset to nuke.setPreset.
-deke
On Mon, Oct 10, 2011 at 19:51, bigfella
nuke-users-re...@thefoundry.co.uk wrote:
I am trying to get node presets to work over a shared network. I can create
the preset localize and it works fine. I then copy the
Thanks Deke, That got rid of the user but the shared user_presets.py is still
killing the local version.
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
Just define your preset as something other then user presets.
So instead of:
import nuke
def nodePresetsStartup():
do this:
import nuke
def nodePresetsShared():
If you renamed it to sharedPresets.py and then in your global
init.py or menu.py, just import it like any other python script:
13 matches
Mail list logo
