Mercurial > mplayer.hg
annotate DOCS/xml/en/tvinput.xml @ 31896:b5636b1d006c
Remove empty paragraph from TV input chapter.
author | diego |
---|---|
date | Wed, 18 Aug 2010 19:51:06 +0000 |
parents | 89ba6df5d766 |
children |
rev | line source |
---|---|
20535 | 1 <?xml version="1.0" encoding="utf-8"?> |
10913
49b1a67e7381
Add revision keyword to english xml files, to ease translation synchronization
lumag
parents:
9948
diff
changeset
|
2 <!-- $Revision$ --> |
31753 | 3 <chapter id="tv-input" xreflabel="TV input"> |
9675 | 4 <title>TV input</title> |
5 | |
6 <para> | |
7 This section is about how to enable <emphasis role="bold">watching/grabbing | |
9776
861a40949bf3
fixes, some by Dmitry Baryshkov <lumag@qnc.ru>, some by me
nicolas
parents:
9683
diff
changeset
|
8 from V4L compatible TV tuner</emphasis>. See the man page for a description |
861a40949bf3
fixes, some by Dmitry Baryshkov <lumag@qnc.ru>, some by me
nicolas
parents:
9683
diff
changeset
|
9 of TV options and keyboard controls. |
9675 | 10 </para> |
11 | |
21521 | 12 <!-- ********** --> |
9675 | 13 |
31753 | 14 <sect1 id="tv-tips"> |
9675 | 15 <title>Usage tips</title> |
21521 | 16 |
9675 | 17 <para> |
18 The full listing of the options is available on the manual page. | |
19 Here are just a few tips: | |
21521 | 20 |
9675 | 21 <itemizedlist> |
21521 | 22 <listitem><para> |
31866
89ba6df5d766
Remove pointless compilation sections from radio and TV input chapters.
diego
parents:
31857
diff
changeset
|
23 Make sure your tuner works with another TV software in Linux, for |
89ba6df5d766
Remove pointless compilation sections from radio and TV input chapters.
diego
parents:
31857
diff
changeset
|
24 example <application>XawTV</application>. |
89ba6df5d766
Remove pointless compilation sections from radio and TV input chapters.
diego
parents:
31857
diff
changeset
|
25 </para></listitem> |
89ba6df5d766
Remove pointless compilation sections from radio and TV input chapters.
diego
parents:
31857
diff
changeset
|
26 <listitem><para> |
21521 | 27 Use the <option>channels</option> option. An example: |
28 <screen>-tv channels=26-MTV1,23-TV2</screen> | |
23516 | 29 Explanation: Using this option, only the 26 and 23 channels will be usable, |
21521 | 30 and there will be a nice OSD text upon channel switching, displaying the |
31 channel's name. Spaces in the channel name must be replaced by the | |
21596 | 32 "_" character. |
21521 | 33 </para></listitem> |
34 <listitem><para> | |
35 Choose some sane image dimensions. The dimensions of the resulting image | |
36 should be divisible by 16. | |
28966 | 37 </para></listitem> |
9675 | 38 <listitem> |
21521 | 39 <para> |
40 If you capture the video with the vertical resolution higher than half | |
41 of the full resolution (i.e. 288 for PAL or 240 for NTSC), then the | |
42 'frames' you get will really be interleaved pairs of fields. | |
43 Depending on what you want to do with the video you may leave it in | |
44 this form, destructively deinterlace, or break the pairs apart into | |
45 individual fields. | |
46 </para> | |
47 <para> | |
48 Otherwise you'll get a movie which is distorted during | |
49 fast-motion scenes and the bitrate controller will be probably even unable | |
50 to retain the specified bitrate as the interlacing artifacts produce high | |
51 amount of detail and thus consume lot of bandwidth. You can enable | |
52 deinterlacing with <option>-vf pp=DEINT_TYPE</option>. | |
53 Usually <option>pp=lb</option> does a good job, but it can be matter of | |
54 personal preference. | |
55 See other deinterlacing algorithms in the manual and give it a try. | |
56 </para> | |
9675 | 57 </listitem> |
21521 | 58 <listitem><para> |
59 Crop out the dead space. When you capture the video, the areas at the edges | |
60 are usually black or contain some noise. These again consume lots of | |
61 unnecessary bandwidth. More precisely it's not the black areas themselves | |
62 but the sharp transitions between the black and the brighter video image | |
63 which do but that's not important for now. Before you start capturing, | |
64 adjust the arguments of the <option>crop</option> option so that all the | |
65 crap at the margins is cropped out. Again, don't forget to keep the resulting | |
66 dimensions sane. | |
67 </para></listitem> | |
68 <listitem><para> | |
69 Watch out for CPU load. It shouldn't cross the 90% boundary for most of the | |
70 time. If you have a large capture buffer, <application>MEncoder</application> | |
71 can survive an overload for few seconds but nothing more. It's better to | |
72 turn off the 3D OpenGL screensavers and similar stuff. | |
28966 | 73 </para></listitem> |
21521 | 74 <listitem><para> |
75 Don't mess with the system clock. <application>MEncoder</application> uses the | |
76 system clock for doing A/V sync. If you adjust the system clock (especially | |
77 backwards in time), <application>MEncoder</application> gets confused and you | |
78 will lose frames. This is an important issue if you are hooked to a network | |
79 and run some time synchronization software like NTP. You have to turn NTP | |
80 off during the capture process if you want to capture reliably. | |
81 </para></listitem> | |
82 <listitem><para> | |
83 Don't change the <option>outfmt</option> unless you know what you are doing | |
84 or your card/driver really doesn't support the default (YV12 colorspace). | |
85 In the older versions of <application>MPlayer</application>/ | |
86 <application>MEncoder</application> it was necessary to specify the output | |
87 format. This issue should be fixed in the current releases and | |
88 <option>outfmt</option> isn't required anymore, and the default suits the | |
89 most purposes. For example, if you are capturing into DivX using | |
90 <systemitem class="library">libavcodec</systemitem> and specify | |
91 <option>outfmt=RGB24</option> in order to increase the quality of the captured | |
92 images, the captured image will be actually later converted back into YV12 so | |
93 the only thing you achieve is a massive waste of CPU power. | |
94 </para></listitem> | |
95 <listitem><para> | |
96 There are several ways of capturing audio. You can grab the sound either using | |
97 your sound card via an external cable connection between video card and | |
98 line-in, or using the built-in ADC in the bt878 chip. In the latter case, you | |
99 have to load the <emphasis role="bold">btaudio</emphasis> driver. Read the | |
100 <filename>linux/Documentation/sound/btaudio</filename> file (in the kernel | |
101 tree, not <application>MPlayer</application>'s) for some instructions on using | |
102 this driver. | |
28966 | 103 </para></listitem> |
21521 | 104 <listitem><para> |
105 If <application>MEncoder</application> cannot open the audio device, make | |
106 sure that it is really available. There can be some trouble with the sound | |
107 servers like aRts (KDE) or ESD (GNOME). If you have a full duplex sound card | |
108 (almost any decent card supports it today), and you are using KDE, try to | |
109 check the "full duplex" option in the sound server preference menu. | |
110 </para></listitem> | |
9675 | 111 </itemizedlist> |
21732 | 112 </para> |
31753 | 113 </sect1> |
9675 | 114 |
21521 | 115 <!-- ********** --> |
9675 | 116 |
31753 | 117 <sect1 id="tv-examples"> |
9675 | 118 <title>Examples</title> |
119 | |
21521 | 120 <informalexample><para> |
9675 | 121 Dummy output, to AAlib :) |
21521 | 122 <screen>mplayer -tv driver=dummy:width=640:height=480 -vo aa tv://</screen> |
123 </para></informalexample> | |
9675 | 124 |
21521 | 125 <informalexample><para> |
9675 | 126 Input from standard V4L: |
127 <screen> | |
21521 | 128 mplayer -tv driver=v4l:width=640:height=480:outfmt=i420 -vc rawi420 -vo xv tv:// |
129 </screen> | |
130 </para></informalexample> | |
9675 | 131 |
21521 | 132 <informalexample><para> |
11540 | 133 A more sophisticated example. This makes <application>MEncoder</application> |
134 capture the full PAL image, crop the margins, and deinterlace the picture | |
135 using a linear blend algorithm. Audio is compressed with a constant bitrate | |
136 of 64kbps, using LAME codec. This setup is suitable for capturing movies. | |
9675 | 137 <screen> |
21521 | 138 mencoder -tv driver=v4l:width=768:height=576 -oac mp3lame -lameopts cbr:br=64\ |
139 -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=900 \ | |
140 -vf crop=720:544:24:16,pp=lb -o <replaceable>output.avi</replaceable> tv:// | |
9675 | 141 </screen> |
21521 | 142 </para></informalexample> |
9675 | 143 |
21521 | 144 <informalexample><para> |
9675 | 145 This will additionally rescale the image to 384x288 and compresses the |
146 video with the bitrate of 350kbps in high quality mode. The vqmax option | |
11271
252fb0cf331a
spelling fixes, mostly by <ismail.donmez@boun.edu.tr>
diego
parents:
10913
diff
changeset
|
147 looses the quantizer and allows the video compressor to actually reach so |
9675 | 148 low bitrate even at the expense of the quality. This can be used for |
149 capturing long TV series, where the video quality isn't so important. | |
150 <screen> | |
21521 | 151 mencoder -tv driver=v4l:width=768:height=576 \ |
152 -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=350:vhq:vqmax=31:keyint=300 \ | |
153 -oac mp3lame -lameopts cbr:br=48 -sws 1 -o <replaceable>output.avi</replaceable>\ | |
154 -vf crop=720:540:24:18,pp=lb,scale=384:288 tv:// | |
9675 | 155 </screen> |
21521 | 156 It's also possible to specify smaller image dimensions in the |
157 <option>-tv</option> option and omit the software scaling but this approach | |
158 uses the maximum available information and is a little more resistant to noise. | |
159 The bt8x8 chips can do the pixel averaging only in the horizontal direction due | |
160 to a hardware limitation. | |
161 </para></informalexample> | |
9675 | 162 </sect1> |
31753 | 163 </chapter> |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
17280
diff
changeset
|
164 |
24584 | 165 |
166 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
167 | |
168 | |
31753 | 169 <chapter id="tv-teletext"> |
24584 | 170 <title>Teletext</title> |
171 | |
172 <para> | |
27018 | 173 Teletext is currently available only in <application>MPlayer</application> |
174 for v4l and v4l2 drivers. | |
24584 | 175 </para> |
176 | |
31753 | 177 <sect1 id="tv-teletext-implementation-notes"> |
24584 | 178 <title>Implementation notes</title> |
179 | |
180 <para> | |
181 <application>MPlayer</application> supports regular text, graphics and navigation links. | |
182 Unfortunately, colored pages are not fully supported yet - all pages are shown as grayscaled. | |
183 Subtitle pages (also known as Closed Captions) are supported, too. | |
184 </para> | |
185 | |
186 <para> | |
187 <application>MPlayer</application> starts caching all teletext pages upon | |
188 starting to receive TV input, so you do not need to wait until the requested page is loaded. | |
189 </para> | |
190 | |
191 <para> | |
192 Note: Using teletext with <option>-vo xv</option> causes strange colors. | |
193 </para> | |
31753 | 194 </sect1> |
24584 | 195 |
31753 | 196 <sect1 id="tv-teletext-usage"> |
24584 | 197 <title>Using teletext</title> |
198 | |
199 <para> | |
200 To enable teletext decoding you must specify the VBI device to get teletext data | |
201 from (usually <filename>/dev/vbi0</filename> for Linux). This can be done by specifying | |
202 <option>tdevice</option> in your configuration file, like shown below: | |
203 <screen>tv=tdevice=/dev/vbi0</screen> | |
204 </para> | |
205 | |
206 <para> | |
207 You might need to specify the teletext language code for your country. | |
208 To list all available country codes use | |
209 <screen>tv=tdevice=/dev/vbi0:tlang=<replaceable>-1</replaceable></screen> | |
210 Here is an example for Russian: | |
211 <screen>tv=tdevice=/dev/vbi0:tlang=<replaceable>33</replaceable></screen> | |
212 </para> | |
31753 | 213 </sect1> |
24584 | 214 |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
17280
diff
changeset
|
215 </chapter> |