Single layer exr's
2338 8 0- sniegockiszymon
- Member
- 67 posts
- Joined: 6月 2022
- Online
- ysysimon
- Member
- 75 posts
- Joined: 12月 2017
- Online
- sniegockiszymon
- Member
- 67 posts
- Joined: 6月 2022
- Online
- jsmack
- Member
- 7755 posts
- Joined: 9月 2011
- Offline
- sniegockiszymon
- Member
- 67 posts
- Joined: 6月 2022
- Online
jsmackYes,I want all passes on seperate file, it should be one checkbox like in redshift or blender for example. Multi layers are not always efficient esspecialy when you are using subtractive workflow in compositing
legacy exrs still have multiple layers. The new exr is 'multi-part' which some older software doesn't support. Are you looking for one layer per file? In that case you'll have to create a product for each layer with a unique file name.
- ysysimon
- Member
- 75 posts
- Joined: 12月 2017
- Online
sniegockiszymonjsmackYes,I want all passes on seperate file, it should be one checkbox like in redshift or blender for example. Multi layers are not always efficient esspecialy when you are using subtractive workflow in compositing
legacy exrs still have multiple layers. The new exr is 'multi-part' which some older software doesn't support. Are you looking for one layer per file? In that case you'll have to create a product for each layer with a unique file name.
I thought this approach would increase a lot of hard disk IO time?
- sniegockiszymon
- Member
- 67 posts
- Joined: 6月 2022
- Online
ysysimonYou are still saving the same amount of data, but in multiple files, so propably saving lasts a little bit longer, but there is huge advatange in reading when you are using subtractive workflow in compo (you load only beauty and then subtract only pass you want to change). There is great explanation https://www.youtube.com/watch?v=e79yb3UvQTQ [www.youtube.com]sniegockiszymonjsmackYes,I want all passes on seperate file, it should be one checkbox like in redshift or blender for example. Multi layers are not always efficient esspecialy when you are using subtractive workflow in compositing
legacy exrs still have multiple layers. The new exr is 'multi-part' which some older software doesn't support. Are you looking for one layer per file? In that case you'll have to create a product for each layer with a unique file name.
I thought this approach would increase a lot of hard disk IO time?
Edited by sniegockiszymon - 2022年11月22日 17:34:20
- jsmack
- Member
- 7755 posts
- Joined: 9月 2011
- Offline
sniegockiszymonysysimonYou are still saving the same amount of data, but in multiple files, so propably saving lasts a little bit longer, but there is huge advatange in reading when you are using subtractive workflow in compo (you load only beauty and then subtract only pass you want to change). There is great explanation https://www.youtube.com/watch?v=e79yb3UvQTQ [www.youtube.com]sniegockiszymonjsmackYes,I want all passes on seperate file, it should be one checkbox like in redshift or blender for example. Multi layers are not always efficient esspecialy when you are using subtractive workflow in compositing
legacy exrs still have multiple layers. The new exr is 'multi-part' which some older software doesn't support. Are you looking for one layer per file? In that case you'll have to create a product for each layer with a unique file name.
I thought this approach would increase a lot of hard disk IO time?
Multipart exr already only loads the passes being used.
- BryanRay
- スタッフ
- 43 posts
- Joined: 3月 2022
- Offline
-
- Quick Links