> (resent to ivtv-devel; no answer on ivtv-users)
>
> Hi list,
>
> I seem to have the same problem that Chris Vargas wrote about in a message
> to
> the ivtv-users list a week or so ago:
>
>   http://www.gossamer-threads.com/lists/ivtv/users/35932
>
> Basically there seems to be a problem with the horizontal sync in the ivtv
> tuner code (?). Here's a screenshot:
>
>   http://ward.vandewege.net/horiz_sync_problem_ivtv.jpg
>
> This is on ivtv 0.10.3, with MythTV 0.20, and the card is an older PVR-350
> PAL version, which has worked fine for several years.
>
> Older recordings (made with 0.7.0) still play fine without these
> artefacts.
> All new recordings are like the above, as is watching live TV. Sometimes
> there are short fragments where the sync issue is not as bad. The sync
> issue
> is always identical when playing a recording repeatedly; the data has been
> recorded badly, playback seems just fine.
>
> I was running ivtv 0.7.0 without problems, and when I upgraded to 0.10.0
> in
> March, I hit the driver issue with vertical syncronization, see this
> thread:
>
>   http://www.gossamer-threads.com/lists/ivtv/devel/35290?do=post_view_threaded
>
> This resulted in a black bar at the top 1/3 of the screen when changing
> channels.
>
> That got fixed in 0.10.1 (the black bar is now removed in a fraction of a
> second), but the horizontal sync issue remains (I've tested 0.10.1 and
> 0.10.3).
>
> Any thoughts? Further debugging I can do? The dmesg output follows below.
>
> Thanks,
> Ward.
>
> ivtv:  ==================== START INIT IVTV ====================
> ivtv:  version 0.10.3 (tagged release) loading
> ivtv:  Linux version: 2.6.20.4 preempt mod_unload K7

Can you upgrade to a 2.6.21 kernel? See if it still happens. If so, then
also test (after a reboot, so everything is cleanly setup) if just doing
'cat /dev/video0 >foo.mpg' also shows the same artifacts (this eliminates
MythTV as a possible, if unlikely, cause).

The most likely cause seems to be the saa7115 video digitizer and I know
some changes were made by others in this module. Back home I use the
2.6.21 kernel and I don't think I've ever seen these artifacts. But to be
honest I'm fairly certain that I've also tested with a 2.6.20 kernel in
the past and it worked fine with that kernel as well.

Regards,

         Hans


_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to