Hey all, just got an xvideo-based capture and record system up and running, and I wanted to speak about one small issue. When you query the Xv extensions to see what formats it supports, it returns a structure that, among other things, has a GUID and a fourcc code. The GUID is just a large hex number, but it specifies a very certain picture format. It may or may not relate to a fourcc code, but if it does then you can look up that code and see what everything is using. It would be sweet and super trivial to map the fourcc code into the v4l2 pixel format specifications. For instance, YUV420 maps to the fourcc code of I420, with a GUID of 0x30323449. Apparently (according to the xpert mailing list), "nobody uses anything but these codes". I guess nobody who developes in the windows world would have been more appropriate. It took a bit of figuring to realize what was going on, perhaps the v4l2 documentation could be added to? It would allow for closer integration of video for linux and the X video extension. Chris
