|ID: 14029 · Rating: 0 · rate: / Reply Quote|
More work? Why would we want a steady flow of work?
|ID: 14030 · Rating: 0 · rate: / Reply Quote|
Yeah, one thing is for sure - it will bring a crazy amount of work to BURP to have this rendered.
|ID: 14034 · Rating: 0 · rate: / Reply Quote|
Sounds like a pretty cool project! Open source rendering projects are always welcome here - especially the BlenderFoundation ones.
|ID: 14040 · Rating: 0 · rate: / Reply Quote|
|ID: 14043 · Rating: 0 · rate: / Reply Quote|
I would like to look into getting both the color/render pass output as well as the z-Depth pass - could this be output in an multilayer EXR?
I think you can do that with just regular EXR by enabling "Z buffer" under the output options and connecting the relevant pin under nodes. There's no way to select EXR as output format during upload (and doing nothing means that the BURP system will render as PNG regardless of what was selected in the scene) but you can write in the description if you would like to try out the experimental EXR or multilayer EXR rendering.
As for the other stuff:
Well, I'll try to make this as general as possible so that it may be used in some of the documentation later. Let's start with the library feature since that is probably the most important thing:
For long productions with multiple scenes you typically have some resources that are re-used across all these scenes. This may be anything like textures, models, even entire sets. For Big Buck Bunny a lot of the stones and trees in the background were props that were re-used across many scenes and they were simply linked into those scenes from libraries.
A production typically organizes its content in directories - it could be like this:
./ (the project root directory) +---./textures/ | +---./textures/some-rocky-texture.png | +---./textures/some-other-texture.jpg +---./models/ | +---./models/a-rock.blend | +---./models/main-character.blend +---./scenes/ | +---./scenes/intro.blend | +---./scenes/scene1.blend | +---./scenes/scene2A.blend +---./stuff-not-used-for-rendering/ +---./stuff-not-used-for-rendering/post-it-note-about-cats.txt +---./stuff-not-used-for-rendering/sound-effects.wav
The "textures" and "models" directory contents are re-used across all the scenes in "scenes".
In order to use this together with BURP you simply put the "textures" and "models" directories into a .zip-file and upload it*. Notice that the "scenes" directory and the "stuff-not-used-for-rendering" directory were both left out of the .zip since they are not to be shared.
Then, for every scene you want to render you do this:
1) Open the scene ./scenes/sceneX.blend in Blender
2a) BURP requires the rendered scene to reside in the project root and all libraries to be next to it or below it in the directory structure. So select File->External Data->Make All Paths Relative to prepare a move of the scene file.
2b) Use File->Save As, to save the scene in the project root directory as ./sceneX.blend
Very important: Make sure that "Compress" and especially "Remap Relative" are selected under the "Save as Blender File" property panel in order to correctly locate the libraries later.
2c) Hit "Save" to move the file.
3) Upload the modified scene to BURP and attach the library you uploaded earlier to the session using the super nice and awesome online library browser that lists your recently uploaded libraries**
That's it really.
The scene file may contain textures, models and animations specific to just that one scene - as long as they are packed into the .blend when uploaded and no unresolved external references remain.
When using libraries - and especially right now where this is a very experimental feature - please allow some extra time for session reviews as every single file inside the library must be individually reviewed the first time that the library is used.
* You can't actually do that through the website yet, so please just post it somewhere and I'll manually upload it.
** You can't do that either yet, just write in the description what library should be attached.
|ID: 14044 · Rating: 0 · rate: / Reply Quote|
I understand that assets can be shared by different sessions, but I have only edited the things needed in the first intro sequence - I could probably get the whole project ready and then upload it for shared session material, but that would probably take a lot of time.
|ID: 14045 · Rating: 0 · rate: / Reply Quote|
but I have only edited the things needed in the first intro sequence
Very good point. It is sometimes the case that there are things which are used only in part of a production - like a character that dies half-way through a movie and no longer appears after that or a set of assets that are only used rarely but could still be shared when they are. It is also happens that a production is a work-in-progress and isn't finished at the time where the shared assets are to be prepared (like in your case).
That is why it is possible to attach not just one .zip-file but several. This way you can divide your project into different groups of assets - for instance those that you believe to be complete, those that are only used in scenes 8 through 14, those that are related to a specific place etc. etc. etc.
By including some, or all, of those libraries in a specific order as well as utilizing the assets bundled inside the .blend-files you can then control what the render nodes "see" as the complete asset tree.
For obvious reasons it would be really cool to have everything prepared in advance so that the best selection of what goes where could be made right away; but if you want to start your test now what I would recommend would be the following:
A) Build a library containing all the files that you know are used in the movie and you don't intend to modify. This could be stuff like the main characters' models, skeleton information, textures relating to things that are not affected by VR (eyes, fur, wood, that kind of stuff). Call it "base.zip" - you know in advance that this will eventually be re-used all over the place. Keep in mind that libraries can have files from many different directories - they will unpack to the same directory structure on the render nodes.
B) Build another library of things that you have changed for the intro scene but you expect are re-used in other scenes. Let's call it "vr-patch1.zip".
C) For all the stuff that are only used in the intro scene, pack it into the .blend
Now with the combined files from (A), (B) and (C) we can render the intro scene and check that it all went fine (there's probably going to be some odd bug that needs fixing but, yeah).
Next week when you've prepared scene 1-8 you will have a better idea about what is shared and you can then go back and check if the stuff in vr-patch1.zip was still relevant.
- If it was all still good and you had nothing new to add then fine, attach base.zip and vr-patch1.zip to those sessions.
- If you had something to add then either use the .blends (for single-session stuff) or if you know it will also be used later add a vr-patch2.zip and attach base,vr-patch1,vr-patch2.zips to the sessions.
- If something changed that was in vr-patch1.zip you can either ditch that .zip and create an entirely new one OR you can overwrite single files from it by also including those files in a new library.
The last one probably requires a bit more explanation:
Let's say that you added painted 2D backgrounds to base.zip because you thought they would work for the entire production. A few weeks into the production you find out that the backgrounds simply are not wide enough. You can either start over with a new 800MB base2.zip that everyone has to download including all the models etc. and go through the review again or you can create a new "overlay", which is another .zip that gets unpacked on top of the old one including only the new backgrounds (and optionally other additional stuff) - they simply overwrite the old files where there is a name clash. That way people only have to download the new files (a few MB) to continue rendering.
There's a limit to how many .zips you can attach to a single session, so if you are continuously changing things, then you may have to consolidate a lot of small .zips into one or two bigger ones. I think the limit is somewhere around 8-10 .zips.
In general, try to keep the number of zips down and try to re-use them across as many sessions as possible - preferably all of them.
It is completely up to you how you name or organize the .zips. For Big Buck Bunny 3D the libraries were split into types of content instead:
This was for most of the sessions and an extra .zip for scenes in the same chapter that shared some additional assets specific to that chapter.
For sessions without matte we could leave out mattes.zip, and likewise chars.zip for sessions without any chars in them.
Back then we didn't have to overlay the .zips since all the assets were static during production. If we suddenly had to change some of the mattes we could have done a mattes-overlay1.zip
|ID: 14046 · Rating: 0 · rate: / Reply Quote|
It is completely up to you how you name or organize the .zips.
When I make resource libraries I everything in shared .blend files which I link to in my main scene setup. Do BURP support setups like this too?
Like, koro.blend with all character resources like textures and mesh data packed, and props.blend etc etc.
I can start restructuring everything right away.
|ID: 14047 · Rating: 0 · rate: / Reply Quote|
Whether or not it makes sense to put everything into .blend-files inside the .zips depends a lot on what you plan to change later. You would have to replace the entire .blend-file with a new one even if there was only a tiny change to a single texture if everything is packed like that.
|ID: 14048 · Rating: 0 · rate: / Reply Quote|
In case anyone is wondering, this is the animation I am currently working on getting on BURP: https://youtu.be/Z4C82eyhwgU
|ID: 14049 · Rating: 0 · rate: / Reply Quote|
Blender 2.75 have gotten some new stereoscopy features with built-in stereoscopic support when rendering.
|ID: 14052 · Rating: 0 · rate: / Reply Quote|
No, BURP cannot output multiple files at the moment but it unofficially and very experimentally supports it through other means.
|ID: 14053 · Rating: 0 · rate: / Reply Quote|
Oh wow, 35TB, so that is uncompressed stereoscopic 4k 5 channel (RGB-A-Z) per frame? since I am just using 2048x2048 and 2x4 channels (RGB-Z) and the animation is only around 3000 frames long I hope I can keep the storage under 1TB since I don't have much more than that on my 2TB storage drive.
|ID: 14054 · Rating: 0 · rate: / Reply Quote|