>> The specification was created this way on purpose, to give some room
>> for ringing and over/under-shoot in both the signal acquisition and
>> the digital operations that follow. The pixels should only need to
>> be clipped to the [16,235]/[16/240] range when converted to R'G'B'...
>
>I see. This is the answer to my question. Why is the complete range [0,255]
>not allowed?
0 and 255 ("all zeros" and "all ones") are reserved for use in
synchronization signals. A lot of studio equipment uses serial
digital interfaces which push around Y'CbCr bits with minimal
encapsulation (since the bitrates are already so high).
>> (The output should be restricted to a [1,254] range, but given the
>> math involved and legal input pixels, clipping is probably not
>> necessary.)
>
>This is what I did. The luminance channel of the matte is used in a convex
>combination of the input sources thus using the [16,235]/219 range.
Well, post your patch, already. You fixed a bug! :)
-matt m.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
