I'm also wondering about an oddity I'm seeing where when using the
/dev/video48 device, video looks like we are missing frames, it's
jerky on playback.
Yup, i've noticed this too - about one in ~40 frames seems to be dropped on average.
> Also the ghosting image over the
top of playback, never happened originally, was perfect pictures, now it's doing that.
I haven't noticed this - I have however spotted that the saturation/brightness/contrast of the YUV framebuffer is markedly different to the OSD's - more so than I'd expect of a normal RGB->YUV translation such as that which the OSD does. Whilst this may well be a shortcoming of my conversion algorithm, I'm also wondering if it's effected by the colourspace the initialising-MPEG2 was encoded in.
So that's my current thing I'm seeing and trying to figure out, can't see where the code changed enough to switch behavior, but hard to tell since YUV decoding is just tricky and still setup/teardown is so hackish.
setup/teardown is the now the 'only' problem that I'm finding with it. Is there any approach to understanding the ITVC register map in the 0x2800-0x2D00 and 0x82c-0x838 regions other than trial and error? Or is there something as simple as a missing call to IVTV_API_DEC_DECODE_SOURCE happening?
M.
------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
