Hej
Just gamma-correct things you want to dissolve: pump up gamma (with "Gamma"
node for instance) before Dissolve - on both inputs- and invert gamma
-correction after dissolve. Values arround '2' and '1/2' will give you Final
Cut Pro -like dissolve but feel free to experiments with this
Adrian Baltowski:
Just remember that with all digital cameras these are arbitrary
logarithmic-like curves applied on top of the linear data captured by the
sensor. Currently I'm working on the Alexa footage: night shot with house on
fire. With AlexaV3logC curve maximum linearized values of fire
is not acceptable for VFX; surely anything is
'acceptable' - even underexposed 8mm... :)
Personally, I'd rather have the stops to play with.
N
Neil Rögnvaldr Scholes www.neilscholes.com On 30/04/14 14:43, Adrian Baltowski
wrote:
Probably you have access to more recent Alexa but with my footages
Just remember that with all digital cameras these are arbitrary
logarithmic-like curves applied on top of the linear data captured by the
sensor. Currently I'm working on the Alexa footage: night shot with house on
fire. With AlexaV3logC curve maximum linearized values of fire are around 36
I did a quick test:
1) import h264 footage from canon 5D to Premiere CS6
2) export dpx seq with default preset: full range
3) import dpx to nuke with colorspace set to sRGB
4) export tiff seq from nuke with default sRGB colorspace
5) import to Premiere and compare to original: color and gamma are
On OSX you have to check in /var/tmp/nuke-u501 folder (or something like
nuke-u5xx) - .autosave file is there.
Spotlight does not search for hidden files by default. Also in Finder You must
enable 'show hidden files' option in plist to get it.
Best
Adrian
W dniu 2014-03-03 02:38:28
Hi
This is a simple python script, which create independent copy of selected
camera. All dependencies, parenting, targets etc. are resolved and recalculated
to standalone Nuke Camera, with baked XYZ. Such a camera You can export with
chan file or fbx or whatever.
Best
Adrian Baltowski
Hi
The math equation used in colorspace node in Nuke assumes, that input signal is
in linear REC709 colorspace but this is not necessarily true. So my advice: try
to use 2 separate colorspace nodes. In the first one set sRGB as in and
REC709 as output and THEN connect the next colorspace node
Mobile: (248) 840-2665
Web: http://richbobo.com/
Man has been endowed with reason, with the power to create, so that he can
add to what he's been given.
- Anton Chekhov
On May 21, 2012, at 6:40 PM, Adrian Baltowski wrote:
Hi
With just few lines of code and totally
Hi
The question is: has your quicktime file the 'pasp' atom but it contains wrong
values OR your file doesn't has any aspect ratio atoms ('pasp' or 'tapt') at
all?
There is small OSX application called Dumpster to inspect and edit quicktime
file's structure. But Dumpster can't add or remove
.
Cheers,
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
+972 (0)54 255 9765 [Israel]
url: http://ronganbar.wordpress.com/
On 2 May 2012 20:36, Adrian Baltowski adrian...@poczta.onet.pl wrote:
Hi
Dumpster is free app. It is available somewhere on apple developer site. I
attached
Hi
Your file is strange. When you open it in Dumpster you find, that timescale and
duration values are inconsistent between movie header atom and track atom and
these values doesn't divide evenly. So it's very likely that file is
misinterpreted in different softwares.
This file was created by
Hi
I want help or advise you something but I don't fully understand your
workflow...
You can of course make color conversion in nuke. Nuke is brilliant software to
make such a conversions BUT What next?? You cannot export layered tiffs out
of Nuke (at least not in usable form). Do you
Hi
There are sample Luma/Chroma images on the exr repository on the exr project
website; shows exactly what happens.
http://www.openexr.com/downloads.html
Generaly speaking: Nuke doesn't support Luma/Chroma encoded exr files. But
problem is more complicated...
Exr libraries provide 2 ways to
Hi
Just one thing to clarify: Nuke psd reader doesn't merge layers from psd file
in any way! While you save layered psd file in Photoshop you have option
Maximize compatibility. When you turn it on, Photoshop merges all active
layers and saves as uncompressed picture into the psd file. And
Hi
Framecycler is 64 bit on Linux and Windows. There is only OSX version of Nuke
shipped with 32 bit Framecycler because 64 bit version of Framecycler for OS X
simply does not exist.
So no reasons to fill bug report or feature request... ;)
Best
W dniu 2012-02-19 08:38:12 użytkownik
A little OT but remember, that in case of native r3d files in Nuke there is a
massive difference between operating systems. On the same hardware (without
rocket card) r3d decoding in Nuke is few times faster on Linux than on OSX.
Also Widows is slower than Linux with this format. There isn't
I wrote psdReader which reads 16 and 32 bits psd files with layers and masks.
It's available on Nukepedia. I will update it for 6.3 soon (unfortunately I
didn't have time to do it so far...).
In general: there is not a bug or weirdness actually. Information about layers
and masks in 16bit and
You encountered old bug in Nuke. When you fetch metadata from movie format
readers (mov, avi, ffmpeg, r3d) Nuke from time to time (quite often) gives
black frame, colorfull noise or shows error messages. In older versions of Nuke
and movReader when this error occurs Nuke shows unhandled pixel
Always when you mean about movs from Alexa remember that in Nuke 6.2 and 6.3
there is no actual 'raw' functionality in movReader.
In older versions of Nuke (up to 6.1 32bit) when you activate raw button,
movReader get values from Quictime's PixelBuffer and copy them directly,
without any
that a
try on our Fedora Core 14 system.
Thanks,
Vincent
On Sat, Jul 23, 2011 at 4:54 AM, Adrian Baltowski adrian...@poczta.onet.pl
wrote:
I suppose that some strange issues on Linux might caused by silent
incompatibility of libstdc++ library used by Nuke instalation.
I had similar
To eliminate flicker you can use old Shake technique with curve tool. In Nuke
there is curveTool node but manual to Nuke is useless in this case. But you can
refer to Shake manual because PixelAnalyzer in Shake and curveTool in Nuke are
similar.
In few words: with curve tool you can
Hey
Formats.tcl file has nothing to do with Reader's aspect ratio. This is only
list of names of formats in Nuke, created for users convenience.
Reader set up format based on info about resolution and aspect ratio of
file. Then Nuke compares the format with the formats.tcl and if format has a
Btw
Trick with order of formats in formats.tcl works but only if Reader don't set
up any aspect ratio.
W dniu 2011-06-23 22:55:03 użytkownik Adrian Baltowski
adrian...@poczta.onet.pl napisał:
Hey
Formats.tcl file has nothing to do with Reader's aspect ratio. This is only
list of names
Hey
First of all: it's possible to keep a controlled workflow with Quicktime
format, and there aren't any specific issues about 10 bit uncompress codec. But
there are mane other things:
1. Which application has generated those files? (Final cut, Avid or something
else), in which format
Hi
In .nuke folder you have file called uistate.ini. This file is automatically
modified by Nuke, but if for some reasons is not and all the time you run new
project you have TMI off, you can modify it manually. Open this file in text
editor and in [ColorPicker] section set:
Most of all: ffmpeg is not available with 64bit OSX version of Nuke. Also
ffmpeg currently has not support for many popular codecs like Prores; ffmpeg is
very useful on Linux as it's better than none, but it's not good solution on
OSX.
Nuke on OSX (32bit version) has native support for mov
On Apr 18, 2011, at 7:11 AM, Jerry Huxtable jerry at thefoundry.co.uk
wrote:
We use QuickTime to read and write QuickTime movies, and always have, so
there's nothing to switch back to. The issue is that due to history of vague
documentation and dodgy codec and host software implementations,
28 matches
Mail list logo
