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