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? Regards, Corey On 11/17/06, Corey Fehr <[EMAIL PROTECTED]> wrote:
Does anybody have a good handle on the layout of the pvr-350 board, I was hoping for some insight from those more informed than I? I have been playing with scaling of the mpeg video for output via /dev/video16 on the PVR-350. If I use the 'ivtvctl -f' option to perform some scaling on the decoder I would expect that the resizing operation would be taking place on the decoding side right before the signal is output from the card but this is not the case since the encoded mpeg stream that the *PC* receives is even scaled. It was my (obviously faulty) understanding that the saa7115 would be handling the mpeg decoding side exclusively and therefore the video inspected prior to /dev/video16 output would be unaffected. I have also run the tests without using the "ivtvctl -f" call and instead using discrete "ivtvctl -g" calls to affect only the saa7115 registers and it is the same result. a) Can somebody fill me in on the details of the architecture in that the "decoder" register settings are changing the incoming "encoded" mpeg stream? b) Does anybody know of a way to off load the resizing operation to *only* on the decoding side so that I can still grab full 720x480 incoming frames on the PC and output a scaled variant via /dev/video16? I know that there is currently a big push to get new releases out but any help would be appreciated. Thanks again. Regards, Corey
_______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
