|
>> 1) the window xawtv uses to display the frames is
not resized to a
>> particular resolution that xawtv successfully asked with the appropriate >> ioctl. I have to do it manually. Any idea? >> (I don't think the problem is the window manager). >xawtv simply doesn't resize the window on its own. Instead it asks >the driver for a frame size matching the current window size. If it >doesn't fit (because the hardware doesn't support random image sizes >for example) the image is centered. If it is centered, xawtv doesn't display
it in correctly...i've to resize it by hand to see the image.
>IMHO this is better from a usability view. The user should control >the application, not the other way around. I agree with you. >> 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've some problems with other v4l apps too
which make me think there's a bug in the v4l1 interface and
i am pretty sure that every method is correctly implemented in my
driver...
|
