yeah, I want the option the other way around! Which appears to be the high end industry standard as well.
I’m sure the developers had good reason for making the new color nodes the way they did , but I
wish they could have added this very important feature, as well.
+1 that makes much more sense! But node classes should be color coded generically, so anyone can follow your screen grab layout at a glance.
Yeah. Probably one agreed upon color set should be the default. { I was trying to follow the Nuke style,
but the nodes don’t always match up. Their Grade is Like a super charged RBG curves node, for example }
Next question would be how to get the proposal to a developer? Who is working on nodes at the moment…?
there might be a clue in this:
Developer Meeting Notes for Sunday 9th September 2012 http://lists.blender.org/pipermail/b...er/037559.html
Hi all,
Here’s the notes of today’s meeting in irc.freenode.net #blendercoders
Open bugs down to 276 total! Campbell and Brecht have been busy, well done!
Jens Verwiebe has a fix for OpenGL display on Macbook with retina screens. Please check latest svn!
Brecht van Lommel finished porting over all Cycles features from Project Mango’s branch; including tile render, better updates, speedup.
- Sergey Sharybin is still working on porting over the color management to trunk. There are possible regressions, this is being studied on still.
- Proposal: We release Blender with OCIO as default. Compiled without, Blender will only work as the old “Use color management” option. If you like to use the old “No colormanagement”, you need to use the official build with OCIO and choose “None” as Display Device transform.
- Brecht will review the color code, and hopefully it goes to svn in a few days, allowing us to move release status to BCon4 (only bugfix period, release in 1-2 weeks).
Proposal: don’t release with the option “use legacy compositor”. Or better said, code gets removed.
Planning: target at release end of month, so it can get copied (and used/tested) with the Mango dvd.
Jens Verwiebe can’t further support OS X PPC, for building or releases. We need someone who keeps all libs for that system, and maintain the build system, and do releases. Mike Erwin looks into taking it over.
Thomas Dinges and Lukas Toenne worked on Cycles Open Shading Language support:
http://code.blender.org/index.php/20...age-in-cycles/
Target is to have it ready for 2.65.
SSE2: will become default for releases from 2.65 on.
Thanks,
-Ton-
I placed a comment here http://code.blender.org/index.php/2012/05/node-editing-tweaks/ but yes, it looks like they have their hands full at the moment.
Nice…thanks.
The colors should be well thought out, not just slapped on. { probably the top shader artist should
design them }
I hear the continual cry that " professionals looked at blender but rejected it cause it didn’t feel right."
Well, the two top Hollywood compositor softwares have a well treaded road with their
color sets. Put it in their league.
Well, waddayaknow. A proposal that actually makes good sense 
Developers?
Just one thing. Never mention industry standards or other applications to the devteam, I think that might actually lower the chances of your proposal making it to trunk 
Count my voice on plus too. It would be really great having that easy-readible nodes setups.
No, the color management spoken of is color spaces, etc. Nothing to do with UI. The module owner for the node editor seems to be Ton Roosendaal, but I believe Lukas Toenne has been doing most of the development in that area lately.
This is a great idea, but I would prefer to see the subdued hues of Fusion than the gaudy tones of Nukes’ nodes!
Would also love to see the factor parameter of the mix nodes exposed in the n-panel. I guess because this is both a driven port and changeable parameter that it is an isolated case? When you have a ton of mix nodes all folded up, it would be much more convenient to access the factor amount from the n-panel 
Additionally, having the render passes that are accessible in the render properties mirrored in the outliner would be good for the sake of consistency. Currently they don’t change when you activate cycles.
My main usability with the compositor is still the same that I have had for a while…the lack of a RAM cache system. I am used to this in AE or Fusion, and am not quite sure how people comp without out it…are you just doing lots of flipbook renders? Having said that, Nuke is only finally getting one now and they will be up to version 7!
You can fake a low res render by sending the Comp scene to another scene running the VSE then create a proxy (of it) there. Clumsy tho.
yeah, probably best to do THE BLENDER WAY. with our own color expert
artist.
Heres the colors of once dominant { now cancelled} Apple Shake. I dont like
this pallet.
you all know about the user preferences panel, don’t you?
Blender 2.63
it could be improved to include all node types, but its available already
Small troll, thanks. There just don’t seem to be enough classes.
yeah, thats a good start. Shows the code already in place! But not enough complimentary colors.
Also, that doesn’t set a node standard, so people can universally read a node tree. { and make their own work faster}
Also, doesn’t it change your main GUI theme colors? I never mess with that, { just pick a pre made theme myself}
Thanks
BUT SINCE thats already in place, could someone just write a universal add on to improve it?
ALL IMPORTANT COMPLEMENTARY COLORS
LINK TO Color Harmonies
http://www.tigercolor.com/color-lab/color-theory/color-harmonies.htm
I agree that collapsed nodes should display node color.
It already displays type color. Maybe node color could be shown as a colored outline around node and a colored triangle inside node.
But I prefer to keep actual colored by category or uncolored header to keep a more readable title.
Dark colors implies bright texts.
