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.

1074 lines
31KB

  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. @end table
  171. @subsection Examples
  172. @itemize
  173. @item
  174. Print the list of DirectShow supported devices and exit:
  175. @example
  176. $ ffmpeg -list_devices true -f dshow -i dummy
  177. @end example
  178. @item
  179. Open video device @var{Camera}:
  180. @example
  181. $ ffmpeg -f dshow -i video="Camera"
  182. @end example
  183. @item
  184. Open second video device with name @var{Camera}:
  185. @example
  186. $ ffmpeg -f dshow -video_device_number 1 -i video="Camera"
  187. @end example
  188. @item
  189. Open video device @var{Camera} and audio device @var{Microphone}:
  190. @example
  191. $ ffmpeg -f dshow -i video="Camera":audio="Microphone"
  192. @end example
  193. @item
  194. Print the list of supported options in selected device and exit:
  195. @example
  196. $ ffmpeg -list_options true -f dshow -i video="Camera"
  197. @end example
  198. @item
  199. Specify pin names to capture by name or alternative name, specify alternative device name:
  200. @example
  201. $ 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"
  202. @end example
  203. @end itemize
  204. @section dv1394
  205. Linux DV 1394 input device.
  206. @section fbdev
  207. Linux framebuffer input device.
  208. The Linux framebuffer is a graphic hardware-independent abstraction
  209. layer to show graphics on a computer monitor, typically on the
  210. console. It is accessed through a file device node, usually
  211. @file{/dev/fb0}.
  212. For more detailed information read the file
  213. Documentation/fb/framebuffer.txt included in the Linux source tree.
  214. To record from the framebuffer device @file{/dev/fb0} with
  215. @command{ffmpeg}:
  216. @example
  217. ffmpeg -f fbdev -r 10 -i /dev/fb0 out.avi
  218. @end example
  219. You can take a single screenshot image with the command:
  220. @example
  221. ffmpeg -f fbdev -frames:v 1 -r 1 -i /dev/fb0 screenshot.jpeg
  222. @end example
  223. See also @url{http://linux-fbdev.sourceforge.net/}, and fbset(1).
  224. @section gdigrab
  225. Win32 GDI-based screen capture device.
  226. This device allows you to capture a region of the display on Windows.
  227. There are two options for the input filename:
  228. @example
  229. desktop
  230. @end example
  231. or
  232. @example
  233. title=@var{window_title}
  234. @end example
  235. The first option will capture the entire desktop, or a fixed region of the
  236. desktop. The second option will instead capture the contents of a single
  237. window, regardless of its position on the screen.
  238. For example, to grab the entire desktop using @command{ffmpeg}:
  239. @example
  240. ffmpeg -f gdigrab -framerate 6 -i desktop out.mpg
  241. @end example
  242. Grab a 640x480 region at position @code{10,20}:
  243. @example
  244. ffmpeg -f gdigrab -framerate 6 -offset_x 10 -offset_y 20 -video_size vga -i desktop out.mpg
  245. @end example
  246. Grab the contents of the window named "Calculator"
  247. @example
  248. ffmpeg -f gdigrab -framerate 6 -i title=Calculator out.mpg
  249. @end example
  250. @subsection Options
  251. @table @option
  252. @item draw_mouse
  253. Specify whether to draw the mouse pointer. Use the value @code{0} to
  254. not draw the pointer. Default value is @code{1}.
  255. @item framerate
  256. Set the grabbing frame rate. Default value is @code{ntsc},
  257. corresponding to a frame rate of @code{30000/1001}.
  258. @item show_region
  259. Show grabbed region on screen.
  260. If @var{show_region} is specified with @code{1}, then the grabbing
  261. region will be indicated on screen. With this option, it is easy to
  262. know what is being grabbed if only a portion of the screen is grabbed.
  263. Note that @var{show_region} is incompatible with grabbing the contents
  264. of a single window.
  265. For example:
  266. @example
  267. ffmpeg -f gdigrab -show_region 1 -framerate 6 -video_size cif -offset_x 10 -offset_y 20 -i desktop out.mpg
  268. @end example
  269. @item video_size
  270. 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.
  271. @item offset_x
  272. When capturing a region with @var{video_size}, set the distance from the left edge of the screen or desktop.
  273. 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.
  274. @item offset_y
  275. When capturing a region with @var{video_size}, set the distance from the top edge of the screen or desktop.
  276. 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.
  277. @end table
  278. @section iec61883
  279. FireWire DV/HDV input device using libiec61883.
  280. To enable this input device, you need libiec61883, libraw1394 and
  281. libavc1394 installed on your system. Use the configure option
  282. @code{--enable-libiec61883} to compile with the device enabled.
  283. The iec61883 capture device supports capturing from a video device
  284. connected via IEEE1394 (FireWire), using libiec61883 and the new Linux
  285. FireWire stack (juju). This is the default DV/HDV input method in Linux
  286. Kernel 2.6.37 and later, since the old FireWire stack was removed.
  287. Specify the FireWire port to be used as input file, or "auto"
  288. to choose the first port connected.
  289. @subsection Options
  290. @table @option
  291. @item dvtype
  292. Override autodetection of DV/HDV. This should only be used if auto
  293. detection does not work, or if usage of a different device type
  294. should be prohibited. Treating a DV device as HDV (or vice versa) will
  295. not work and result in undefined behavior.
  296. The values @option{auto}, @option{dv} and @option{hdv} are supported.
  297. @item dvbuffer
  298. Set maximum size of buffer for incoming data, in frames. For DV, this
  299. is an exact value. For HDV, it is not frame exact, since HDV does
  300. not have a fixed frame size.
  301. @item dvguid
  302. Select the capture device by specifying it's GUID. Capturing will only
  303. be performed from the specified device and fails if no device with the
  304. given GUID is found. This is useful to select the input if multiple
  305. devices are connected at the same time.
  306. Look at /sys/bus/firewire/devices to find out the GUIDs.
  307. @end table
  308. @subsection Examples
  309. @itemize
  310. @item
  311. Grab and show the input of a FireWire DV/HDV device.
  312. @example
  313. ffplay -f iec61883 -i auto
  314. @end example
  315. @item
  316. Grab and record the input of a FireWire DV/HDV device,
  317. using a packet buffer of 100000 packets if the source is HDV.
  318. @example
  319. ffmpeg -f iec61883 -i auto -hdvbuffer 100000 out.mpg
  320. @end example
  321. @end itemize
  322. @section jack
  323. JACK input device.
  324. To enable this input device during configuration you need libjack
  325. installed on your system.
  326. A JACK input device creates one or more JACK writable clients, one for
  327. each audio channel, with name @var{client_name}:input_@var{N}, where
  328. @var{client_name} is the name provided by the application, and @var{N}
  329. is a number which identifies the channel.
  330. Each writable client will send the acquired data to the FFmpeg input
  331. device.
  332. Once you have created one or more JACK readable clients, you need to
  333. connect them to one or more JACK writable clients.
  334. To connect or disconnect JACK clients you can use the @command{jack_connect}
  335. and @command{jack_disconnect} programs, or do it through a graphical interface,
  336. for example with @command{qjackctl}.
  337. To list the JACK clients and their properties you can invoke the command
  338. @command{jack_lsp}.
  339. Follows an example which shows how to capture a JACK readable client
  340. with @command{ffmpeg}.
  341. @example
  342. # Create a JACK writable client with name "ffmpeg".
  343. $ ffmpeg -f jack -i ffmpeg -y out.wav
  344. # Start the sample jack_metro readable client.
  345. $ jack_metro -b 120 -d 0.2 -f 4000
  346. # List the current JACK clients.
  347. $ jack_lsp -c
  348. system:capture_1
  349. system:capture_2
  350. system:playback_1
  351. system:playback_2
  352. ffmpeg:input_1
  353. metro:120_bpm
  354. # Connect metro to the ffmpeg writable client.
  355. $ jack_connect metro:120_bpm ffmpeg:input_1
  356. @end example
  357. For more information read:
  358. @url{http://jackaudio.org/}
  359. @section lavfi
  360. Libavfilter input virtual device.
  361. This input device reads data from the open output pads of a libavfilter
  362. filtergraph.
  363. For each filtergraph open output, the input device will create a
  364. corresponding stream which is mapped to the generated output. Currently
  365. only video data is supported. The filtergraph is specified through the
  366. option @option{graph}.
  367. @subsection Options
  368. @table @option
  369. @item graph
  370. Specify the filtergraph to use as input. Each video open output must be
  371. labelled by a unique string of the form "out@var{N}", where @var{N} is a
  372. number starting from 0 corresponding to the mapped input stream
  373. generated by the device.
  374. The first unlabelled output is automatically assigned to the "out0"
  375. label, but all the others need to be specified explicitly.
  376. The suffix "+subcc" can be appended to the output label to create an extra
  377. stream with the closed captions packets attached to that output
  378. (experimental; only for EIA-608 / CEA-708 for now).
  379. The subcc streams are created after all the normal streams, in the order of
  380. the corresponding stream.
  381. For example, if there is "out19+subcc", "out7+subcc" and up to "out42", the
  382. stream #43 is subcc for stream #7 and stream #44 is subcc for stream #19.
  383. If not specified defaults to the filename specified for the input
  384. device.
  385. @item graph_file
  386. Set the filename of the filtergraph to be read and sent to the other
  387. filters. Syntax of the filtergraph is the same as the one specified by
  388. the option @var{graph}.
  389. @end table
  390. @subsection Examples
  391. @itemize
  392. @item
  393. Create a color video stream and play it back with @command{ffplay}:
  394. @example
  395. ffplay -f lavfi -graph "color=c=pink [out0]" dummy
  396. @end example
  397. @item
  398. As the previous example, but use filename for specifying the graph
  399. description, and omit the "out0" label:
  400. @example
  401. ffplay -f lavfi color=c=pink
  402. @end example
  403. @item
  404. Create three different video test filtered sources and play them:
  405. @example
  406. ffplay -f lavfi -graph "testsrc [out0]; testsrc,hflip [out1]; testsrc,negate [out2]" test3
  407. @end example
  408. @item
  409. Read an audio stream from a file using the amovie source and play it
  410. back with @command{ffplay}:
  411. @example
  412. ffplay -f lavfi "amovie=test.wav"
  413. @end example
  414. @item
  415. Read an audio stream and a video stream and play it back with
  416. @command{ffplay}:
  417. @example
  418. ffplay -f lavfi "movie=test.avi[out0];amovie=test.wav[out1]"
  419. @end example
  420. @item
  421. Dump decoded frames to images and closed captions to a file (experimental):
  422. @example
  423. ffmpeg -f lavfi -i "movie=test.ts[out0+subcc]" -map v frame%08d.png -map s -c copy -f rawvideo subcc.bin
  424. @end example
  425. @end itemize
  426. @section libcdio
  427. Audio-CD input device based on cdio.
  428. To enable this input device during configuration you need libcdio
  429. installed on your system. Requires the configure option
  430. @code{--enable-libcdio}.
  431. This device allows playing and grabbing from an Audio-CD.
  432. For example to copy with @command{ffmpeg} the entire Audio-CD in /dev/sr0,
  433. you may run the command:
  434. @example
  435. ffmpeg -f libcdio -i /dev/sr0 cd.wav
  436. @end example
  437. @section libdc1394
  438. IIDC1394 input device, based on libdc1394 and libraw1394.
  439. Requires the configure option @code{--enable-libdc1394}.
  440. @section openal
  441. The OpenAL input device provides audio capture on all systems with a
  442. working OpenAL 1.1 implementation.
  443. To enable this input device during configuration, you need OpenAL
  444. headers and libraries installed on your system, and need to configure
  445. FFmpeg with @code{--enable-openal}.
  446. OpenAL headers and libraries should be provided as part of your OpenAL
  447. implementation, or as an additional download (an SDK). Depending on your
  448. installation you may need to specify additional flags via the
  449. @code{--extra-cflags} and @code{--extra-ldflags} for allowing the build
  450. system to locate the OpenAL headers and libraries.
  451. An incomplete list of OpenAL implementations follows:
  452. @table @strong
  453. @item Creative
  454. The official Windows implementation, providing hardware acceleration
  455. with supported devices and software fallback.
  456. See @url{http://openal.org/}.
  457. @item OpenAL Soft
  458. Portable, open source (LGPL) software implementation. Includes
  459. backends for the most common sound APIs on the Windows, Linux,
  460. Solaris, and BSD operating systems.
  461. See @url{http://kcat.strangesoft.net/openal.html}.
  462. @item Apple
  463. OpenAL is part of Core Audio, the official Mac OS X Audio interface.
  464. See @url{http://developer.apple.com/technologies/mac/audio-and-video.html}
  465. @end table
  466. This device allows one to capture from an audio input device handled
  467. through OpenAL.
  468. You need to specify the name of the device to capture in the provided
  469. filename. If the empty string is provided, the device will
  470. automatically select the default device. You can get the list of the
  471. supported devices by using the option @var{list_devices}.
  472. @subsection Options
  473. @table @option
  474. @item channels
  475. Set the number of channels in the captured audio. Only the values
  476. @option{1} (monaural) and @option{2} (stereo) are currently supported.
  477. Defaults to @option{2}.
  478. @item sample_size
  479. Set the sample size (in bits) of the captured audio. Only the values
  480. @option{8} and @option{16} are currently supported. Defaults to
  481. @option{16}.
  482. @item sample_rate
  483. Set the sample rate (in Hz) of the captured audio.
  484. Defaults to @option{44.1k}.
  485. @item list_devices
  486. If set to @option{true}, print a list of devices and exit.
  487. Defaults to @option{false}.
  488. @end table
  489. @subsection Examples
  490. Print the list of OpenAL supported devices and exit:
  491. @example
  492. $ ffmpeg -list_devices true -f openal -i dummy out.ogg
  493. @end example
  494. Capture from the OpenAL device @file{DR-BT101 via PulseAudio}:
  495. @example
  496. $ ffmpeg -f openal -i 'DR-BT101 via PulseAudio' out.ogg
  497. @end example
  498. Capture from the default device (note the empty string '' as filename):
  499. @example
  500. $ ffmpeg -f openal -i '' out.ogg
  501. @end example
  502. Capture from two devices simultaneously, writing to two different files,
  503. within the same @command{ffmpeg} command:
  504. @example
  505. $ ffmpeg -f openal -i 'DR-BT101 via PulseAudio' out1.ogg -f openal -i 'ALSA Default' out2.ogg
  506. @end example
  507. Note: not all OpenAL implementations support multiple simultaneous capture -
  508. try the latest OpenAL Soft if the above does not work.
  509. @section oss
  510. Open Sound System input device.
  511. The filename to provide to the input device is the device node
  512. representing the OSS input device, and is usually set to
  513. @file{/dev/dsp}.
  514. For example to grab from @file{/dev/dsp} using @command{ffmpeg} use the
  515. command:
  516. @example
  517. ffmpeg -f oss -i /dev/dsp /tmp/oss.wav
  518. @end example
  519. For more information about OSS see:
  520. @url{http://manuals.opensound.com/usersguide/dsp.html}
  521. @section pulse
  522. PulseAudio input device.
  523. To enable this output device you need to configure FFmpeg with @code{--enable-libpulse}.
  524. The filename to provide to the input device is a source device or the
  525. string "default"
  526. To list the PulseAudio source devices and their properties you can invoke
  527. the command @command{pactl list sources}.
  528. More information about PulseAudio can be found on @url{http://www.pulseaudio.org}.
  529. @subsection Options
  530. @table @option
  531. @item server
  532. Connect to a specific PulseAudio server, specified by an IP address.
  533. Default server is used when not provided.
  534. @item name
  535. Specify the application name PulseAudio will use when showing active clients,
  536. by default it is the @code{LIBAVFORMAT_IDENT} string.
  537. @item stream_name
  538. Specify the stream name PulseAudio will use when showing active streams,
  539. by default it is "record".
  540. @item sample_rate
  541. Specify the samplerate in Hz, by default 48kHz is used.
  542. @item channels
  543. Specify the channels in use, by default 2 (stereo) is set.
  544. @item frame_size
  545. Specify the number of bytes per frame, by default it is set to 1024.
  546. @item fragment_size
  547. Specify the minimal buffering fragment in PulseAudio, it will affect the
  548. audio latency. By default it is unset.
  549. @end table
  550. @subsection Examples
  551. Record a stream from default device:
  552. @example
  553. ffmpeg -f pulse -i default /tmp/pulse.wav
  554. @end example
  555. @section qtkit
  556. QTKit input device.
  557. The filename passed as input is parsed to contain either a device name or index.
  558. The device index can also be given by using -video_device_index.
  559. A given device index will override any given device name.
  560. If the desired device consists of numbers only, use -video_device_index to identify it.
  561. The default device will be chosen if an empty string or the device name "default" is given.
  562. The available devices can be enumerated by using -list_devices.
  563. @example
  564. ffmpeg -f qtkit -i "0" out.mpg
  565. @end example
  566. @example
  567. ffmpeg -f qtkit -video_device_index 0 -i "" out.mpg
  568. @end example
  569. @example
  570. ffmpeg -f qtkit -i "default" out.mpg
  571. @end example
  572. @example
  573. ffmpeg -f qtkit -list_devices true -i ""
  574. @end example
  575. @section sndio
  576. sndio input device.
  577. To enable this input device during configuration you need libsndio
  578. installed on your system.
  579. The filename to provide to the input device is the device node
  580. representing the sndio input device, and is usually set to
  581. @file{/dev/audio0}.
  582. For example to grab from @file{/dev/audio0} using @command{ffmpeg} use the
  583. command:
  584. @example
  585. ffmpeg -f sndio -i /dev/audio0 /tmp/oss.wav
  586. @end example
  587. @section video4linux2, v4l2
  588. Video4Linux2 input video device.
  589. "v4l2" can be used as alias for "video4linux2".
  590. If FFmpeg is built with v4l-utils support (by using the
  591. @code{--enable-libv4l2} configure option), it is possible to use it with the
  592. @code{-use_libv4l2} input device option.
  593. The name of the device to grab is a file device node, usually Linux
  594. systems tend to automatically create such nodes when the device
  595. (e.g. an USB webcam) is plugged into the system, and has a name of the
  596. kind @file{/dev/video@var{N}}, where @var{N} is a number associated to
  597. the device.
  598. Video4Linux2 devices usually support a limited set of
  599. @var{width}x@var{height} sizes and frame rates. You can check which are
  600. supported using @command{-list_formats all} for Video4Linux2 devices.
  601. Some devices, like TV cards, support one or more standards. It is possible
  602. to list all the supported standards using @command{-list_standards all}.
  603. The time base for the timestamps is 1 microsecond. Depending on the kernel
  604. version and configuration, the timestamps may be derived from the real time
  605. clock (origin at the Unix Epoch) or the monotonic clock (origin usually at
  606. boot time, unaffected by NTP or manual changes to the clock). The
  607. @option{-timestamps abs} or @option{-ts abs} option can be used to force
  608. conversion into the real time clock.
  609. Some usage examples of the video4linux2 device with @command{ffmpeg}
  610. and @command{ffplay}:
  611. @itemize
  612. @item
  613. Grab and show the input of a video4linux2 device:
  614. @example
  615. ffplay -f video4linux2 -framerate 30 -video_size hd720 /dev/video0
  616. @end example
  617. @item
  618. Grab and record the input of a video4linux2 device, leave the
  619. frame rate and size as previously set:
  620. @example
  621. ffmpeg -f video4linux2 -input_format mjpeg -i /dev/video0 out.mpeg
  622. @end example
  623. @end itemize
  624. For more information about Video4Linux, check @url{http://linuxtv.org/}.
  625. @subsection Options
  626. @table @option
  627. @item standard
  628. Set the standard. Must be the name of a supported standard. To get a
  629. list of the supported standards, use the @option{list_standards}
  630. option.
  631. @item channel
  632. Set the input channel number. Default to -1, which means using the
  633. previously selected channel.
  634. @item video_size
  635. Set the video frame size. The argument must be a string in the form
  636. @var{WIDTH}x@var{HEIGHT} or a valid size abbreviation.
  637. @item pixel_format
  638. Select the pixel format (only valid for raw video input).
  639. @item input_format
  640. Set the preferred pixel format (for raw video) or a codec name.
  641. This option allows one to select the input format, when several are
  642. available.
  643. @item framerate
  644. Set the preferred video frame rate.
  645. @item list_formats
  646. List available formats (supported pixel formats, codecs, and frame
  647. sizes) and exit.
  648. Available values are:
  649. @table @samp
  650. @item all
  651. Show all available (compressed and non-compressed) formats.
  652. @item raw
  653. Show only raw video (non-compressed) formats.
  654. @item compressed
  655. Show only compressed formats.
  656. @end table
  657. @item list_standards
  658. List supported standards and exit.
  659. Available values are:
  660. @table @samp
  661. @item all
  662. Show all supported standards.
  663. @end table
  664. @item timestamps, ts
  665. Set type of timestamps for grabbed frames.
  666. Available values are:
  667. @table @samp
  668. @item default
  669. Use timestamps from the kernel.
  670. @item abs
  671. Use absolute timestamps (wall clock).
  672. @item mono2abs
  673. Force conversion from monotonic to absolute timestamps.
  674. @end table
  675. Default value is @code{default}.
  676. @end table
  677. @section vfwcap
  678. VfW (Video for Windows) capture input device.
  679. The filename passed as input is the capture driver number, ranging from
  680. 0 to 9. You may use "list" as filename to print a list of drivers. Any
  681. other filename will be interpreted as device number 0.
  682. @section x11grab
  683. X11 video input device.
  684. Depends on X11, Xext, and Xfixes. Requires the configure option
  685. @code{--enable-x11grab}.
  686. This device allows one to capture a region of an X11 display.
  687. The filename passed as input has the syntax:
  688. @example
  689. [@var{hostname}]:@var{display_number}.@var{screen_number}[+@var{x_offset},@var{y_offset}]
  690. @end example
  691. @var{hostname}:@var{display_number}.@var{screen_number} specifies the
  692. X11 display name of the screen to grab from. @var{hostname} can be
  693. omitted, and defaults to "localhost". The environment variable
  694. @env{DISPLAY} contains the default display name.
  695. @var{x_offset} and @var{y_offset} specify the offsets of the grabbed
  696. area with respect to the top-left border of the X11 screen. They
  697. default to 0.
  698. Check the X11 documentation (e.g. man X) for more detailed information.
  699. Use the @command{dpyinfo} program for getting basic information about the
  700. properties of your X11 display (e.g. grep for "name" or "dimensions").
  701. For example to grab from @file{:0.0} using @command{ffmpeg}:
  702. @example
  703. ffmpeg -f x11grab -framerate 25 -video_size cif -i :0.0 out.mpg
  704. @end example
  705. Grab at position @code{10,20}:
  706. @example
  707. ffmpeg -f x11grab -framerate 25 -video_size cif -i :0.0+10,20 out.mpg
  708. @end example
  709. @subsection Options
  710. @table @option
  711. @item draw_mouse
  712. Specify whether to draw the mouse pointer. A value of @code{0} specify
  713. not to draw the pointer. Default value is @code{1}.
  714. @item follow_mouse
  715. Make the grabbed area follow the mouse. The argument can be
  716. @code{centered} or a number of pixels @var{PIXELS}.
  717. When it is specified with "centered", the grabbing region follows the mouse
  718. pointer and keeps the pointer at the center of region; otherwise, the region
  719. follows only when the mouse pointer reaches within @var{PIXELS} (greater than
  720. zero) to the edge of region.
  721. For example:
  722. @example
  723. ffmpeg -f x11grab -follow_mouse centered -framerate 25 -video_size cif -i :0.0 out.mpg
  724. @end example
  725. To follow only when the mouse pointer reaches within 100 pixels to edge:
  726. @example
  727. ffmpeg -f x11grab -follow_mouse 100 -framerate 25 -video_size cif -i :0.0 out.mpg
  728. @end example
  729. @item framerate
  730. Set the grabbing frame rate. Default value is @code{ntsc},
  731. corresponding to a frame rate of @code{30000/1001}.
  732. @item show_region
  733. Show grabbed region on screen.
  734. If @var{show_region} is specified with @code{1}, then the grabbing
  735. region will be indicated on screen. With this option, it is easy to
  736. know what is being grabbed if only a portion of the screen is grabbed.
  737. For example:
  738. @example
  739. ffmpeg -f x11grab -show_region 1 -framerate 25 -video_size cif -i :0.0+10,20 out.mpg
  740. @end example
  741. With @var{follow_mouse}:
  742. @example
  743. ffmpeg -f x11grab -follow_mouse centered -show_region 1 -framerate 25 -video_size cif -i :0.0 out.mpg
  744. @end example
  745. @item video_size
  746. Set the video frame size. Default value is @code{vga}.
  747. @item use_shm
  748. Use the MIT-SHM extension for shared memory. Default value is @code{1}.
  749. It may be necessary to disable it for remote displays.
  750. @end table
  751. @section decklink
  752. The decklink input device provides capture capabilities for Blackmagic
  753. DeckLink devices.
  754. To enable this input device, you need the Blackmagic DeckLink SDK and you
  755. need to configure with the appropriate @code{--extra-cflags}
  756. and @code{--extra-ldflags}.
  757. On Windows, you need to run the IDL files through @command{widl}.
  758. DeckLink is very picky about the formats it supports. Pixel format is always
  759. uyvy422, framerate and video size must be determined for your device with
  760. @command{-list_formats 1}. Audio sample rate is always 48 kHz and the number
  761. of channels currently is limited to 2 (stereo).
  762. @subsection Options
  763. @table @option
  764. @item list_devices
  765. If set to @option{true}, print a list of devices and exit.
  766. Defaults to @option{false}.
  767. @item list_formats
  768. If set to @option{true}, print a list of supported formats and exit.
  769. Defaults to @option{false}.
  770. @end table
  771. @subsection Examples
  772. @itemize
  773. @item
  774. List input devices:
  775. @example
  776. ffmpeg -f decklink -list_devices 1 -i dummy
  777. @end example
  778. @item
  779. List supported formats:
  780. @example
  781. ffmpeg -f decklink -list_formats 1 -i 'Intensity Pro'
  782. @end example
  783. @item
  784. Capture video clip at 1080i50 (format 11):
  785. @example
  786. ffmpeg -f decklink -i 'Intensity Pro@@11' -acodec copy -vcodec copy output.avi
  787. @end example
  788. @end itemize
  789. @c man end INPUT DEVICES