[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-patch-tracker] [patch #8709] fixes to color conversion functions

From: Carnë Draug
Subject: [Octave-patch-tracker] [patch #8709] fixes to color conversion functions (mainly rgb2ntsc and ntsc2rgb)
Date: Mon, 02 Nov 2015 19:22:11 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.3.0

Follow-up Comment #10, patch #8709 (project octave):

We convert hsv and rgb images in integers into the [0 1] range because those
are the values we expect those images to have if they were floating points. 
We can easily compute the expected range of YIQ values as floating points.

Since the matrix for conversion is:

  trans = [ 0.299  0.596  0.211
            0.587 -0.274 -0.523
            0.114 -0.322  0.312 ];

the expected output range (consider RGB values between [0 1]) would be:

Y = [ 0      1.106]
I = [-0.797  0.587]
Q = [-0.322  0.426]

It wouldn't be too complicated to do such conversion. What do you think? It
may not be worth the extra complication if we don't think anyone will ever
find or use it. If that's so, then I agree with your first solution of not
allowing floating point input at all for this function.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]