Hey Adrian,
Not currently that I'm aware of. There's a few hacky workarounds such as
checking the node name and it's intree status (poss combined with
current outputcontext sizes) that currently seems to work in 6.2, but
the likelihood is as the op regeneration becomes more efficient in
future builds the browser op will be reused so I wouldn't rely on it
staying that way.
Write in to support to ask for some method of this being done from
within an op (probably on the proxy system in some way I guess).
Cheers
Jack
On 10/03/2011 19:57, Adrian Baltowski wrote:
Hey
When one select some multilayer file (like exr or psd) in file browser nuke
goes through all layers: layer by layer, channel by channel nuke
allocate memory, decompress it etc, etc. In case of really big files, with many
layers it can take long time. And it's all for nothing
because prewiew window shows only base RGB set. Additionaly: even if I just
click on such a multilayer file to watch it, Nuke permanently
create tons of channels in my script. It can be irritating if one works with
such files all the time.
So I have a question: is there way to distinc betwen "normal" usage of Reader and
"file browser preview"? I guess there is no difference in
call to Reader constructor. But it would be great to find some way to disable
multilayer support in file browser preview.
Best
Adrian
_______________________________________________
Nuke-dev mailing list
[email protected]
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
--
Jack Binks, Product Manager
The Foundry, 6th Floor, Communications Building
48 Leicester Square, London, WC2H 7LT, UK
Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550
Web: www.thefoundry.co.uk
The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027
_______________________________________________
Nuke-dev mailing list
[email protected]
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
