On Saturday 18 November 2006 11:35, Hans Verkuil wrote: > On Saturday 18 November 2006 12:25, Ian Armstrong wrote: > > On Saturday 18 November 2006 01:22, Corey Fehr wrote: > > > Ok, I realise my mistake now. :) Let the ribbing begin. > > > > > > The saa7115 registers are affecting the input capture. I suppose > > > that my original questions still stand though. What is the device > > > doing the mepg decoding and to anoyone's knowledge is it capable of > > > resizing output on the fly? > > > > The decoder itself (iTVC15) can resize the video. You'll need the > > ivtv-fb module loaded though. I'm still running an old ivtv build > > here, and the command to resize the mpeg stream being displayed by > > the 350 is something like this... > > > > ivtvfbctl -d /dev/fb0 -w left=350,top=150,width=250,height=200 > > > > I don't think the options really need explaining, though you may need > > to add -v 0 to 'hide' the framebuffer and reveal the video. > > Huh? I always thought this call was specific to the OSD and that it > didn't change the MPEG output. So this is really a generic call that > applies to all of MPEG out, YUV out and OSD out?
I don't believe it does anything to the OSD itself, but simply positions the video output window within the OSD. I've only tried changing the size for MPEG (video16) playback, but it should work for YUV (video48). The scaling & positioning code in ivtv-yuv doesn't use this call, but hits the decoder registers direct allowing for much greater control & avoiding the limitations imposed by the firmware API. The same scaling & position registers affect both MPEG & YUV. -- Ian _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
