Brecht, I think I wrote enogh to explain my analisys. It is a lot more than simply "my way is better".
Let's wait for other users that are rely working with stereo to publish their feedbacks too. I rest my case for now ;) Adriano 2013/6/17 Brecht Van Lommel <[email protected]> > Hi Adriano, > > I can't do much with this answer, to me this reads "it's better > because it's better". It doesn't explain how anything that is possible > in your workflow will not be possible now, or how your workflow is > simpler. I'd like to understand it but as far as I can tell you are > just reiterating how you want it to work and not why it should work > that way? > > To me this is similar to the color management and > premultiplied/straight alpha discussions, and to the way full sample > AA works for example. Some people will say, just give me the nodes to > do all the conversions and I'll set it up myself. That's on way to do > it and we can support that. If you want to create a separate scene for > compositing and composite the L/R parts in one nodes setup, you should > be able to do that. > > But we can provide a higher level workflow too that makes things > easier for most users. And for that workflow I think it's important to > have a good separation between what you do in the compositing nodes > and the particular stereo method that is used for display and file > saving. > > Thanks, > Brecht. > > On Mon, Jun 17, 2013 at 2:51 PM, Adriano Oliveira > <[email protected]> wrote: > > Hi Brecht, > > > >> But can you explain to me specifically why that is better than the > > workflow used in the branch? > > > > Because it is more simple and better fits in actual Blender logic. It is > > also the way everey other composite sistem works, as far as I know. > > > > > >> But why? How is this different from the RenderLayer/RenderPass > > distinction we have already? > > > > The current SELECT VIEW approach in Image Editor is leading to > limitations > > and changing too much in Blender UI and Node Editor. > > > > • Select View is not necessary because we already have Select Pass and > L/R > > views are simply new kind of passes. > > • Select View "3-D" offers a fancy fast-composition that is independent > > from Node Editor, so it turns Image Editor inconsistent with composition. > > • Implementing Select View is a danger, because it changes a lot in Node > > Editor output logic, without offering as much. > > • Treating L/R as passes is just enough. We add new possibilities and > don't > > chage a lot what is already working. > > • Obtaining Image Editor stereo outputs through composition nodes is just > > enough and safer. > > • To keep node editor compatible with new EXR capabilities we just need a > > Nuke like merge channel node, so we can re-insert decomposed layers and > > output them to a single file. This is useful beyond stereo. > > • STEREO PREVIEW option in 3D View is ok. We don't need stereo options in > > user preferences, as long as automated preview would only affect 3D View, > > and Node Editor affects Image Editor. > > > > Let's just not add to Node Editor/Image Editor things that leads to > > different and untested workflows that we don't miss. > > > > This is a very nice discussion! > > > > :D > > > > Adriano > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
