From owner-freebsd-multimedia  Tue Jun 10 11:48:05 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA23613
          for multimedia-outgoing; Tue, 10 Jun 1997 11:48:05 -0700 (PDT)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA23533
          for <freebsd-multimedia@FreeBSD.ORG>; Tue, 10 Jun 1997 11:47:58 -0700 (PDT)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA06874; Tue, 10 Jun 1997 20:15:15 +0200
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199706101815.UAA06874@labinfo.iet.unipi.it>
Subject: Re: Neat BT848/fxtv problem
To: bad@uhf.wireless.net (Bernie Doehner)
Date: Tue, 10 Jun 1997 20:15:15 +0200 (MET DST)
Cc: tom@inna.net, freebsd-multimedia@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.95.970610130505.2563A-100000@uhf.wdc.net> from "Bernie Doehner" at Jun 10, 97 01:05:27 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-multimedia@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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

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.

	Luigi