Thanks, Devin. Below is the output of azap. I'm assuming that the errors are
occurring at the same time the video/audio glitches would be. I think it is
slightly worse on some channels than on others (but not drastically). The
example below is from one of the worse channels.
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 799789900 Hz
video pid 0x0000, audio pid 0x0000
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 1f | signal 013e | snr 013e | ber 000019a7 | unc 000019a7 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000267 | unc 00000267 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000264 | unc 00000264 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0146 | snr 0146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0145 | snr 0145 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> Date: Fri, 12 Feb 2010 15:24:54 -0500
> From: [email protected]
> To: [email protected]
> Subject: Re: [ivtv-users] hvr-1600, frame CRC mismatch - incomplete frame
>
> On Fri, Feb 12, 2010 at 3:15 PM, Kyle Lil <[email protected]> wrote:
> > I'm using the latest version of the cx18 drivers available from the
> > linuxtv.org mercurial repository, which, as I understand, includes the
> > latest performance tweaks for the Hauppage HVR-1600 by Devin Heitmueller.
> > Unfortunately, I'm still getting occasional (~every 30 seconds) glitches in
> > the video (watching with MythTV 0.22, Karmic x64), accompanied by an audible
> > buzz, and the following error message in the mythfrontend.log:
> >
> > 2010-02-11 20:11:25.510 [ac3 @ 0x7fa2a884c820]frame CRC mismatch
> > 2010-02-11 20:11:25.543 [ac3 @ 0x7fa2a884c820]incomplete frame
> > 2010-02-11 20:11:25.543 [ac3 @ 0x7fa2a884c820]invalid frame size
> >
> > The card is capable of tuning the same channel with no apparent errors in
> > Windows XP.
> >
> > Please let me know if I can provide any other information to help
> > troubleshoot this problem.
>
> I would suggest using azap to tune to the target channel, and then
> watch the BER/UNC counts when the errors appear. That will give us
> some idea whether the problem is with the frontend, or whether it's
> with the bridge.
>
> Also, do you see the issue with *all* channels? Or just particular
> channels? And what is the SNR on the channels in question that show
> the problem?
>
> Devin
>
> --
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/201469227/direct/01/_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
