[Nuke-users] Re: Opaque roto projections.
That worked a treat! Thanks so much, greatly appreciated! Tim ___ 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] How to check zip compression type for EXR images...?
Hi, Anyone know a quick way to check EXR images to see if they were saved as 16-scanline zips or single-scanline zips? ViewMetaData reveals nothing about the compression type. I'm sure there's a command line invocation that will show more - I just can't find it... Thanks for any help, Rich Rich Bobo Senior VFX Compositor Mobile: (248) 840-2665 Web: http://richbobo.com/ ___ 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
Re: [Nuke-users] Resolution/Screens for HD compositing
I'm a big fan of 27 inch displays (2560x) such as the one dell does, or the apple one, which is quite glossy though... On Tue, May 22, 2012 at 11:46 AM, KiboOst nuke-users-re...@thefoundry.co.uk wrote: Iya folks ! What do you prefer to do compositing on HD 1080p footages ? Dual 1920x1600 screens, one 2560x1600 screen, etc ? What give you the more freedom and UI space while compositing with viewer at 1:1 ? Thks RD/Technical Director | www.kreaction.com i7 3930K, 16Gb, GTX 580 3Go, SSD cache, win 7 pro x64 ___ 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
Re: [Nuke-users] How to check zip compression type for EXR images...?
the only way i found to do this was by launching a subprocess for exrinfo and then parsing through the piped output. if anyone knows of a simpler way i'd love to hear it. -josh On Mon, May 21, 2012 at 7:14 PM, Rich Bobo rich.b...@armstrong-white.com wrote: Hi, Anyone know a quick way to check EXR images to see if they were saved as 16-scanline zips or single-scanline zips? ViewMetaData reveals nothing about the compression type. I'm sure there's a command line invocation that will show more - I just can't find it... Thanks for any help, Rich Rich Bobo Senior VFX Compositor Mobile: (248) 840-2665 Web: http://richbobo.com/ ___ 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
[Nuke-users] Re: Deep Images coming from Houdini
I had a chance to put together an open source RAT readers for Nuke. They are not particularly tested at the moment, but at least ready to be tested. I haven't compiled it on Windows nor OSX (there seems to be an issue on Windows caused by VStudio mismatch between Nuke and Houdini), but plugins seem to compile and work well on 64bit Linux under Nuke6.3v2 and Houdini12.0.6xx. Let me know if you face any problems or would like to commit fixes etc. Unfortunately I'm not like deep into deep compositing, so I may have some total misconceptions about metadatas or readers' logic. Comments are welcomed! http://code.google.com/p/rat4nuke cheers, skk. ___ 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
Re: [Nuke-users] How to check zip compression type for EXR images...?
Hmm... Just tried upping the header size with the EXRs I have and got your code
to start working again when I raised the header search size to 4096.
Rich
On May 22, 2012, at 9:15 AM, Rich Bobo wrote:
Adrian,
I just did a few more tests after getting to work and had less success than
my initial testing last night. I'm guessing that the location of the
compression flag will change, based on other header data and the space it
takes up? You had very specific index locations in your sample code. How did
you determine how far to look? Would a larger header size be more likely to
work with files that are larger and that have more channels? Sorry for the
dumb questions - I have a an intuitive grasp of how this is working, but no
experience with it...
Thanks,
Rich
On May 21, 2012, at 6:40 PM, Adrian Baltowski wrote:
Hi
With just few lines of code and totally simplified
**
compList = ['None', 'RLE', 'ZIP', 'ZIP 16 lines', 'PIZ', 'PXR24', 'B44',
'B44A']
n = nuke.selectedNode()
file = nuke.filename(n, nuke.REPLACE)
fd = open(file, 'rb')
header = fd.read(1024)
index = header.find('compression')
comp =ord(header[(index+28):(index+29)])
print compList[comp]
***
Each exr file MUST have compression info in the header and this info is
placed just after channels info. It's simple to get actual size of channels
list but I quickly set 1024 bytes of a headroom.
Best
Adrian
W dniu 2012-05-21 21:04:38 użytkownik Rich Bobo richb...@mac.com napisał:
On May 21, 2012, at 3:00 PM, Nathan Rusch wrote:
The OpenEXR utilities are pretty nice to have around, especially exrheader.
Sounds like it might be worth a look for you.
exrheader /path/to/input/image.exr | grep compression
Yep. I'll have a look, when I get a bit of extra time to experiment...
Thanks!
Rich
-Nathan
From: Rich Bobo
Sent: Monday, May 21, 2012 11:53 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] How to check zip compression type for EXR
images...?
Thanks, Nathan. Looks like more trouble than it's worth. I tried a down and
dirty 'strings path | grep compress | more' and came up with two instances
of the word compression, but no other info. So, I guess I'll just use the
Does it take lots longer to cache? testing method! ;^)
Rich
On May 21, 2012, at 2:37 PM, Nathan Rusch wrote:
No, it isn’t.
Depending on the context from which you need to check the compression
scheme, if Python proves too unwieldy, you could also resort to
parsing/pattern-matching the output of the exrheader executable.
-Nathan
From: Rich Bobo
Sent: Monday, May 21, 2012 11:32 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] How to check zip compression type for EXR
images...?
I found this reference and it looks like the OpenEXR module would have what
I need, but I'm not sure if it's part of Nuke's Python installation or not...
http://excamera.com/articles/26/doc/openexr.html
Rich
On May 21, 2012, at 2:24 PM, Rich Bobo wrote:
Hi,
Anyone know a quick way to check EXR images to see if they were saved as
16-scanline zips or single-scanline zips? ViewMetaData reveals nothing
about the compression type. I'm sure there's a command line invocation that
will show more - I just can't find it...
Thanks for any help,
Rich
Rich Bobo
Senior VFX Compositor
Mobile: (248) 840-2665
Web: http://richbobo.com/
___
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
___
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
___
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
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
Re: [Nuke-users] Re: Resolution/Screens for HD compositing
i've been using the mac and dell screens, and prefer the dell's. The mac screens look amazing, but they tend to be as reflective as a full on mirror if you're not in a completely dark room :( On Tue, May 22, 2012 at 2:14 PM, KiboOst nuke-users-re...@thefoundry.co.uk wrote: And can you use Nuke on one 2560x monitor with viewer at 100% ? anough place for nuke UI/tools/schem etc ? Could I ask a screen ? RD/Technical Director | www.kreaction.com i7 3930K, 16Gb, GTX 580 3Go, SSD cache, win 7 pro x64 ___ 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
[Nuke-users] Nuke crash on OSX when quitting or closing project
Almost every time when I quit nuke or close a current project nuke crashes on me after all windows are closed. I have a clean install of OS X 10.7.4 and nuke6.3v6 running. I also had this behaviour with 10.7.3. This occurs on my Mac Pro as well as my MacBook Pro. I cannot seem to find any other reference to this problem. Any ideas? Thanks. brave rabbit | Mac Pro 2.4 GHz 8 Core | ATI Radeon HD 5870 | 12 GB RAM | OS X 10.7.4 ___ 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
Re: [Nuke-users] Nuke crash on OSX when quitting or closing project
On 22/05/2012 15:25, iclemens wrote: Almost every time when I quit nuke or close a current project nuke crashes on me after all windows are closed. I have a clean install of OS X 10.7.4 and nuke6.3v6 running. I also had this behaviour with 10.7.3. This occurs on my Mac Pro as well as my MacBook Pro. I cannot seem to find any other reference to this problem. Any ideas? Hello, This was filed as bug 20550 and fixed for 6.3v7. It should be noted that OS X Lion is not an officially supported platform. We would of course recommend you only use Nuke on supported platforms but if you do encounter any bugs on Lion, let support know. Thanks, Wouter -- Wouter Klouwen, Software Engineer The Foundry, 6th Floor, Comms Building, 48 Leicester Sq, London WC2H LT Tel: +442079686828 • Fax: +4420 79308906 • thefoundry.co.uk The Foundry Visionmongers Ltd • Reg.d in England and Wales No: 4642027 ___ 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] Re: Nuke crash on OSX when quitting or closing project
Thanks for the info Wouter. Really appreciated. I guessed that this might be related to incompatibilities and I noted that Lion is officially it not supported. But if there is light on the horizon I am good here. Thanks alot. brave rabbit | Mac Pro 2.4 GHz 8 Core | ATI Radeon HD 5870 | 12 GB RAM | OS X 10.7.4 ___ 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
Re: [Nuke-users] How to check zip compression type for EXR images...?
This is great! Can you let us know what index number the datatype is
in? I'm finding it hard to tell.
thx
Dan
On Mon, May 21, 2012 at 7:30 PM, Richard Bobo richb...@mac.com wrote:
Adrian,
Brilliant - I'll be making it into a nice little pulldown menu utility
function! And, looking a bit deeper at your code, of course, so I can learn
some more Python... 8^)
Thanks!
Rich
Rich Bobo
Senior VFX Compositor
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 simplified
**
compList = ['None', 'RLE', 'ZIP', 'ZIP 16 lines', 'PIZ', 'PXR24', 'B44',
'B44A']
n = nuke.selectedNode()
file = nuke.filename(n, nuke.REPLACE)
fd = open(file, 'rb')
header = fd.read(1024)
index = header.find('compression')
comp =ord(header[(index+28):(index+29)])
print compList[comp]
***
Each exr file MUST have compression info in the header and this info is
placed just after channels info. It's simple to get actual size of channels
list but I quickly set 1024 bytes of a headroom.
Best
Adrian
W dniu 2012-05-21 21:04:38 użytkownik Rich Bobo richb...@mac.com napisał:
On May 21, 2012, at 3:00 PM, Nathan Rusch wrote:
The OpenEXR utilities are pretty nice to have around, especially exrheader.
Sounds like it might be worth a look for you.
exrheader /path/to/input/image.exr | grep compression
Yep. I'll have a look, when I get a bit of extra time to experiment...
Thanks!
Rich
-Nathan
From: Rich Bobo
Sent: Monday, May 21, 2012 11:53 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] How to check zip compression type for EXR
images...?
Thanks, Nathan. Looks like more trouble than it's worth. I tried a down and
dirty 'strings path | grep compress | more' and came up with two instances
of the word compression, but no other info. So, I guess I'll just use the
Does it take lots longer to cache? testing method! ;^)
Rich
On May 21, 2012, at 2:37 PM, Nathan Rusch wrote:
No, it isn't.
Depending on the context from which you need to check the compression
scheme, if Python proves too unwieldy, you could also resort to
parsing/pattern-matching the output of the exrheader executable.
-Nathan
From: Rich Bobo
Sent: Monday, May 21, 2012 11:32 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] How to check zip compression type for EXR
images...?
I found this reference and it looks like the OpenEXR module would have what
I need, but I'm not sure if it's part of Nuke's Python installation or
not...
http://excamera.com/articles/26/doc/openexr.html
Rich
On May 21, 2012, at 2:24 PM, Rich Bobo wrote:
Hi,
Anyone know a quick way to check EXR images to see if they were saved as
16-scanline zips or single-scanline zips? ViewMetaData reveals nothing
about the compression type. I'm sure there's a command line invocation that
will show more - I just can't find it...
Thanks for any help,
Rich
Rich Bobo
Senior VFX Compositor
Mobile: (248) 840-2665
Web: http://richbobo.com/
___
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
___
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
___
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
___
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/
Re: [Nuke-users] How to check zip compression type for EXR images...?
The compression attribute will be in a different place within the header
depending on the number of channels in the file (due to the layout of the
EXR header).
Adrian's snippet is simply finding the 'compression' attribute name within
the header, since that is one of the standard EXR attributes. From there,
based on known information about the EXR file layout, he can determine where
the actual compression attribute value is stored.
The read size of 1024 is pretty much an arbitrary value; you may need to
read a larger chunk in order to get far enough into the file to locate the
compression attribute if your file has a lot of channels. If you know the
names of all the channels within the file, you could figure out exactly how
many bytes to read, or even start your read from a predefined offset to keep
your data buffer as small as possible; otherwise, you'll just need to make a
safe estimate.
Check out this doc for a nice simple example of the structure of an EXR
file: http://www.openexr.com/openexrfilelayout.pdf
Hope this helps.
-Nathan
-Original Message-
From: Dan Rosen
Sent: Tuesday, May 22, 2012 9:59 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] How to check zip compression type for EXR
images...?
This is great! Can you let us know what index number the datatype is
in? I'm finding it hard to tell.
thx
Dan
On Mon, May 21, 2012 at 7:30 PM, Richard Bobo richb...@mac.com wrote:
Adrian,
Brilliant - I'll be making it into a nice little pulldown menu utility
function! And, looking a bit deeper at your code, of course, so I can
learn
some more Python... 8^)
Thanks!
Rich
Rich Bobo
Senior VFX Compositor
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 simplified
**
compList = ['None', 'RLE', 'ZIP', 'ZIP 16 lines', 'PIZ', 'PXR24', 'B44',
'B44A']
n = nuke.selectedNode()
file = nuke.filename(n, nuke.REPLACE)
fd = open(file, 'rb')
header = fd.read(1024)
index = header.find('compression')
comp =ord(header[(index+28):(index+29)])
print compList[comp]
***
Each exr file MUST have compression info in the header and this info is
placed just after channels info. It's simple to get actual size of
channels
list but I quickly set 1024 bytes of a headroom.
Best
Adrian
___
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
Re: [Nuke-users] How to check zip compression type for EXR images...?
OK, I have something that seems to work really well, at least in my test
cases... It has some checks for whether or not you have any nodes selected, if
it's a Read node and if it's an EXR file. After that, I used Adrian's code -
after bumping up the header size to search - from 1024 to 4096. I don't know
how to check to see how big the header really is, so I tried 2048, which still
didn't work for my EXRs, and then finally bumped it to 4096, which is now
working...
Function to test EXR file Compression scheme...
def exrCompressionTest():
compressList = ['None', 'RLE', 'ZIP', 'ZIP 16 lines', 'PIZ', 'PXR24',
'B44', 'B44A']
try:
n = nuke.selectedNode()
if nuke.selectedNode().Class()!='Read' or nuke.selectedNode()
== :
nuke.message('No Read node selected.')
elif
os.path.splitext(nuke.filename(nuke.selectedNode()))[-1]!=.exr :
nuke.message('Selected Read is not an EXR')
else:
file = nuke.filename(n, nuke.REPLACE)
fd = open(file, 'rb')
header = fd.read(4096)
index = header.find('compression')
comp =ord(header[(index+28):(index+29)])
compressMethod = compressList[comp]
print compressMethod
nuke.message('EXR compression is %s' %(compressMethod))
except ValueError:
nuke.message('Please select a Read node...')
...I added a new menu item for the function to my utilities menu and it's
working great, so far!
Rich
Rich Bobo
Senior VFX Compositor
Mobile: (248) 840-2665
Web: http://richbobo.com/
On May 22, 2012, at 12:59 PM, Dan Rosen wrote:
This is great! Can you let us know what index number the datatype is
in? I'm finding it hard to tell.
thx
Dan
On Mon, May 21, 2012 at 7:30 PM, Richard Bobo richb...@mac.com wrote:
Adrian,
Brilliant - I'll be making it into a nice little pulldown menu utility
function! And, looking a bit deeper at your code, of course, so I can learn
some more Python... 8^)
Thanks!
Rich
Rich Bobo
Senior VFX Compositor
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 simplified
**
compList = ['None', 'RLE', 'ZIP', 'ZIP 16 lines', 'PIZ', 'PXR24', 'B44',
'B44A']
n = nuke.selectedNode()
file = nuke.filename(n, nuke.REPLACE)
fd = open(file, 'rb')
header = fd.read(1024)
index = header.find('compression')
comp =ord(header[(index+28):(index+29)])
print compList[comp]
***
Each exr file MUST have compression info in the header and this info is
placed just after channels info. It's simple to get actual size of channels
list but I quickly set 1024 bytes of a headroom.
Best
Adrian
W dniu 2012-05-21 21:04:38 użytkownik Rich Bobo richb...@mac.com napisał:
On May 21, 2012, at 3:00 PM, Nathan Rusch wrote:
The OpenEXR utilities are pretty nice to have around, especially exrheader.
Sounds like it might be worth a look for you.
exrheader /path/to/input/image.exr | grep compression
Yep. I'll have a look, when I get a bit of extra time to experiment...
Thanks!
Rich
-Nathan
From: Rich Bobo
Sent: Monday, May 21, 2012 11:53 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] How to check zip compression type for EXR
images...?
Thanks, Nathan. Looks like more trouble than it's worth. I tried a down and
dirty 'strings path | grep compress | more' and came up with two instances
of the word compression, but no other info. So, I guess I'll just use the
Does it take lots longer to cache? testing method! ;^)
Rich
On May 21, 2012, at 2:37 PM, Nathan Rusch wrote:
No, it isn't.
Depending on the context from which you need to check the compression
scheme, if Python proves too unwieldy, you could also resort to
parsing/pattern-matching the output of the exrheader executable.
-Nathan
From: Rich Bobo
Sent: Monday, May 21, 2012 11:32 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] How to check zip compression type for EXR
images...?
I found this reference and it looks like the OpenEXR module would have what
I need, but I'm not sure if it's part of Nuke's Python installation or
not...
http://excamera.com/articles/26/doc/openexr.html
Rich
On May 21, 2012, at 2:24 PM, Rich Bobo wrote:
Hi,
Anyone know a quick way to check EXR images to see if they were saved as
16-scanline zips or single-scanline zips? ViewMetaData reveals nothing
about the compression type. I'm sure there's a command
Re: [Nuke-users] RED and color space options (not gamma curves)
i'm not an expert on this but interested in this topic too. only thing i can say is that red say: dont use our ACES profil for production. there is a big thread about the why on the reduser forum, thay say the ACES profil has to many erorrs and artifacts in the current state. Am 21.05.2012 23:44, schrieb Simon Björk: As anyone who has used RED footage in production knows, the color workflow is a bit of a nightmare. There are many options that each has it's pros and cons. The problems we had earlier with gamma curves (Redlog, Redspace etc), are now working quite well as we have both a linear and a Cineon (RedLogFilm) output. But what about color space? I've been using Redcolor2 for quite some time, but I'm looking at using the Camera RGB option as it seems to have less artifacts. Is anyone using this, and if so, how are you working with the footage? Are you applying a lut that transforms the bleak colors into a more pleasing image or are you just match grading as usual? Is anyone using the ACES output that RED provides? Thanks, Simon ___ 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
Re: [Nuke-users] How to check zip compression type for EXR images...?
Hi
In fact each channel name in exr can be 31 bytes long, so even 4096 could be
too less in some extreme cases. On the other side we don't want to read too
much.
The code below fix this issue: I did small modifications to read actual size of
channels list and skip over, no matter how many channels is in the file. I
added few comments to clarify.
import struct
compList = ['None', 'RLE', 'ZIP', 'ZIP 16 lines', 'PIZ', 'PXR24', 'B44', 'B44A']
n = nuke.selectedNode()
file = nuke.filename(n, nuke.REPLACE)
fd = open(file, 'rb')
# read small portion of data
header = fd.read(256)
# search for channels list tag. Well... in fact we could hardcode this position
but I prefer to write it more flexible
channels = header.find('channels')
# skip the tags...
fd.seek(channels+16)
# ...and read the actual size of channels list. We know, that it's 4-byte
integer
channelsSize = fd.read(4)
# Ok, so we know how long (in bytes) is the channels list in our file. And we
simply jump over
fd.seek(struct.unpack('i', channelsSize)[0], 1)
# Here we are
position = fd.tell()
# read next portion of data and search for compression
header = fd.read(256)
index = header.find('compression')
fd.seek(position + index+28)
comp = ord(fd.read(1))
print compList[comp]
##
Best
Adrian
Nathan,
Thanks for the PDF link to the OpenEXR file layout - I was looking for
something like that!
Rich
On May 22, 2012, at 1:23 PM, Nathan Rusch wrote:
The compression attribute will be in a different place within the header
depending on the number of channels in the file (due to the layout of the
EXR header).
Adrian's snippet is simply finding the 'compression' attribute name within
the header, since that is one of the standard EXR attributes. From there,
based on known information about the EXR file layout, he can determine
where the actual compression attribute value is stored.
The read size of 1024 is pretty much an arbitrary value; you may need to
read a larger chunk in order to get far enough into the file to locate the
compression attribute if your file has a lot of channels. If you know the
names of all the channels within the file, you could figure out exactly how
many bytes to read, or even start your read from a predefined offset to
keep your data buffer as small as possible; otherwise, you'll just need to
make a safe estimate.
Check out this doc for a nice simple example of the structure of an EXR
file: http://www.openexr.com/openexrfilelayout.pdf
Hope this helps.
-Nathan
-Original Message- From: Dan Rosen
Sent: Tuesday, May 22, 2012 9:59 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] How to check zip compression type for EXR
images...?
This is great! Can you let us know what index number the datatype is
in? I'm finding it hard to tell.
thx
Dan
On Mon, May 21, 2012 at 7:30 PM, Richard Bobo richb...@mac.com wrote:
Adrian,
Brilliant - I'll be making it into a nice little pulldown menu utility
function! And, looking a bit deeper at your code, of course, so I can learn
some more Python... 8^)
Thanks!
Rich
Rich Bobo
Senior VFX Compositor
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 simplified
**
compList = ['None', 'RLE', 'ZIP', 'ZIP 16 lines', 'PIZ', 'PXR24', 'B44',
'B44A']
n = nuke.selectedNode()
file = nuke.filename(n, nuke.REPLACE)
fd = open(file, 'rb')
header = fd.read(1024)
index = header.find('compression')
comp =ord(header[(index+28):(index+29)])
print compList[comp]
***
Each exr file MUST have compression info in the header and this info is
placed just after channels info. It's simple to get actual size of channels
list but I quickly set 1024 bytes of a headroom.
Best
Adrian
___
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
___
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] Alignment Layout A over B in Nuke
It has always puzzled me when using the alignment's shortcut L would put your A nodes to the top B nodes to the left like, A A B__| __ B__| The new 'breakout layers' option for psd also align the nodes that way, but must of the artists, including me working the other way around to keep the B pipe as a backbone like, B A__| B A__| So, the question is, isn't the foundry suppose to fix this so that when we hit L (lower case) it would align B on top A on the left? Just curious. J ___ 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
Re: [Nuke-users] Alignment Layout A over B in Nuke
+1 I'm still new to Nuke, but I also find myself using B as a backbone. It makes more sense to be adding the A channel on top of B… Rich Rich Bobo Senior VFX Compositor Mobile: (248) 840-2665 Web: http://richbobo.com/ The world stands aside to let anyone pass who knows where he is going. - David Starr Jordan On May 22, 2012, at 8:56 PM, Jason P Nguyen wrote: It has always puzzled me when using the alignment's shortcut L would put your A nodes to the top B nodes to the left like, A A B__| __ B__| The new 'breakout layers' option for psd also align the nodes that way, but must of the artists, including me working the other way around to keep the B pipe as a backbone like, B A__| B A__| So, the question is, isn't the foundry suppose to fix this so that when we hit L (lower case) it would align B on top A on the left? Just curious. J ___ 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
Re: [Nuke-users] Alignment Layout A over B in Nuke
Exactly, Same feelings. I tend not to use layout shortcut for anythign that is connected, as it never gives desired results in my experience. -Adam On 05/22/2012 06:35 PM, Richard Bobo wrote: +1 I'm still new to Nuke, but I also find myself using B as a backbone. It makes more sense to be adding the A channel on top of B... Rich Rich Bobo Senior VFX Compositor Mobile: (248) 840-2665 Web: http://richbobo.com/ The world stands aside to let anyone pass who knows where he is going. - David Starr Jordan On May 22, 2012, at 8:56 PM, Jason P Nguyen wrote: It has always puzzled me when using the alignment's shortcut L would put your A nodes to the top B nodes to the left like, A A B__| __ B__| The new 'breakout layers' option for psd also align the nodes that way, but must of the artists, including me working the other way around to keep the B pipe as a backbone like, B A__| B A__| So, the question is, isn't the foundry suppose to fix this so that when we hit L (lower case) it would align B on top A on the left? Just curious. J ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk mailto: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 ___ 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
Re: [Nuke-users] How to check zip compression type for EXR images...?
Terrific, Adrian! I'm happy you had a chance to make it more accurate!
Hopefully, I'll have a chance tomorrow to give it a try. ...Reminds me of the
old days when I used tape handling commands on an 8mm Exabyte tape drive to
find headers and file markers to read specific frames from tape! (Yes, I'm old.
;^) LOL )
Rich
On May 22, 2012, at 7:28 PM, Adrian Baltowski wrote:
Hi
In fact each channel name in exr can be 31 bytes long, so even 4096 could be
too less in some extreme cases. On the other side we don't want to read too
much.
The code below fix this issue: I did small modifications to read actual size
of channels list and skip over, no matter how many channels is in the file. I
added few comments to clarify.
import struct
compList = ['None', 'RLE', 'ZIP', 'ZIP 16 lines', 'PIZ', 'PXR24', 'B44',
'B44A']
n = nuke.selectedNode()
file = nuke.filename(n, nuke.REPLACE)
fd = open(file, 'rb')
# read small portion of data
header = fd.read(256)
# search for channels list tag. Well... in fact we could hardcode this
position but I prefer to write it more flexible
channels = header.find('channels')
# skip the tags...
fd.seek(channels+16)
# ...and read the actual size of channels list. We know, that it's 4-byte
integer
channelsSize = fd.read(4)
# Ok, so we know how long (in bytes) is the channels list in our file. And we
simply jump over
fd.seek(struct.unpack('i', channelsSize)[0], 1)
# Here we are
position = fd.tell()
# read next portion of data and search for compression
header = fd.read(256)
index = header.find('compression')
fd.seek(position + index+28)
comp = ord(fd.read(1))
print compList[comp]
##
Best
Adrian
Nathan,
Thanks for the PDF link to the OpenEXR file layout - I was looking for
something like that!
Rich
On May 22, 2012, at 1:23 PM, Nathan Rusch wrote:
The compression attribute will be in a different place within the header
depending on the number of channels in the file (due to the layout of the
EXR header).
Adrian's snippet is simply finding the 'compression' attribute name within
the header, since that is one of the standard EXR attributes. From there,
based on known information about the EXR file layout, he can determine
where the actual compression attribute value is stored.
The read size of 1024 is pretty much an arbitrary value; you may need to
read a larger chunk in order to get far enough into the file to locate the
compression attribute if your file has a lot of channels. If you know the
names of all the channels within the file, you could figure out exactly how
many bytes to read, or even start your read from a predefined offset to
keep your data buffer as small as possible; otherwise, you'll just need to
make a safe estimate.
Check out this doc for a nice simple example of the structure of an EXR
file: http://www.openexr.com/openexrfilelayout.pdf
Hope this helps.
-Nathan
-Original Message- From: Dan Rosen
Sent: Tuesday, May 22, 2012 9:59 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] How to check zip compression type for EXR
images...?
This is great! Can you let us know what index number the datatype is
in? I'm finding it hard to tell.
thx
Dan
On Mon, May 21, 2012 at 7:30 PM, Richard Bobo richb...@mac.com wrote:
Adrian,
Brilliant - I'll be making it into a nice little pulldown menu utility
function! And, looking a bit deeper at your code, of course, so I can learn
some more Python... 8^)
Thanks!
Rich
Rich Bobo
Senior VFX Compositor
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 simplified
**
compList = ['None', 'RLE', 'ZIP', 'ZIP 16 lines', 'PIZ', 'PXR24', 'B44',
'B44A']
n = nuke.selectedNode()
file = nuke.filename(n, nuke.REPLACE)
fd = open(file, 'rb')
header = fd.read(1024)
index = header.find('compression')
comp =ord(header[(index+28):(index+29)])
print compList[comp]
***
Each exr file MUST have compression info in the header and this info is
placed just after channels info. It's simple to get actual size of channels
list but I quickly set 1024 bytes of a headroom.
Best
Adrian
___
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/
