From owner-freebsd-multimedia  Tue Jun 10 11:52:37 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA23966
          for multimedia-outgoing; Tue, 10 Jun 1997 11:52:37 -0700 (PDT)
Received: from uhf.wdc.net (uhf.wdc.net [198.147.74.44])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23959
          for <freebsd-multimedia@FreeBSD.ORG>; Tue, 10 Jun 1997 11:52:32 -0700 (PDT)
Received: from localhost (bad@localhost) by uhf.wdc.net (8.8.5/8.6.12) with SMTP id OAA02933; Tue, 10 Jun 1997 14:53:11 -0400 (EDT)
Date: Tue, 10 Jun 1997 14:53:10 -0400 (EDT)
From: Bernie Doehner <bad@uhf.wireless.net>
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
cc: tom@inna.net, freebsd-multimedia@FreeBSD.ORG
Subject: Re: Neat BT848/fxtv problem
In-Reply-To: <199706101815.UAA06874@labinfo.iet.unipi.it>
Message-ID: <Pine.BSF.3.95.970610144950.2928A-100000@uhf.wdc.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-multimedia@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > 
> > BT848_ADC_CRUSH didn't seem to make much of a difference here though (when
> > receiving of an antenna, so I left it in).

I think a clarrification is in order. I am quite far from all TV stations
and was using an indoor dipole antenna (away from the computer), so the
local fluctuations due to changes in location of furniture/people,etc.
made it impossible to really notice a difference.  

The only way for me to really tell is to add a ioctl so I can switch
ADC_CRUSH on/off on the fly.
 
> certainly BT848_ADC_SYNC_T is more important because it allows to
> sync better. I think some AGC decisions  (e.g. the level right
> after sync pulses etc.) are taken assuming the frame is properly
> synchronized, so if you lose sync and leave BT848_ADC_CRUSH on,
> you might run into the fading problem which were mentioned.

Hmmmm..  

Bernie