From 4abe6d29df26fb08481a866f7b3f13d05df1a12a Mon Sep 17 00:00:00 2001 From: gabucino Date: Fri, 26 Oct 2001 17:19:13 +0000 Subject: rewritten matrox tvout section git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@2487 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/video.html | 158 ++++++++++++++++++++++---------------------------------- 1 file changed, 63 insertions(+), 95 deletions(-) (limited to 'DOCS/video.html') diff --git a/DOCS/video.html b/DOCS/video.html index f7d2ba9539..1c36495a84 100644 --- a/DOCS/video.html +++ b/DOCS/video.html @@ -707,102 +707,70 @@ your PC since video BIOS initializes itself only once during POST procedure.

2.2.1.A.1. Matrox cards

-

What I'd love to see in mplayer is the the same feature that I see in my -windows box. When I start a movie in windows (in a window or in full screen) -the movie is also redirected to the tv-out and I can also see it full screen -on my tv. I love this feature and was wondering how hard it would be to add -such a feature to mplayer.

- -

It's a driver limitation. BES (Back-End Scaler, it's the overlay generator -and YUV scaling engine of G200/G400/G450/G550 cards) works only with CRTC1. -Normally, CRTC1 (textmode, every bpp gfx and BES) is routed to HEAD1, -and CRTC2 (only 16/32bpp gfx) is routed to HEAD2 (TV-out).

- -

Under linux, you have two choices to get TV-out working:

- -

- -

Follow these instructions:

- -

- -You should edit your config file, to contain the screenw and -screenh options (the first should be set to the horizontal -resolution of the framebuffer, and the latter to the vertical. See -example.conf). This is required for fullscreen playing, and for -the aspect code to work.

- -

Yes, it is a bit 'hack' now. But I'm waiting for the marvel -project to be finished, it will provide real TV-out drivers, I hope.

- -

My current problem is that BES is working only with CRTC1. So picture -will always shown up on head routed to CRTC1 (normaly the monitor), -so i have to swap CRTC's, but this way your console will framebuffer -(CRTC2 can't do text-mode) and a bit slow (no acceleration). :(

- -

Anyway i also just get monochrome output on the tv ...
-Maybe you have NTSC TV? Or just didn't run one of TV-* scripts.

- - -

2.2.1.A.1a. Matrox cards (method 2 - the XFree approach)

- -

The previous method doesn't work very good for X users, since either they -have to shutdown it, or it becomes uselessly messy. This section is for them.

+

Under Linux you have 2 methods to get TV out working :

-

  • compile the matroxfb stuff to modules
  • -
  • load modules with the ./modules script
  • -
  • turn on display cloning with ./cloning . This way CRTC2 -won't be used, CRTC1 will display on both heads. -
  • execute ./TV-640x512 or whichever resolution you -wish to use
  • +

    -

    Now you should have a clean picture on the TV, and maybe a somewhat strange -picture on the monitor. But monitor doesn't matter, start X. Your TV -goes black or have strange stripes, but monitor/X is fine !
    - -

    -So, anytime you want to start watching something on TV, just start -MPlayer in X with the -vo mga -screenw XXX -screenh XXX -(write the horizontal and vertical resolution of your framebuffer to the XXX's, -respectively) options, change to tty1 (with ctrl-alt-f1), and turn off the -monitor. -

    2.2.1.A.2. ATI cards

    @@ -853,8 +821,8 @@ movies on their TV through VESA drivers.

    -I should say good words into address of ATI Inc. too:
    -it produces top quality BIOSes. +I should say good words to ATI Inc. too:
    +they produce top quality BIOSes.

    @@ -865,7 +833,7 @@ chips with 64 - 128-bit access) so it's not bottleneck for them. There are no limitations on which video mode can be displayed on your TV (like on other cards) so you can use any video mode on your TV (from 320x200 up to 1024x768).
    -Only thing you need to do - have plugged tv-connector in before booting your +Only thing you need to do - have TV connector plugged in before booting your PC since video BIOS initializes itself only once during POST procedure.

    -- cgit v1.2.3