|
I have just commited my changes to svn for the yuv
playback. The commit message was Log: YUV playback now always
defaults to interlaced. There are now 3 modes
interlace,progressive & auto. There are 2 new ioctl's to
set & get the mode & the threshold used for auto. There are 2 new options to
ivtvctl to get & set the mode and threshold --set-yuv-mode &
--get-yuv-mode. There are 2 new module load
options to set the default values ivtv_yuv_mode & ivtv_yuv_threshold. The yuv playback code has
been altered to cope with the mode being changed whilst in the moddle of
playing back something. The change here is that until now anything with a source
height of 480 lines or less was treated as progressive video and the 350 was
set up to play back like this. As long as it is being fed a progressive video
stream this works well and doubles the frame rate which works well for xmame. However if it is being fed an interlaced video stream then
it doesn’t display complete frames. This is I suspect what has been
causing the comments about jumpy playback. With this commit the default changes to always being
interlaced but the mode can be changed with either kernel load options or
options to ivtvctl. It would make sense for instance to wrap xmame in a script
that sets progressive mode at the start and restores interlaced mode on exit. To change back to the original settings you would either
specify the module load options ivtv_yuv_mode=2 ivtv_yuv_threshold=480 or after loading the module you could use ivtvctl ivtvctl –set-yuv-mode=mode=2,threshold=480 Any problems let me know. John |
- [ivtv-devel] Change in yuv playback in 0.3.8 version John Harvey
- Re: [ivtv-devel] Change in yuv playback in 0.3.8 vers... Graeme Wilford
- Re: [ivtv-devel] Change in yuv playback in 0.3.8 ... Jesse Guardiani
- RE: [ivtv-devel] Change in yuv playback in 0.... John Harvey
- Re: [ivtv-devel] Change in yuv playback in 0.3.8 vers... Jerome Hettich
