Bit Depth Information

[user_deleted]

Hello,

I am a new Nuke user. In the interface I don`t seem to be able to find any information regarding the bit depth of the images I load in Nuke. Usually the bit depth is displayed in the viewer, but obviously not in Nuke.

Can someone give me some directions?

Thanks

[maya-man]

QUOTE(scimmiabian @ 03/08/07, 10:39 PM) [snapback]261838[/snapback]
Hello,

I am a new Nuke user. In the interface I don`t seem to be able to find any information regarding the bit depth of the images I load in Nuke. Usually the bit depth is displayed in the viewer, but obviously not in Nuke.

Can someone give me some directions?

Thanks

I've been using Nuke for a few months and would like to know this too. If you hit 'i' on the keyboard with the read node selected you do get a bunch of info but I can't find anything there about the bit depth.

[max854]

From memory there is no bit-depth information available through the interface in Nuke due to the fact that images are automatically promoted to 32-bit float upon access through the Read node.

Its been a while since I've been infront of Nuke so please correct me if I'm wrong...

[user_deleted]

Correct, Nuke is optimized for floating point processing so all images are converted in the Read node. No need to bother with lower bit depths.

[maya-man]

QUOTE(rueter @ 03/20/07, 05:17 PM) [snapback]262571[/snapback]
Correct, Nuke is optimized for floating point processing so all images are converted in the Read node. No need to bother with lower bit depths.

Yes, understood, but the issue isn't comping in 8 or 16 bit, but knowing the bit depth of the footage prior to the promotion to float. If it was irrelevant we would all work with 8 bit files. It's important to know that your proxies are 8 bit as well, if that is the intention. So a quick way of identifying the bit depth of the source footage is important IMO. All it needs is an extra line in the read node info, near the top so that you don't have to scroll down. Or better yet, steal it from (gasp) Shake, where if you mouse over the filein, it tells you in the status line.

Respectfully
Michael

[user_deleted]

I agree. This is a good feature request and would probably be pretty easy to sort out.
For shits and giggles you could probably write a little tcl script that hijacks shake's info command to pop up in Nuke. ( i.e. you could make a new button in the Read nodes to execute "shake -i" along with the read node's file and pop up that info in a display window or the node's label.)

In the meantime I'd say send a feature request to support@thefoundry.com

cheers,
frank

[maya-man]

QUOTE(rueter @ 04/19/07, 06:37 AM) [snapback]264368[/snapback]
I agree. This is a good feature request and would probably be pretty easy to sort out.
For shits and giggles you could probably write a little tcl script that hijacks shake's info command to pop up in Nuke. ( i.e. you could make a new button in the Read nodes to execute "shake -i" along with the read node's file and pop up that info in a display window or the node's label.)

In the meantime I'd say send a feature request to support@thefoundry.com

cheers,
frank

Done...that is a pretty cool idea about taking the Shake command into Nuke. I haven't got to tcl scripting yet....I seem to remember saying that 3 months ago too!

Edit: the message was returned - the email address doesn't seem to exist! Anyone know the best support channel right now?

[user_deleted]

try this:

Read {
inputs 0
format "2048 1556 0 0 2048 1556 1 2k"
last 6
edge_code "00 00 00 0000 0000 00"
name Read1
selected true
xpos -146
ypos -56
addUserKnob {20 "" User}
addUserKnob {2 shake_exe "shake exe"}
shake_exe /vol/apps/nreal/shake-v4.10.0606/bin/shake
addUserKnob {26 "" ""}
addUserKnob {32 "" "image info" T "set curFile [value file]\ndisplay -t \"image info for \$curFile\" {exec [value shake_exe] \$curFile -info}"}
}

[maya-man]

Thanks for posting, I changed the path but it doesn't work for me, Nuke crashes when I click the new image info button in the Read node. I'm on OSX at the moment so maybe that has something to do with it. I took the path for the Shake unix executable (as opposed to Shake.app) to be sure. Not to worry...

Also, I figured out that the email address for the foundry is .co.uk not .com so have forwarded on the feature request...

Cheers,

Michael

[user_deleted]

hm weird, another OSX bug? I tried it on both Linux and Windows and it worked fine (windows was terribly slow though).
does it work when you type it directly into a shell (i.e. " -h")?

Also, I figured out that the email address for the foundry is .co.uk not .com so have forwarded on the feature request...

Oops, yes, sorry about that.

[maya-man]

QUOTE(rueter @ 04/20/07, 07:04 AM) [snapback]264445[/snapback]
hm weird, another OSX bug? I tried it on both Linux and Windows and it worked fine (windows was terribly slow though).
does it work when you type it directly into a shell (i.e. " -h")?

Yes, this does work. I expanded out the "shake" environment variable to the full path to check that I was using the right one in Nuke and it was correct. So I don't know what I would be doing wrong if it's not a bug. I can try it out on Windows at some point.

[user_deleted]

if it works directly in the command line try putting the same line in double quotes into the tcl console preceded by "exec".
I.e. exec ""

if that doesn't work it's probably a problem with OSX I'd assume.

[maya-man]

I can type exec "shake", or exec "do/the/full/path/to/shake" and it will launch from within Nuke but when typing exec "shake /thisfile.jpg" it seems to have trouble recognising file paths for the image...says no such file or directory.

[user_deleted]

are you using quotes for the file path? are there and issues with slashes vs. back slashes on OSX?

[maya-man]

I spent a bit of time looking at this and I found that the following works:
With the selected Read node run this script:
exec shake [knob [selected_node].file] -info
...and it throws up the message with the shake info stats.

However (assuming I load a file into the Read node) if I make a button called ShakeInfo(using the following script), Nuke crashes after throwing up the message.

Read {
inputs 0
name Read1
selected true
xpos -141
ypos -266
addUserKnob {20 "" l User}
addUserKnob {32 "" l ShakeInfo T "exec shake [knob [selected_node].file] -info"}
}

So there may be a bug in OSX to do with accessing TCL scripts via custom user knobs.

[user_deleted]

is this in 4.6? I noticed a bug yesterday where pressing a user defined script button in a Bezier node will crash Nuke 4.6 (on linux).
Seemed work ok in other nodes though.

[maya-man]

QUOTE(rueter @ 04/25/07, 06:41 AM) [snapback]264791[/snapback]
is this in 4.6? I noticed a bug yesterday where pressing a user defined script button in a Bezier node will crash Nuke 4.6 (on linux).
Seemed work ok in other nodes though.

yes, 4.6 on a mac intel machine.