"Luca" <luca_ing@xxxxxxxxx> writes: > If it is centered, xawtv doesn't display it in correctly...i've to > resize it by hand to see the image. xawtv -v 1 will log to stderr what it is trying too do. One of the drawbacks of the v4l1 API is that you can't negotiate a parameters between driver and application easily, this might cause some trouble too. > >> 2) The frames are grabbed using the YUV422-16bit format (original video), > >> but when xawtv try to display them, the colours vary from green to > >> purple only (i am not an expert, but i think the u or v value > >> is setted to 0). > > >bytes swapped? > > No, it doesn't sound like bytes are swapped.. > > In my very _humble_ opinion there's something wrong with the new > high-level v4l1 interface (videodev.c) concerning some calls > (pheraps the way it (eventually) handles/asks for mmapped memory?): I doubt that. videodev.o doesn't touch the ioctl data passed between application and driver. Neither the old nor the new version. mmap() is just passed through too. Gerd -- Weil die späten Diskussionen nicht mal mehr den Rotwein lohnen. -- Wacholder in “Melanie”
