search for: rgb555

...represented, and perhaps something to accurately specify the colour space, basically what you are doing is opening up millions of possibilities, most of which are completely useless. If you have a bits per channel field in RGB, what about RGB24, 3 channels, 8 bits each, but padded into 32 bits. RGB555, 15 bits, padded to 16. There's thousands of invalid possibilities, and only 15-20 or less valid ones... only really 3-5 commonly used. If someone wants to go crazy and design a franken-yuv format for some bizarre reason, then they can easily make another stream format... but you can prett...

On Tue, Nov 08, 2005 at 06:08:25PM +0800, illiminable wrote: > Why not just make it OggRawFOURCC, do we really need one stream format for > rgb, and one for yuv ? [snip] > I just meant oggRaw, not fourcc. Oh, thank god you corrected this. :-) I was contemplating an "OggVid" format, and here is why I'm steering against it (though, yes, this has been a topic of

On Tue, Nov 08, 2005 at 06:08:25PM +0800, illiminable wrote: > Why not just make it OggRawFOURCC, do we really need one stream format for > rgb, and one for yuv ? [snip] > I just meant oggRaw, not fourcc. Oh, thank god you corrected this. :-) I was contemplating an "OggVid" format, and here is why I'm steering against it (though, yes, this has been a topic of

...represented, and perhaps something to accurately specify the colour space, basically what you are doing is opening up millions of possibilities, most of which are completely useless. If you have a bits per channel field in RGB, what about RGB24, 3 channels, 8 bits each, but padded into 32 bits. RGB555, 15 bits, padded to 16. There's thousands of invalid possibilities, and only 15-20 or less valid ones... only really 3-5 commonly used. If someone wants to go crazy and design a franken-yuv format for some bizarre reason, then they can easily make another stream format... but you can prett...

...'m sure derf or rillian can tell you all about it). That's one of the fields we're currently lacking on the wiki, and one which I don't understand either. > If you have a bits per channel field in RGB, what about RGB24, 3 channels, > 8 bits each, but padded into 32 bits. RGB555, 15 bits, padded to 16. Or RGB 565, giving green an extra bit because the human eye can see twice as many shades of green than red or blue.. but yes, RGB doubles the issue, which is why we need a seperate codec for it. > There's thousands of invalid possibilities, and only 15-20 or less...

...'m sure derf or rillian can tell you all about it). That's one of the fields we're currently lacking on the wiki, and one which I don't understand either. > If you have a bits per channel field in RGB, what about RGB24, 3 channels, > 8 bits each, but padded into 32 bits. RGB555, 15 bits, padded to 16. Or RGB 565, giving green an extra bit because the human eye can see twice as many shades of green than red or blue.. but yes, RGB doubles the issue, which is why we need a seperate codec for it. > There's thousands of invalid possibilities, and only 15-20 or less...

Hi, I hope you can help, I am in need of some assistance with the DirectShow filters for Theora. I have successfully created a working capture graph using OGG / Vorbis / Theora, however, when I add a Sample Grabber Directshow filter between the FFDShow decoder and Theora Encoder, this results in the video file being mirrored vertically. I have noticed that the original CaptureGraph was using

...git.freedesktop.org/git/swfdec s/SwfdecCodec/SwfdecAudioCodec/ and introduce SwfdecVideoCodec add swfdec_bits_get_bu16 Make the z_stream part of the SwfdecDecoder struct rate == 0 is allowed now fix wrong type in macros remove \n from debugging messages fix RGB555 images append the right SwfdecContent to the list get the next_event time before comparing Fix includes add jpeg_rgb_decoder_get_image_size rework cache handling The key should be static const, we don't want it on the stack Merge branch 'master'...