I've put the insmod settings for bttv below. More than likely your problems
are with one of these options. Playing with the pll option made a big
difference, originally I didn't have it and things were real fuzzy. Once I
added it everything got crystal clear.

My modules config file looks like this. straight from the bttv docs.

# i2c
alias char-major-89     i2c-dev
options i2c-core                i2c_debug=1
options i2c-algo-bit    bit_test=1

# bttv
alias char-major-81     videodev
alias char-major-81-0   bttv
options bttv            card=64 tuner=2 pll=1
options tuner           type=2


bttv.o
        the bt848/878 (grabber chip) driver

        insmod args:
                card=n          card type, see CARDLIST for a list.
                tuner=n         tuner type, see CARDLIST for a list.
                radio=0/1       card supports radio
                pll=0/1/2       pll settings
                        0: don't use PLL
                        1: 28 MHz crystal installed
                        2: 35 MHz crystal installed

                triton1=0/1     for Triton1 (+others) compatibility
                vsfx=0/1        yet another chipset bug compatibility bit
                                see README.quirks for details on these two.

                bigendian=n     Set the endianness of the gfx framebuffer.
                                Default is native endian.
                fieldnr=0/1     Count fields.  Some TV descrambling software
                                needs this, for others it only generates
                                50 useless IRQs/sec.  default is 0 (off).
                autoload=0/1    autoload helper modules (tuner, audio).
                                default is 1 (on).
                bttv_verbose=0/1/2  verbose level (at insmod time, while
                                looking at the hardware).  default is 1.
                bttv_debug=0/1  debug messages (for capture).
                                default is 0 (off).
                irq_debug=0/1   irq handler debug messages.
                                default is 0 (off).
                gbuffers=2-32   number of capture buffers for mmap'ed capture.
                                default is 4.
                gbufsize=       size of capture buffers. default and
                                maximum value is 0x208000 (~2MB)
                no_overlay=0    Enable overlay on broken hardware.  There
                                are some chipsets (SIS for example) which
                                are known to have problems with the PCI DMA
                                push used by bttv.  bttv will disable overlay
                                by default on this hardware to avoid crashes.
                                With this insmod option you can override this.
                automute=0/1    Automatically mutes the sound if there is
                                no TV signal, on by default.  You might try
                                to disable this if you have bad input signal
                                quality which leading to unwanted sound
                                dropouts.
                chroma_agc=0/1  AGC of chroma signal, off by default.
                adc_crush=0/1   Luminance ADC crush, on by default.

                bttv_gpio=0/1
                gpiomask=
                audioall=
                audiomux=
                                See Sound-FAQ for a detailed description.

        remap, card, radio and pll accept up to four comma-separated arguments
        (for multiple boards).

tuner.o
        The tuner driver.  You need this unless you want to use only
        with a camera or external tuner ...

        insmod args:
                debug=1         print some debug info to the syslog
                type=n          type of the tuner chip. n as follows:
                                see CARDLIST for a complete list.
                pal=[bdgil]     select PAL variant (used for some tuners
                                only, important for the audio carrier).


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Alan
Murrell
Sent: Wednesday, February 26, 2003 10:25 AM
To: [EMAIL PROTECTED]
Subject: Re: [Freevo-devel] Another Tv Viewing problem...


Hi Krister,

--- Krister Lagerstrom <[EMAIL PROTECTED]> wrote:
> Tuner=3 refers to the tuner channel setting in this

Ah, okay, that makes some sense I guess.  Darn,
thought I figured out the source of the problem :-)

> Try starting other channels to see the difference.

Yup, that's definately it.  I tired a couple other
channels, and the 'tuner=' value was the same as the
'channel=' value.

Hrm, if the MPlayer frequency table is screwed up (and
I know that was just a guess on your part), is that
something that I can fix in the config?  I have tried
both 'us-cable' and 'canada-cable' (since I live in
Canada), but with the same result.

Alan


______________________________________________________________________
Post your free ad now! http://personals.yahoo.ca


-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to