Bugs item #2779564, was opened at 2009-04-23 10:39 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=2779564&group_id=64325
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pixes (pix_ objects) Group: None >Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: Nobody/Anonymous (nobody) Summary: pix_chroma_key uses RGB values from 0-255, not 0-1 Initial Comment: For whatever reason, [pix_chroma_key] uses RGB values between 0 and 255 rather than 0 and 1 like the rest of Gem. http://lists.puredata.info/pipermail/gem-dev/2009-04/003952.html ---------------------------------------------------------------------- >Comment By: Hans-Christoph Steiner (eighthave) Date: 2009-06-02 09:36 Message: >From what I understand, this will now respond to both 0-1 and 0-255. I think this could lead to some very confusing bugs/behavior. How about just issuing a warning that the data range changed from 0-255 to 0-1? ---------------------------------------------------------------------- Comment By: IOhannes m zmlnig (zmoelnig) Date: 2009-06-02 04:41 Message: should be fixed with revision 2828. the behaviour is now: if all of the |values| are <=1.0, then we assume they are normalized, else we switch to legacy mode. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=2779564&group_id=64325 _______________________________________________ GEM-dev mailing list [email protected] http://lists.puredata.info/listinfo/gem-dev
