You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1110 lines
33KB

  1. @chapter Input Devices
  2. @c man begin INPUT DEVICES
  3. Input devices are configured elements in FFmpeg which allow to access
  4. the data coming from a multimedia device attached to your system.
  5. When you configure your FFmpeg build, all the supported input devices
  6. are enabled by default. You can list all available ones using the
  7. configure option "--list-indevs".
  8. You can disable all the input devices using the configure option
  9. "--disable-indevs", and selectively enable an input device using the
  10. option "--enable-indev=@var{INDEV}", or you can disable a particular
  11. input device using the option "--disable-indev=@var{INDEV}".
  12. The option "-devices" of the ff* tools will display the list of
  13. supported input devices.
  14. A description of the currently available input devices follows.
  15. @section alsa
  16. ALSA (Advanced Linux Sound Architecture) input device.
  17. To enable this input device during configuration you need libasound
  18. installed on your system.
  19. This device allows capturing from an ALSA device. The name of the
  20. device to capture has to be an ALSA card identifier.
  21. An ALSA identifier has the syntax:
  22. @example
  23. hw:@var{CARD}[,@var{DEV}[,@var{SUBDEV}]]
  24. @end example
  25. where the @var{DEV} and @var{SUBDEV} components are optional.
  26. The three arguments (in order: @var{CARD},@var{DEV},@var{SUBDEV})
  27. specify card number or identifier, device number and subdevice number
  28. (-1 means any).
  29. To see the list of cards currently recognized by your system check the
  30. files @file{/proc/asound/cards} and @file{/proc/asound/devices}.
  31. For example to capture with @command{ffmpeg} from an ALSA device with
  32. card id 0, you may run the command:
  33. @example
  34. ffmpeg -f alsa -i hw:0 alsaout.wav
  35. @end example
  36. For more information see:
  37. @url{http://www.alsa-project.org/alsa-doc/alsa-lib/pcm.html}
  38. @section avfoundation
  39. AVFoundation input device.
  40. AVFoundation is the currently recommended framework by Apple for streamgrabbing on OSX >= 10.7 as well as on iOS.
  41. The older QTKit framework has been marked deprecated since OSX version 10.7.
  42. The input filename has to be given in the following syntax:
  43. @example
  44. -i "[[VIDEO]:[AUDIO]]"
  45. @end example
  46. The first entry selects the video input while the latter selects the audio input.
  47. The stream has to be specified by the device name or the device index as shown by the device list.
  48. Alternatively, the video and/or audio input device can be chosen by index using the
  49. @option{
  50. -video_device_index <INDEX>
  51. }
  52. and/or
  53. @option{
  54. -audio_device_index <INDEX>
  55. }
  56. , overriding any
  57. device name or index given in the input filename.
  58. All available devices can be enumerated by using @option{-list_devices true}, listing
  59. all device names and corresponding indices.
  60. There are two device name aliases:
  61. @table @code
  62. @item default
  63. Select the AVFoundation default device of the corresponding type.
  64. @item none
  65. Do not record the corresponding media type.
  66. This is equivalent to specifying an empty device name or index.
  67. @end table
  68. @subsection Options
  69. AVFoundation supports the following options:
  70. @table @option
  71. @item -list_devices <TRUE|FALSE>
  72. If set to true, a list of all available input devices is given showing all
  73. device names and indices.
  74. @item -video_device_index <INDEX>
  75. Specify the video device by its index. Overrides anything given in the input filename.
  76. @item -audio_device_index <INDEX>
  77. Specify the audio device by its index. Overrides anything given in the input filename.
  78. @item -pixel_format <FORMAT>
  79. Request the video device to use a specific pixel format.
  80. If the specified format is not supported, a list of available formats is given
  81. und the first one in this list is used instead. Available pixel formats are:
  82. @code{monob, rgb555be, rgb555le, rgb565be, rgb565le, rgb24, bgr24, 0rgb, bgr0, 0bgr, rgb0,
  83. bgr48be, uyvy422, yuva444p, yuva444p16le, yuv444p, yuv422p16, yuv422p10, yuv444p10,
  84. yuv420p, nv12, yuyv422, gray}
  85. @end table
  86. @subsection Examples
  87. @itemize
  88. @item
  89. Print the list of AVFoundation supported devices and exit:
  90. @example
  91. $ ffmpeg -f avfoundation -list_devices true -i ""
  92. @end example
  93. @item
  94. Record video from video device 0 and audio from audio device 0 into out.avi:
  95. @example
  96. $ ffmpeg -f avfoundation -i "0:0" out.avi
  97. @end example
  98. @item
  99. Record video from video device 2 and audio from audio device 1 into out.avi:
  100. @example
  101. $ ffmpeg -f avfoundation -video_device_index 2 -i ":1" out.avi
  102. @end example
  103. @item
  104. Record video from the system default video device using the pixel format bgr0 and do not record any audio into out.avi:
  105. @example
  106. $ ffmpeg -f avfoundation -pixel_format bgr0 -i "default:none" out.avi
  107. @end example
  108. @end itemize
  109. @section bktr
  110. BSD video input device.
  111. @section dshow
  112. Windows DirectShow input device.
  113. DirectShow support is enabled when FFmpeg is built with the mingw-w64 project.
  114. Currently only audio and video devices are supported.
  115. Multiple devices may be opened as separate inputs, but they may also be
  116. opened on the same input, which should improve synchronism between them.
  117. The input name should be in the format:
  118. @example
  119. @var{TYPE}=@var{NAME}[:@var{TYPE}=@var{NAME}]
  120. @end example
  121. where @var{TYPE} can be either @var{audio} or @var{video},
  122. and @var{NAME} is the device's name or alternative name..
  123. @subsection Options
  124. If no options are specified, the device's defaults are used.
  125. If the device does not support the requested options, it will
  126. fail to open.
  127. @table @option
  128. @item video_size
  129. Set the video size in the captured video.
  130. @item framerate
  131. Set the frame rate in the captured video.
  132. @item sample_rate
  133. Set the sample rate (in Hz) of the captured audio.
  134. @item sample_size
  135. Set the sample size (in bits) of the captured audio.
  136. @item channels
  137. Set the number of channels in the captured audio.
  138. @item list_devices
  139. If set to @option{true}, print a list of devices and exit.
  140. @item list_options
  141. If set to @option{true}, print a list of selected device's options
  142. and exit.
  143. @item video_device_number
  144. Set video device number for devices with same name (starts at 0,
  145. defaults to 0).
  146. @item audio_device_number
  147. Set audio device number for devices with same name (starts at 0,
  148. defaults to 0).
  149. @item pixel_format
  150. Select pixel format to be used by DirectShow. This may only be set when
  151. the video codec is not set or set to rawvideo.
  152. @item audio_buffer_size
  153. Set audio device buffer size in milliseconds (which can directly
  154. impact latency, depending on the device).
  155. Defaults to using the audio device's
  156. default buffer size (typically some multiple of 500ms).
  157. Setting this value too low can degrade performance.
  158. See also
  159. @url{http://msdn.microsoft.com/en-us/library/windows/desktop/dd377582(v=vs.85).aspx}
  160. @item video_pin_name
  161. Select video capture pin to use by name or alternative name.
  162. @item audio_pin_name
  163. Select audio capture pin to use by name or alternative name.
  164. @item crossbar_video_input_pin_number
  165. Select video input pin number for crossbar device. This will be
  166. routed to the crossbar device's Video Decoder output pin.
  167. @item crossbar_audio_input_pin_number
  168. Select audio input pin number for crossbar device. This will be
  169. routed to the crossbar device's Audio Decoder output pin.
  170. @item show_video_device_dialog
  171. If set to @option{true}, before capture starts, popup a display dialog
  172. to the end user, allowing them to change video filter properties
  173. and configurations manually.
  174. Note that for crossbar devices, this may be needed at times to toggle
  175. between PAL and NTSC input frame rates and sizes, etc. Possibly
  176. enabling different scan rates/frame rates and avoiding green bars at
  177. the bottom, etc.
  178. @item show_audio_device_dialog
  179. If set to @option{true}, before capture starts, popup a display dialog
  180. to the end user, allowing them to change audio filter properties
  181. and configurations manually.
  182. @item show_crossbar_connection_dialog
  183. If set to @option{true}, before capture starts, popup a display
  184. dialog to the end user, allowing them to manually
  185. modify crossbar pin routings.
  186. @item show_analog_tv_tuner_dialog
  187. If set to @option{true}, before capture starts, popup a display
  188. dialog to the end user, allowing them to manually
  189. modify TV channels and frequencies.
  190. @item show_analog_tv_tuner_audio_dialog
  191. If set to @option{true}, before capture starts, popup a display
  192. dialog to the end user, allowing them to manually
  193. modify TV audio (like mono vs. stereo, Language A,B or C).
  194. @end table
  195. @subsection Examples
  196. @itemize
  197. @item
  198. Print the list of DirectShow supported devices and exit:
  199. @example
  200. $ ffmpeg -list_devices true -f dshow -i dummy
  201. @end example
  202. @item
  203. Open video device @var{Camera}:
  204. @example
  205. $ ffmpeg -f dshow -i video="Camera"
  206. @end example
  207. @item
  208. Open second video device with name @var{Camera}:
  209. @example
  210. $ ffmpeg -f dshow -video_device_number 1 -i video="Camera"
  211. @end example
  212. @item
  213. Open video device @var{Camera} and audio device @var{Microphone}:
  214. @example
  215. $ ffmpeg -f dshow -i video="Camera":audio="Microphone"
  216. @end example
  217. @item
  218. Print the list of supported options in selected device and exit:
  219. @example
  220. $ ffmpeg -list_options true -f dshow -i video="Camera"
  221. @end example
  222. @item
  223. Specify pin names to capture by name or alternative name, specify alternative device name:
  224. @example
  225. $ ffmpeg -f dshow -audio_pin_name "Audio Out" -video_pin_name 2 -i video=video="@@device_pnp_\\?\pci#ven_1a0a&dev_6200&subsys_62021461&rev_01#4&e2c7dd6&0&00e1#@{65e8773d-8f56-11d0-a3b9-00a0c9223196@}\@{ca465100-deb0-4d59-818f-8c477184adf6@}":audio="Microphone"
  226. @end example
  227. @item
  228. Configure a crossbar device, specifying crossbar pins, allow user to adjust video capture properties at startup:
  229. @example
  230. $ ffmpeg -f dshow -show_video_device_dialog true -crossbar_video_input_pin_number 0
  231. -crossbar_audio_input_pin_number 3 -i video="AVerMedia BDA Analog Capture":audio="AVerMedia BDA Analog Capture"
  232. @end example
  233. @end itemize
  234. @section dv1394
  235. Linux DV 1394 input device.
  236. @section fbdev
  237. Linux framebuffer input device.
  238. The Linux framebuffer is a graphic hardware-independent abstraction
  239. layer to show graphics on a computer monitor, typically on the
  240. console. It is accessed through a file device node, usually
  241. @file{/dev/fb0}.
  242. For more detailed information read the file
  243. Documentation/fb/framebuffer.txt included in the Linux source tree.
  244. To record from the framebuffer device @file{/dev/fb0} with
  245. @command{ffmpeg}:
  246. @example
  247. ffmpeg -f fbdev -r 10 -i /dev/fb0 out.avi
  248. @end example
  249. You can take a single screenshot image with the command:
  250. @example
  251. ffmpeg -f fbdev -frames:v 1 -r 1 -i /dev/fb0 screenshot.jpeg
  252. @end example
  253. See also @url{http://linux-fbdev.sourceforge.net/}, and fbset(1).
  254. @section gdigrab
  255. Win32 GDI-based screen capture device.
  256. This device allows you to capture a region of the display on Windows.
  257. There are two options for the input filename:
  258. @example
  259. desktop
  260. @end example
  261. or
  262. @example
  263. title=@var{window_title}
  264. @end example
  265. The first option will capture the entire desktop, or a fixed region of the
  266. desktop. The second option will instead capture the contents of a single
  267. window, regardless of its position on the screen.
  268. For example, to grab the entire desktop using @command{ffmpeg}:
  269. @example
  270. ffmpeg -f gdigrab -framerate 6 -i desktop out.mpg
  271. @end example
  272. Grab a 640x480 region at position @code{10,20}:
  273. @example
  274. ffmpeg -f gdigrab -framerate 6 -offset_x 10 -offset_y 20 -video_size vga -i desktop out.mpg
  275. @end example
  276. Grab the contents of the window named "Calculator"
  277. @example
  278. ffmpeg -f gdigrab -framerate 6 -i title=Calculator out.mpg
  279. @end example
  280. @subsection Options
  281. @table @option
  282. @item draw_mouse
  283. Specify whether to draw the mouse pointer. Use the value @code{0} to
  284. not draw the pointer. Default value is @code{1}.
  285. @item framerate
  286. Set the grabbing frame rate. Default value is @code{ntsc},
  287. corresponding to a frame rate of @code{30000/1001}.
  288. @item show_region
  289. Show grabbed region on screen.
  290. If @var{show_region} is specified with @code{1}, then the grabbing
  291. region will be indicated on screen. With this option, it is easy to
  292. know what is being grabbed if only a portion of the screen is grabbed.
  293. Note that @var{show_region} is incompatible with grabbing the contents
  294. of a single window.
  295. For example:
  296. @example
  297. ffmpeg -f gdigrab -show_region 1 -framerate 6 -video_size cif -offset_x 10 -offset_y 20 -i desktop out.mpg
  298. @end example
  299. @item video_size
  300. Set the video frame size. The default is to capture the full screen if @file{desktop} is selected, or the full window size if @file{title=@var{window_title}} is selected.
  301. @item offset_x
  302. When capturing a region with @var{video_size}, set the distance from the left edge of the screen or desktop.
  303. Note that the offset calculation is from the top left corner of the primary monitor on Windows. If you have a monitor positioned to the left of your primary monitor, you will need to use a negative @var{offset_x} value to move the region to that monitor.
  304. @item offset_y
  305. When capturing a region with @var{video_size}, set the distance from the top edge of the screen or desktop.
  306. Note that the offset calculation is from the top left corner of the primary monitor on Windows. If you have a monitor positioned above your primary monitor, you will need to use a negative @var{offset_y} value to move the region to that monitor.
  307. @end table
  308. @section iec61883
  309. FireWire DV/HDV input device using libiec61883.
  310. To enable this input device, you need libiec61883, libraw1394 and
  311. libavc1394 installed on your system. Use the configure option
  312. @code{--enable-libiec61883} to compile with the device enabled.
  313. The iec61883 capture device supports capturing from a video device
  314. connected via IEEE1394 (FireWire), using libiec61883 and the new Linux
  315. FireWire stack (juju). This is the default DV/HDV input method in Linux
  316. Kernel 2.6.37 and later, since the old FireWire stack was removed.
  317. Specify the FireWire port to be used as input file, or "auto"
  318. to choose the first port connected.
  319. @subsection Options
  320. @table @option
  321. @item dvtype
  322. Override autodetection of DV/HDV. This should only be used if auto
  323. detection does not work, or if usage of a different device type
  324. should be prohibited. Treating a DV device as HDV (or vice versa) will
  325. not work and result in undefined behavior.
  326. The values @option{auto}, @option{dv} and @option{hdv} are supported.
  327. @item dvbuffer
  328. Set maximum size of buffer for incoming data, in frames. For DV, this
  329. is an exact value. For HDV, it is not frame exact, since HDV does
  330. not have a fixed frame size.
  331. @item dvguid
  332. Select the capture device by specifying it's GUID. Capturing will only
  333. be performed from the specified device and fails if no device with the
  334. given GUID is found. This is useful to select the input if multiple
  335. devices are connected at the same time.
  336. Look at /sys/bus/firewire/devices to find out the GUIDs.
  337. @end table
  338. @subsection Examples
  339. @itemize
  340. @item
  341. Grab and show the input of a FireWire DV/HDV device.
  342. @example
  343. ffplay -f iec61883 -i auto
  344. @end example
  345. @item
  346. Grab and record the input of a FireWire DV/HDV device,
  347. using a packet buffer of 100000 packets if the source is HDV.
  348. @example
  349. ffmpeg -f iec61883 -i auto -hdvbuffer 100000 out.mpg
  350. @end example
  351. @end itemize
  352. @section jack
  353. JACK input device.
  354. To enable this input device during configuration you need libjack
  355. installed on your system.
  356. A JACK input device creates one or more JACK writable clients, one for
  357. each audio channel, with name @var{client_name}:input_@var{N}, where
  358. @var{client_name} is the name provided by the application, and @var{N}
  359. is a number which identifies the channel.
  360. Each writable client will send the acquired data to the FFmpeg input
  361. device.
  362. Once you have created one or more JACK readable clients, you need to
  363. connect them to one or more JACK writable clients.
  364. To connect or disconnect JACK clients you can use the @command{jack_connect}
  365. and @command{jack_disconnect} programs, or do it through a graphical interface,
  366. for example with @command{qjackctl}.
  367. To list the JACK clients and their properties you can invoke the command
  368. @command{jack_lsp}.
  369. Follows an example which shows how to capture a JACK readable client
  370. with @command{ffmpeg}.
  371. @example
  372. # Create a JACK writable client with name "ffmpeg".
  373. $ ffmpeg -f jack -i ffmpeg -y out.wav
  374. # Start the sample jack_metro readable client.
  375. $ jack_metro -b 120 -d 0.2 -f 4000
  376. # List the current JACK clients.
  377. $ jack_lsp -c
  378. system:capture_1
  379. system:capture_2
  380. system:playback_1
  381. system:playback_2
  382. ffmpeg:input_1
  383. metro:120_bpm
  384. # Connect metro to the ffmpeg writable client.
  385. $ jack_connect metro:120_bpm ffmpeg:input_1
  386. @end example
  387. For more information read:
  388. @url{http://jackaudio.org/}
  389. @section lavfi
  390. Libavfilter input virtual device.
  391. This input device reads data from the open output pads of a libavfilter
  392. filtergraph.
  393. For each filtergraph open output, the input device will create a
  394. corresponding stream which is mapped to the generated output. Currently
  395. only video data is supported. The filtergraph is specified through the
  396. option @option{graph}.
  397. @subsection Options
  398. @table @option
  399. @item graph
  400. Specify the filtergraph to use as input. Each video open output must be
  401. labelled by a unique string of the form "out@var{N}", where @var{N} is a
  402. number starting from 0 corresponding to the mapped input stream
  403. generated by the device.
  404. The first unlabelled output is automatically assigned to the "out0"
  405. label, but all the others need to be specified explicitly.
  406. The suffix "+subcc" can be appended to the output label to create an extra
  407. stream with the closed captions packets attached to that output
  408. (experimental; only for EIA-608 / CEA-708 for now).
  409. The subcc streams are created after all the normal streams, in the order of
  410. the corresponding stream.
  411. For example, if there is "out19+subcc", "out7+subcc" and up to "out42", the
  412. stream #43 is subcc for stream #7 and stream #44 is subcc for stream #19.
  413. If not specified defaults to the filename specified for the input
  414. device.
  415. @item graph_file
  416. Set the filename of the filtergraph to be read and sent to the other
  417. filters. Syntax of the filtergraph is the same as the one specified by
  418. the option @var{graph}.
  419. @end table
  420. @subsection Examples
  421. @itemize
  422. @item
  423. Create a color video stream and play it back with @command{ffplay}:
  424. @example
  425. ffplay -f lavfi -graph "color=c=pink [out0]" dummy
  426. @end example
  427. @item
  428. As the previous example, but use filename for specifying the graph
  429. description, and omit the "out0" label:
  430. @example
  431. ffplay -f lavfi color=c=pink
  432. @end example
  433. @item
  434. Create three different video test filtered sources and play them:
  435. @example
  436. ffplay -f lavfi -graph "testsrc [out0]; testsrc,hflip [out1]; testsrc,negate [out2]" test3
  437. @end example
  438. @item
  439. Read an audio stream from a file using the amovie source and play it
  440. back with @command{ffplay}:
  441. @example
  442. ffplay -f lavfi "amovie=test.wav"
  443. @end example
  444. @item
  445. Read an audio stream and a video stream and play it back with
  446. @command{ffplay}:
  447. @example
  448. ffplay -f lavfi "movie=test.avi[out0];amovie=test.wav[out1]"
  449. @end example
  450. @item
  451. Dump decoded frames to images and closed captions to a file (experimental):
  452. @example
  453. ffmpeg -f lavfi -i "movie=test.ts[out0+subcc]" -map v frame%08d.png -map s -c copy -f rawvideo subcc.bin
  454. @end example
  455. @end itemize
  456. @section libcdio
  457. Audio-CD input device based on cdio.
  458. To enable this input device during configuration you need libcdio
  459. installed on your system. Requires the configure option
  460. @code{--enable-libcdio}.
  461. This device allows playing and grabbing from an Audio-CD.
  462. For example to copy with @command{ffmpeg} the entire Audio-CD in /dev/sr0,
  463. you may run the command:
  464. @example
  465. ffmpeg -f libcdio -i /dev/sr0 cd.wav
  466. @end example
  467. @section libdc1394
  468. IIDC1394 input device, based on libdc1394 and libraw1394.
  469. Requires the configure option @code{--enable-libdc1394}.
  470. @section openal
  471. The OpenAL input device provides audio capture on all systems with a
  472. working OpenAL 1.1 implementation.
  473. To enable this input device during configuration, you need OpenAL
  474. headers and libraries installed on your system, and need to configure
  475. FFmpeg with @code{--enable-openal}.
  476. OpenAL headers and libraries should be provided as part of your OpenAL
  477. implementation, or as an additional download (an SDK). Depending on your
  478. installation you may need to specify additional flags via the
  479. @code{--extra-cflags} and @code{--extra-ldflags} for allowing the build
  480. system to locate the OpenAL headers and libraries.
  481. An incomplete list of OpenAL implementations follows:
  482. @table @strong
  483. @item Creative
  484. The official Windows implementation, providing hardware acceleration
  485. with supported devices and software fallback.
  486. See @url{http://openal.org/}.
  487. @item OpenAL Soft
  488. Portable, open source (LGPL) software implementation. Includes
  489. backends for the most common sound APIs on the Windows, Linux,
  490. Solaris, and BSD operating systems.
  491. See @url{http://kcat.strangesoft.net/openal.html}.
  492. @item Apple
  493. OpenAL is part of Core Audio, the official Mac OS X Audio interface.
  494. See @url{http://developer.apple.com/technologies/mac/audio-and-video.html}
  495. @end table
  496. This device allows one to capture from an audio input device handled
  497. through OpenAL.
  498. You need to specify the name of the device to capture in the provided
  499. filename. If the empty string is provided, the device will
  500. automatically select the default device. You can get the list of the
  501. supported devices by using the option @var{list_devices}.
  502. @subsection Options
  503. @table @option
  504. @item channels
  505. Set the number of channels in the captured audio. Only the values
  506. @option{1} (monaural) and @option{2} (stereo) are currently supported.
  507. Defaults to @option{2}.
  508. @item sample_size
  509. Set the sample size (in bits) of the captured audio. Only the values
  510. @option{8} and @option{16} are currently supported. Defaults to
  511. @option{16}.
  512. @item sample_rate
  513. Set the sample rate (in Hz) of the captured audio.
  514. Defaults to @option{44.1k}.
  515. @item list_devices
  516. If set to @option{true}, print a list of devices and exit.
  517. Defaults to @option{false}.
  518. @end table
  519. @subsection Examples
  520. Print the list of OpenAL supported devices and exit:
  521. @example
  522. $ ffmpeg -list_devices true -f openal -i dummy out.ogg
  523. @end example
  524. Capture from the OpenAL device @file{DR-BT101 via PulseAudio}:
  525. @example
  526. $ ffmpeg -f openal -i 'DR-BT101 via PulseAudio' out.ogg
  527. @end example
  528. Capture from the default device (note the empty string '' as filename):
  529. @example
  530. $ ffmpeg -f openal -i '' out.ogg
  531. @end example
  532. Capture from two devices simultaneously, writing to two different files,
  533. within the same @command{ffmpeg} command:
  534. @example
  535. $ ffmpeg -f openal -i 'DR-BT101 via PulseAudio' out1.ogg -f openal -i 'ALSA Default' out2.ogg
  536. @end example
  537. Note: not all OpenAL implementations support multiple simultaneous capture -
  538. try the latest OpenAL Soft if the above does not work.
  539. @section oss
  540. Open Sound System input device.
  541. The filename to provide to the input device is the device node
  542. representing the OSS input device, and is usually set to
  543. @file{/dev/dsp}.
  544. For example to grab from @file{/dev/dsp} using @command{ffmpeg} use the
  545. command:
  546. @example
  547. ffmpeg -f oss -i /dev/dsp /tmp/oss.wav
  548. @end example
  549. For more information about OSS see:
  550. @url{http://manuals.opensound.com/usersguide/dsp.html}
  551. @section pulse
  552. PulseAudio input device.
  553. To enable this output device you need to configure FFmpeg with @code{--enable-libpulse}.
  554. The filename to provide to the input device is a source device or the
  555. string "default"
  556. To list the PulseAudio source devices and their properties you can invoke
  557. the command @command{pactl list sources}.
  558. More information about PulseAudio can be found on @url{http://www.pulseaudio.org}.
  559. @subsection Options
  560. @table @option
  561. @item server
  562. Connect to a specific PulseAudio server, specified by an IP address.
  563. Default server is used when not provided.
  564. @item name
  565. Specify the application name PulseAudio will use when showing active clients,
  566. by default it is the @code{LIBAVFORMAT_IDENT} string.
  567. @item stream_name
  568. Specify the stream name PulseAudio will use when showing active streams,
  569. by default it is "record".
  570. @item sample_rate
  571. Specify the samplerate in Hz, by default 48kHz is used.
  572. @item channels
  573. Specify the channels in use, by default 2 (stereo) is set.
  574. @item frame_size
  575. Specify the number of bytes per frame, by default it is set to 1024.
  576. @item fragment_size
  577. Specify the minimal buffering fragment in PulseAudio, it will affect the
  578. audio latency. By default it is unset.
  579. @end table
  580. @subsection Examples
  581. Record a stream from default device:
  582. @example
  583. ffmpeg -f pulse -i default /tmp/pulse.wav
  584. @end example
  585. @section qtkit
  586. QTKit input device.
  587. The filename passed as input is parsed to contain either a device name or index.
  588. The device index can also be given by using -video_device_index.
  589. A given device index will override any given device name.
  590. If the desired device consists of numbers only, use -video_device_index to identify it.
  591. The default device will be chosen if an empty string or the device name "default" is given.
  592. The available devices can be enumerated by using -list_devices.
  593. @example
  594. ffmpeg -f qtkit -i "0" out.mpg
  595. @end example
  596. @example
  597. ffmpeg -f qtkit -video_device_index 0 -i "" out.mpg
  598. @end example
  599. @example
  600. ffmpeg -f qtkit -i "default" out.mpg
  601. @end example
  602. @example
  603. ffmpeg -f qtkit -list_devices true -i ""
  604. @end example
  605. @section sndio
  606. sndio input device.
  607. To enable this input device during configuration you need libsndio
  608. installed on your system.
  609. The filename to provide to the input device is the device node
  610. representing the sndio input device, and is usually set to
  611. @file{/dev/audio0}.
  612. For example to grab from @file{/dev/audio0} using @command{ffmpeg} use the
  613. command:
  614. @example
  615. ffmpeg -f sndio -i /dev/audio0 /tmp/oss.wav
  616. @end example
  617. @section video4linux2, v4l2
  618. Video4Linux2 input video device.
  619. "v4l2" can be used as alias for "video4linux2".
  620. If FFmpeg is built with v4l-utils support (by using the
  621. @code{--enable-libv4l2} configure option), it is possible to use it with the
  622. @code{-use_libv4l2} input device option.
  623. The name of the device to grab is a file device node, usually Linux
  624. systems tend to automatically create such nodes when the device
  625. (e.g. an USB webcam) is plugged into the system, and has a name of the
  626. kind @file{/dev/video@var{N}}, where @var{N} is a number associated to
  627. the device.
  628. Video4Linux2 devices usually support a limited set of
  629. @var{width}x@var{height} sizes and frame rates. You can check which are
  630. supported using @command{-list_formats all} for Video4Linux2 devices.
  631. Some devices, like TV cards, support one or more standards. It is possible
  632. to list all the supported standards using @command{-list_standards all}.
  633. The time base for the timestamps is 1 microsecond. Depending on the kernel
  634. version and configuration, the timestamps may be derived from the real time
  635. clock (origin at the Unix Epoch) or the monotonic clock (origin usually at
  636. boot time, unaffected by NTP or manual changes to the clock). The
  637. @option{-timestamps abs} or @option{-ts abs} option can be used to force
  638. conversion into the real time clock.
  639. Some usage examples of the video4linux2 device with @command{ffmpeg}
  640. and @command{ffplay}:
  641. @itemize
  642. @item
  643. Grab and show the input of a video4linux2 device:
  644. @example
  645. ffplay -f video4linux2 -framerate 30 -video_size hd720 /dev/video0
  646. @end example
  647. @item
  648. Grab and record the input of a video4linux2 device, leave the
  649. frame rate and size as previously set:
  650. @example
  651. ffmpeg -f video4linux2 -input_format mjpeg -i /dev/video0 out.mpeg
  652. @end example
  653. @end itemize
  654. For more information about Video4Linux, check @url{http://linuxtv.org/}.
  655. @subsection Options
  656. @table @option
  657. @item standard
  658. Set the standard. Must be the name of a supported standard. To get a
  659. list of the supported standards, use the @option{list_standards}
  660. option.
  661. @item channel
  662. Set the input channel number. Default to -1, which means using the
  663. previously selected channel.
  664. @item video_size
  665. Set the video frame size. The argument must be a string in the form
  666. @var{WIDTH}x@var{HEIGHT} or a valid size abbreviation.
  667. @item pixel_format
  668. Select the pixel format (only valid for raw video input).
  669. @item input_format
  670. Set the preferred pixel format (for raw video) or a codec name.
  671. This option allows one to select the input format, when several are
  672. available.
  673. @item framerate
  674. Set the preferred video frame rate.
  675. @item list_formats
  676. List available formats (supported pixel formats, codecs, and frame
  677. sizes) and exit.
  678. Available values are:
  679. @table @samp
  680. @item all
  681. Show all available (compressed and non-compressed) formats.
  682. @item raw
  683. Show only raw video (non-compressed) formats.
  684. @item compressed
  685. Show only compressed formats.
  686. @end table
  687. @item list_standards
  688. List supported standards and exit.
  689. Available values are:
  690. @table @samp
  691. @item all
  692. Show all supported standards.
  693. @end table
  694. @item timestamps, ts
  695. Set type of timestamps for grabbed frames.
  696. Available values are:
  697. @table @samp
  698. @item default
  699. Use timestamps from the kernel.
  700. @item abs
  701. Use absolute timestamps (wall clock).
  702. @item mono2abs
  703. Force conversion from monotonic to absolute timestamps.
  704. @end table
  705. Default value is @code{default}.
  706. @end table
  707. @section vfwcap
  708. VfW (Video for Windows) capture input device.
  709. The filename passed as input is the capture driver number, ranging from
  710. 0 to 9. You may use "list" as filename to print a list of drivers. Any
  711. other filename will be interpreted as device number 0.
  712. @section x11grab
  713. X11 video input device.
  714. Depends on X11, Xext, and Xfixes. Requires the configure option
  715. @code{--enable-x11grab}.
  716. This device allows one to capture a region of an X11 display.
  717. The filename passed as input has the syntax:
  718. @example
  719. [@var{hostname}]:@var{display_number}.@var{screen_number}[+@var{x_offset},@var{y_offset}]
  720. @end example
  721. @var{hostname}:@var{display_number}.@var{screen_number} specifies the
  722. X11 display name of the screen to grab from. @var{hostname} can be
  723. omitted, and defaults to "localhost". The environment variable
  724. @env{DISPLAY} contains the default display name.
  725. @var{x_offset} and @var{y_offset} specify the offsets of the grabbed
  726. area with respect to the top-left border of the X11 screen. They
  727. default to 0.
  728. Check the X11 documentation (e.g. man X) for more detailed information.
  729. Use the @command{dpyinfo} program for getting basic information about the
  730. properties of your X11 display (e.g. grep for "name" or "dimensions").
  731. For example to grab from @file{:0.0} using @command{ffmpeg}:
  732. @example
  733. ffmpeg -f x11grab -framerate 25 -video_size cif -i :0.0 out.mpg
  734. @end example
  735. Grab at position @code{10,20}:
  736. @example
  737. ffmpeg -f x11grab -framerate 25 -video_size cif -i :0.0+10,20 out.mpg
  738. @end example
  739. @subsection Options
  740. @table @option
  741. @item draw_mouse
  742. Specify whether to draw the mouse pointer. A value of @code{0} specify
  743. not to draw the pointer. Default value is @code{1}.
  744. @item follow_mouse
  745. Make the grabbed area follow the mouse. The argument can be
  746. @code{centered} or a number of pixels @var{PIXELS}.
  747. When it is specified with "centered", the grabbing region follows the mouse
  748. pointer and keeps the pointer at the center of region; otherwise, the region
  749. follows only when the mouse pointer reaches within @var{PIXELS} (greater than
  750. zero) to the edge of region.
  751. For example:
  752. @example
  753. ffmpeg -f x11grab -follow_mouse centered -framerate 25 -video_size cif -i :0.0 out.mpg
  754. @end example
  755. To follow only when the mouse pointer reaches within 100 pixels to edge:
  756. @example
  757. ffmpeg -f x11grab -follow_mouse 100 -framerate 25 -video_size cif -i :0.0 out.mpg
  758. @end example
  759. @item framerate
  760. Set the grabbing frame rate. Default value is @code{ntsc},
  761. corresponding to a frame rate of @code{30000/1001}.
  762. @item show_region
  763. Show grabbed region on screen.
  764. If @var{show_region} is specified with @code{1}, then the grabbing
  765. region will be indicated on screen. With this option, it is easy to
  766. know what is being grabbed if only a portion of the screen is grabbed.
  767. For example:
  768. @example
  769. ffmpeg -f x11grab -show_region 1 -framerate 25 -video_size cif -i :0.0+10,20 out.mpg
  770. @end example
  771. With @var{follow_mouse}:
  772. @example
  773. ffmpeg -f x11grab -follow_mouse centered -show_region 1 -framerate 25 -video_size cif -i :0.0 out.mpg
  774. @end example
  775. @item video_size
  776. Set the video frame size. Default value is @code{vga}.
  777. @item use_shm
  778. Use the MIT-SHM extension for shared memory. Default value is @code{1}.
  779. It may be necessary to disable it for remote displays.
  780. @end table
  781. @section decklink
  782. The decklink input device provides capture capabilities for Blackmagic
  783. DeckLink devices.
  784. To enable this input device, you need the Blackmagic DeckLink SDK and you
  785. need to configure with the appropriate @code{--extra-cflags}
  786. and @code{--extra-ldflags}.
  787. On Windows, you need to run the IDL files through @command{widl}.
  788. DeckLink is very picky about the formats it supports. Pixel format is always
  789. uyvy422, framerate and video size must be determined for your device with
  790. @command{-list_formats 1}. Audio sample rate is always 48 kHz and the number
  791. of channels currently is limited to 2 (stereo).
  792. @subsection Options
  793. @table @option
  794. @item list_devices
  795. If set to @option{true}, print a list of devices and exit.
  796. Defaults to @option{false}.
  797. @item list_formats
  798. If set to @option{true}, print a list of supported formats and exit.
  799. Defaults to @option{false}.
  800. @end table
  801. @subsection Examples
  802. @itemize
  803. @item
  804. List input devices:
  805. @example
  806. ffmpeg -f decklink -list_devices 1 -i dummy
  807. @end example
  808. @item
  809. List supported formats:
  810. @example
  811. ffmpeg -f decklink -list_formats 1 -i 'Intensity Pro'
  812. @end example
  813. @item
  814. Capture video clip at 1080i50 (format 11):
  815. @example
  816. ffmpeg -f decklink -i 'Intensity Pro@@11' -acodec copy -vcodec copy output.avi
  817. @end example
  818. @end itemize
  819. @c man end INPUT DEVICES