[Bf-committers] Luminance patches
p_boelens at msn.com
Tue Feb 17 23:20:50 CET 2015
I'm not sure how important it is in this case, or even how often these kind of things happen, but I wonder if there's a way we could notify users when a loaded .blend is "broken". The top bar notification seems too small and insignificant for this, but I am thinking in that direction; something that says "Hey! This is an old file, and so your colors might be off slightly, because we changed X, Y and Z. Btw, your 2.45 driver's also kaput now. ;)" This is probably more something for the UI team, but figured I'd throw it on here just in case - apologies if this is considered too off-topic.
> Date: Tue, 17 Feb 2015 23:05:41 +0100
> From: kalast at gmail.com
> To: software at plasmasolutions.de; bf-committers at blender.org
> Subject: Re: [Bf-committers] Luminance patches
> Hi Thomas, agreed, I am also of the same opinion. It will hurt old
> files slightly but better now than never.
> On 17 February 2015 at 20:21, Thomas Beck <software at plasmasolutions.de> wrote:
> > Hi Antony,
> > I'm for "fix it properly by breaking old files slightly". I (the artists
> > around me agree) prefer to let old files break (in terms of color
> > correction) when we get a working color pipeline with correct formulas in
> > exchange for it. I would really not like to see a wrong behavior carried on
> > endless times just to be compatible to infinity and beyond ;) .
> > Greetings, Thomas
> > Plasmasolutions
> > Design | Development | Training
> > Website: Http://www.plasmasolutions.de <http://www.plasmasolutions.de/>
> > Blog: Http://blog.plasmasolutions.de <http://blog.plasmasolutions.de/>
> > Telefon: +49 176 2017 9565
> > Blender Foundation Certified Trainer
> > <http://www.blendernetwork.org/BFCT>Autor von "Blender 2.7 - das umfassende
> > Handbuch" <http://www.galileo-press.de/3404>
> > 2015-02-17 19:42 GMT+01:00 Antony Riakiotakis <kalast at gmail.com>:
> >> Hi,
> >> We have quite a few functions to select luminance in our code.
> >> Recently there were two patches to cleanup things.
> >> https://developer.blender.org/D1082
> >> https://developer.blender.org/D517
> >> Seeing how developers still use any of the two in the code and how
> >> there's really one correct formula for this it might be good to make
> >> some decision about this.
> >> Choises are - either we change this and break old files slightly or we
> >> keep it and we have wrong histograms, tools and compatibility with
> >> color management pipeline.
> >> I am curious about what coders and artists think about the change
> >> since it will influence both.
> >> _______________________________________________
> >> Bf-committers mailing list
> >> Bf-committers at blender.org
> >> http://lists.blender.org/mailman/listinfo/bf-committers
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers