Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Feb 2002 22:44:52 -0800
From:      Andy Sparrow <spadger@best.com>
To:        Jason Hill <jch@xmission.com>
Cc:        freebsd-multimedia@freebsd.org, "Mike Meyer" <mwm-dated-1014245902.21304d@mired.org>
Subject:   Re: fxtv tweaking/fullscreen? 
Message-ID:  <20020216064452.5A9063E2D@CRWdog.demon.co.uk>
In-Reply-To: Message from Jason Hill <jch@xmission.com>  of "Fri, 15 Feb 2002 21:51:07 MST." <20020215215107.A24575@xmission.com> 

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
> Andy,
> 
> I've checked both dga and xdpyinfo and I've confirmed that I
> have DGA enabled (see output below).  Any other ideas?  The only 
> weirdness that I spot is that some piece of my WinTV card or interface is
> undetected (pci0: <unknown card> (vendor=0x109e, dev=0x0878) at 13.1 irq 11)

Yeah, I get:

bktr0: Hauppauge Model 62471 A2A 
bktr0: Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo.
pci0: <unknown card> (vendor=0x109e, dev=0x0878) at 17.1 irq 16

but it's always said that, and it works fine :)

> but that should prevent me from going fullscreen.

Agreed, so long as you actually meant the negation of the above statement, 
which I suspect you do :)

>  If I can just confirm --
> what resolution do you run X at

I run X @ 1600x1200@85Hz in 16 bit on the machine with the Happauge in it, but 
it'll go fullscreen from 1280x1024, 1024x768, whatever.

> and are you in fact able to view your
> tv window at fullscreen?

Well, what actually happens is that 'fxtv' uses DGA to switch to a video mode 
such that the video window (which is being updated directly from the hardware) 
fills the entire visible area of the screen.

In other words, DGA dynamically switches resolution (and/or color depth, in 
DGA 2.x, available in XFree86-4 only)

However, it doesn't magically generate mode lines for you, and thinking about 
it, that might be what's biting both of you.

For example, for enabling fullscreen with funky-sized AVI/MPEGs and 'mplayer' 
on my laptop I've got the following (fairly common) resolutions defined in my 
XF86Config-4 file:

        Modes       "1024x768" "800x600" "640x480" "544x352" "536x344" 
"480x288"
 "384x288" "320x240" "352x240" "352x280" "352x288"

and the corresponding "mode line" entries elsewhere.

Thus, I get these in my XFree86.0.log file:

(**) ATI(0): Default mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz
(II) ATI(0): Modeline "1024x768"   78.80  1024 1040 1136 1312  768 769 772 800 
+
hsync +vsync
(**) ATI(0): Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) ATI(0): Modeline "800x600"   49.50  800 816 896 1056  600 601 604 625 
+hsyn
c +vsync
(**) ATI(0): Mode "384x288": 15.8 MHz, 36.5 kHz, 58.8 Hz (D)
(II) ATI(0): Modeline "384x288"   15.75  384 400 416 432  288 290 296 310 
double
scan
(**) ATI(0): Mode "320x240": 15.8 MHz, 39.4 kHz, 75.1 Hz (D)
(II) ATI(0): Modeline "320x240"   15.75  320 336 384 400  240 244 246 262 
double
scan
(**) ATI(0): Mode "352x240": 15.8 MHz, 36.5 kHz, 69.6 Hz (D)
(II) ATI(0): Modeline "352x240"   15.75  352 368 416 432  240 244 246 262 
double
scan
(**) ATI(0): Mode "352x280": 15.8 MHz, 36.5 kHz, 60.4 Hz (D)
(II) ATI(0): Modeline "352x280"   15.75  352 368 416 432  280 286 288 302 
double
scan
(**) ATI(0): Mode "352x288": 15.8 MHz, 36.5 kHz, 58.8 Hz (D)
(II) ATI(0): Modeline "352x288"   15.75  352 368 416 432  288 290 296 310 
double
scan

(Note to self, need to fix the bogus modes that get rejected. Ho hum ;-).

However, you see the point, I'm sure - for "standard" modes, you don't need to 
specify mode lines IIRC, but you'll need to enable them for the "Server" entry 
in the config file.

My machine with the WinTV in it only has 1600x1200, 1280x1024, 1024x768, 
800x700, 640x480 defined in the "Display" sections, thus:

        SubSection "Display"
                Depth     16
                Modes       "1600x1200" "1280x1024" "1024x768" "800x600" 
"640x480"

and it has _no mode lines whatsoever_ defined - the server magically creates 
them on-the-fly when it starts.

I get the feeling that something like this (or rsther, the lack of it) might 
be causing your problem.

>  Is it worth trying an older version of fxtv?

Shouldn't think so, I'm using 1.03 as well, and it works exactly the same as 
the older ones, as far as I can tell :)


HTH.

Cheers,

AS



[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE8bf/kPHh895bDXeQRAvN4AKCXaHLFwJeZ57CgcuXi24Grd5I3QACfboZk
ufTqEzeuNcQ/eTKtxAJxlmA=
=oCN6
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020216064452.5A9063E2D>