Extract channels from only one EXR loader

Anyone knows an option or build a setup to extract diferent channels from only one Loader containing EXR?

I tried channel booleans, but it don't wanna read available channels from EXR, so at this moment I'm working with multiple copies of the same EXR loader and setting handly each one the channel that I want pick from EXR. That is not very memory cheap.

You can't... and it sucks badly.

You have to map first the channel you want in the available "standard" channel of fusion, in the tab "format" of the loader, then you can use it like in a channel boolean

2016-11-23_09h41_41.png (12.85 KiB) Viewed 5894 times

Thank you for your reply.

I'm already doing as your screenshot. Question is this have mainly two cons. I can't replace loaders by drag and drop, cos loader ids are changed and channels selection are lost.
Also this way force me to have many loaders for the same input file and its memory consumption.

If you are using Fusion 7 you can try this script to at least speed along the process of splitting the EXR. Not sure if it works with Fusion 8.
http://www.svenneve.com/?p=239

Really hoping that Black Magic develops something native for better handling of EXR's.

You're right fusion isn't really taillored for vfx compositing, this is so simple in nuke or even afterfx !

the only solution is this script http://www.littlevfx.com/tools/ who isn't working in fusion 8, this sucks !

i updated the scripts from tim little to work in fusion8
viewtopic.php?f=22&t=53746&p=311185#p311185

You're right fusion isn't really taillored for vfx compositing, this is so simple in nuke or even afterfx !

well, thats a broad statement.
i think correct is: fusion isnt taillored for multipass exr files, but vfx compositing is no problem

yes, nuke play very nice with multilayer exr files and its whole workflow is build around it.
fusion has a different workflow and maybe its old and from a time where 1000 channels in an image wasnt normal, but you can work with single layer files and a good file/folder structure very efficent. you would probaly also work faster and more memory efficent. you need only to load the layers that are needed and not the whole file, you will load faster because smaller file size, ...
with a little script you can increase the version of all/selected loaders for importing new versions, you can even mix between different version of the renderings

For me one of the main purpose of a "channel" workflow is the ability to keep the network simple and clean.
Actually if for example we need to CC a thing on nuke we just drop a grade and in the mask section we choose the correct matte channel comming from the main exr.
If we do that in fusion the result needs a mask extraction from the exr and some wires, that's not as easy and clean

It has both its advantages and disadvantages.

Clean sometimes means less clear.

If there are no 'wires' how can you tell from the comp what it is you're doing?
That's my main issue with layer-based compositing.

If we do that in fusion the result needs a mask extraction from the exr and some wires, that's not as easy and clean

I'll buy your dongle for $400.

If we do that in fusion the result needs a mask extraction from the exr and some wires, that's not as easy and clean

I'll buy your dongle for $400.

You're right i'm not totally fair, sorry for being in a bad mood.

If you are using Fusion 7 you can try this script to at least speed along the process of splitting the EXR. Not sure if it works with Fusion 8.
http://www.svenneve.com/?p=239

Really hoping that Black Magic develops something native for better handling of EXR's.

Thanks so much!

I still use Fusion 6 (I don't will use F7 or F8 while BM not fix scripts issue) and I tried with splitEXR 1.4 and 1.5 versions (they are .eyeonscript) but I obtain an error like 'no valid nil value'.

I still use Fusion 6 (I don't will use F7 or F8 while BM not fix scripts issue)

what issue do you mean? there was a change in the script language and this was communicated clearly. (this was still in the eyeon time)
do you expect BMD to update every custom script someone wrote years ago to work with the new syntax?

and I tried with splitEXR 1.4 and 1.5 versions (they are .eyeonscript) but I obtain an error like 'no valid nil value'.

can you copy the exact error message? then we could help you

I still use Fusion 6 (I don't will use F7 or F8 while BM not fix scripts issue)

what issue do you mean? there was a change in the script language and this was communicated clearly. (this was still in the eyeon time)
do you expect BMD to update every custom script someone wrote years ago to work with the new syntax?

Hotkey Manager, AddTool,... they are custom scripts? From Eyeon, this pack of scripts was built-in. Now I hope I have at less the same functionality that previous versions, from BMD, without I have to do peripetias after installion.
When BMD fix this, then I will can upgrade it.
In the meantime, how many better is lua than eyeonscript?
Why not migrate all Fusion scripts to python? Is tedious to have learn it own scripting language for each software. Really I feel in the past.
From the most DCC applications have Python support, development from scripters should going towards there.

and I tried with splitEXR 1.4 and 1.5 versions (they are .eyeonscript) but I obtain an error like 'no valid nil value'.

can you copy the exact error message? then we could help you

Tomorrow I posting the error. At this time I don't have Fusion in front, sorry.

Eyeonscript was and is LUA. It's just extended with another library.
fusion also supports python 2.7 and 3, since 6.2(??)

The add tool function is now in the core program and no script anymore

Also the Hotkey Manager can now be found under view->customize hotkeys, so that's integrated into Fusion quite nicely as well.

I did not seen Hotkey Manager in Fusion 8. It is better like this.

hos_SplitEXR return me this error:
...eon/Fusion 6.4/Scripts/Comp/hos_SplitEXR.eyeonscript:107: attempt to index global 'tool' (a nil value)

I did not seen Hotkey Manager in Fusion 8. It is better like this.

hos_SplitEXR return me this error:
...eon/Fusion 6.4/Scripts/Comp/hos_SplitEXR.eyeonscript:107: attempt to index global 'tool' (a nil value)

this is a tool script and belongs under the "PATH_TO_FUSION/Scripts/Tools" and you can find it then if you right click on the loader under "scripts"