Well it's nice to know that after 17 years of using Sapphire on 3 compositing
packages it still has to have a crop ;0
Howard
> On 22 Feb 2017, at 5:28 pm, Sven Schönmann wrote:
>
> Finally found the problem. Cropping the image was the right direction. But be
>
Finally found the problem. Cropping the image was the right direction. But
be shure to deselect the "Black Outside" option in the crop (or use a
reformat). Even the one pixel bounding box created by the crop leads to
nonstop crashing on my machine.
Thanks again Howard...you saved me a lot of
Hi Howard,
that might be the trick. I had problems with a specific clip earlier which
was pre-rendered with autocrop. After manually resetting the bounding box
to the full frame it seemed to me that the crashes became less. I'm gonna
check my script about bounding boxes...but that might be it!
Put a crop before the spahirre plugin - the rotos may be changing Bounding
boxes and I’m not convinced Saphirre likes that
Howard Jones
Visual Effects Supervisor
m: 07973 265624 | e: how...@axis-vfx.com | w: www.axis-vfx.com
> On 22 Feb 2017, at 16:21, Sven Schönmann
Hi everyone,
I got massive problems with using the Sapphire OFX plugins in Nuke. Hard
crashing without any error message or something every 2-3 minutes. Using
the versions mentioned in the subject line. Tried also different Nuke
versions and downgraded to Sapphire Version 9.03. Same issues.
Are
Hi all!
Got a serious problem with distortion here. I have a 2.35 footage (= pixel
aspect ratio of 2.0), and I need to undistort the images for a matchmoving
process on SynthEyes. I therefore use NukeX and its LensDistortion plugin. The
issue is, whatever the undistort method we use (Image
On 27 feb 2012, at 16:12, head_in_fire wrote:
I'd like to find a way to calculate the distortion in Nuke itself,
because we later need to re-distort the 3D images to match the live
footage, and we therefore need to re-use the same value that allowed
us to undistort; as a result, I don't
it should be trackable. Did you use any user tracks with foreground
and background targets? You can also do a few planar tracks then use a
checkboard with small squares laid in where you track fore mid and BG.
Do you have the proper gate and lens input?
Randy S. Little
http://www.rslittle.com
The results you are getting is a limitation of the type of camera move you
are doing(nodal pan). The trouble with this type of move is that there
isn't any paralax changes in order to figure out where features are in
depth from the camera. Therefore you get that of wall of pixels. If you
Hi,
what Deke said is spot on... however if you have a few still shots from the
place you could use something like PFTRACk and use all the different shots
to help your camera track and get some depth in the point cloud...
hope this helps
2011/11/26 Deke Kincaid dekekinc...@gmail.com
The
Hello Chris,
Thanks for your response, it helped me figure out my card wasn't to
blameIt's now running smoothly. Being new to Nuke, I found out the hard
way that some nodes don't do exactly what I thought they did and nodes like
Kronos and timeoffset combined with write nodes that are reading
probably not very useful to solve your problem, but i've
been running nuke on a 2008 macpro with 4870 (osx 10.6.8)
for quite a while and didnt see any issue with any recent
version of nuke.
i'm thinking of switching to another card too though as i'd
like to install blackmagic resolve and the
Hi there,
On Mac OS 10.6 how can I start multiple NukeX sessions without using command
line? When in NukeX, pressing Ctrl/Cmd+N loads a new Nuke rather than a
NukeX.
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
+972 (0)54 255 9765 [Israel]
url:
Hi Ron,
It does actually start a new NukeX, there is a bug where it displays
Nuke in the menu bar instead. If you go to About Nuke it should show the
NukeX splash screen and you should still be able to use NukeX features.
Thanks,
Mark
On 03/08/2011 14:25, Ron Ganbar wrote:
Hi there,
On
14 matches
Mail list logo