Neither Photoshop or any other image editing application that can handle 32bit files?
photoshop cs2 so for architectural purposes it is more than enough but 32bit possibilities are very rough
I'm sorry, but you shouldn't be doing CG then
aye Sir! I am an architect so this is not my primal target. CG is rather hobby
I mean I hope this doesn't sound arrogant, but it's like saying Win95 is good enough for me! There is really no excuse for not working in 32bit especially if you want to make these kinds of edits to your images.
with my canon that I bought oneday I get canon software that can magically sets BW in my RAW files with one click.
As I said it would be a cool workflow feature to have "WB" in Maxwell
I totally agree with You as always
, but I think some are missing the point here of why white balance is necessary in the real world, and what it does. It's sort of like the question of why you need two exposures to expose both for indoor and outdoor lighting. You have a WB setting, now what? Do you white balance in this case the yellow lights so they are more or less white? But then the sunlight will turn blue....so I hope people don't expect a "fix it all" setting, you still have to know what you're doing from the beginning.
It is mostly needed for getting rid allyellowishbubblegum of 5777K from sun. blue from sky is not so strong comparing to pure power of sun on clear sky
In this case you would be a bit screwed, WB setting or not, unless you had used color Multilight - in which case, set the lights to 6500K - you've "white balanced" the light from the emitter.
setting emitters to 6500K ? now it is blasphemy. maybe it works different in post-process multilight features, but doing something like that is fail wrong and even worst. scene lit with 2600 K with postprocess WB would looks completelly different than used 6500 K emmiters without using WB.
If they would looks the same in maxwellrender. then something is very wrong from beggining.
If you think from the beginning what the different light sources temp would be in the real world, but you just want a small difference in color cast, don't use 2600K lights together with physical sky for example, set the lights closer to the physical sky sun temp and you get less of a difference...or don't use yellow/blue lights at all if you don't want a color cast in your scene, you can have perfectly white emitters.... That's why I'm thinking how useful this would really be if you can already "WB" before hand (and afterwards with color ML which would be more flexible than an overall WB) and it's so easy.
Just saying, don't get too hung up on a feature name, and that it's "missing" when we are not dealing with the constraints of a real world situation.
translating 2600 K in wave equivalent is one of the most stunning features in maxwellrender. If someone tell me I should use MORE WHITE LIGHTS insted of physical correct one so there is something wrong.
when I render in biased render I use pure white to not fight with funny GI second bounce colors.
I hope maxwell treated this RGB-spectral conversion this way http://www.google.pl/url?sa=t&rct=j&q=an+rbg+to+spectrum&source=web&cd=3&ved=0CDgQFjAC&url=http%3A%2F%2Fblog.neodyme.net%2Fwp-content%2Fuploads%2F2011%2F03%2Fpaper.pdf&ei=JQEmT8zAN4qy0QXevujOCg&usg=AFQjCNEml7s-ztPd-NoXDDBef6umgxT3zQ&cad=rja
- so emmiters should be set on REAL color (as in real life)
- frambuffer in maxwellrender should looks little crappy at first look (as in real life RAW files without WB proper set)
- White Balance should be used in POSTPROCES (as in real life - processor in my canon does it for me, or canon software fixed it on my RAW fies)
-so if maxwellredner is "easy as taking a photo" so it would be nice to have few presets, and one place to set KELVINS, and one pickdrop to point white wall with one click telling maxwell "THIS SHOULD BE WHITE"
-as I said , it don't look so impossible to tallented coders in NL.
and last ...
this is Half Life's fault
he was thinking WHY WISHLIST is so empty
here You go Jason !