Mercurial > mplayer.hg
comparison DOCS/TVout-G400 @ 664:50cca1591b15
Matrox TV-out HOWTO
author | arpi_esp |
---|---|
date | Sun, 29 Apr 2001 22:53:26 +0000 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
663:121cb2047c08 | 664:50cca1591b15 |
---|---|
1 MPlayer TV-out with G400 | |
2 ~~~~~~~~~~~~~~~~~~~~~~~~ | |
3 (this was a reply at the mplayer-matrox list) | |
4 | |
5 > What I'd love to see in mplayer is the the same feature that I see in my | |
6 > windows box. When I start a movie in windows (in a window or in full screen) | |
7 > the movie is also redirected to the tv-out and I can also see it full screen | |
8 > on my tv. I love this feature and was wondering how hard it would be to add | |
9 > such a feature to mplayer. | |
10 | |
11 It's a driver limitation. BES (Back-End Scaler, it's the overlay generator | |
12 and YUV scaling engine of G200/G400/G450 cards) works only with CRTC1. | |
13 Normally, CRTC1 (textmode, every bpp gfx and BES) is routed to HEAD1, | |
14 and CRTC2 (only 16/32bpp gfx) is routed to HEAD2 (TV-out). | |
15 | |
16 Under linux, you have two choices to get TV-out working: | |
17 | |
18 1. Using X 4.0.x + the HAL driver from matrox, so you'll get dual-head | |
19 support, and you'll be able to redirect second output to the TV. | |
20 Unfortunately it has Macrovision encryption enabled, so it will | |
21 only work on directly-connected TV, no through VCR. | |
22 Other problem is that Xv doesn't work on the second head. | |
23 (I don't know how Windows solve it, maybe it swaps the CRTCs between | |
24 the heads, or just uses YUV framebuffer of second DAC with some trick) | |
25 | |
26 2. Using matroxfb with dual-head support enabled (2.4.x kernels). | |
27 You'll be able to get a framebuffer console (using CRTC2, so it's | |
28 slow), and TV-out (using CRTC1, with BES support). | |
29 You have to forget X while using this kind of TV-out! :( | |
30 | |
31 How to enable? | |
32 | |
33 - Compile all the matrox-related things to modules in the kernel. | |
34 (you MUST compile them to modules, at least I couldn't get them | |
35 working built-in yet) | |
36 [reboot to new kernel & install modules, but don't load them yet!] | |
37 | |
38 - Run the 'modules' script from the TV-out directory of mplayer. | |
39 It will switch your console to framebuffer. | |
40 Change to tty1 (ALT+F1)! | |
41 Now run the script 'independent', it will set up your tty's: | |
42 tty 1,2: fb console, CRTC2, head 1 (monitor) | |
43 tty 3,4,5...: framebuffer+BES, CRTC1, head 2 (TV-out) | |
44 You should run the scripts TV-* and Mon-* to set up resolutions: | |
45 change to tty1 (ALT+F1), and run Mon-* (one of them) | |
46 change to tty3 (ALT+F3) and then back to tty1 (ALT+F1) | |
47 (this change will select tty3 on /dev/fb1 - tricky) | |
48 run TV-* (one of them) | |
49 (now you'll get a console on your PAL TV - don't know about NTSC) | |
50 | |
51 Now if you start mplayer (on tty1), the picture will show up on | |
52 the tty3, so you'll see it on your TV or second monitor. | |
53 | |
54 Yes, it is a bit 'hack' now. But I'm waiting for the marvel | |
55 project to be finished, it will provide real TV-out drivers, I hope. | |
56 | |
57 My current problem is that BES is working only with CRTC1. So picture | |
58 will always shown up on head routed to CRTC1 (normaly the monitor), | |
59 so i have to swap CRTC's, but this way your console will framebuffer | |
60 (CRTC2 can't do text-mode) and a bit slow (no acceleration). :( | |
61 | |
62 | |
63 > anyway i also just get monochrome output on the tv ... | |
64 Maybe you have NTSC TV? Or just didn't run one of TV-* scripts. | |
65 | |
66 | |
67 A'rpi / Astral & ESP-team |