ffmpeg-devices - FFmpeg devices
| Use Case | Command | Description |
|---|---|---|
| 🎥 Capture from ALSA audio device | ffmpeg -f alsa -i hw:0 output.wav | Record audio from ALSA card 0 |
| 📷 List input devices (decklink) | ffmpeg -sources decklink | Show available DeckLink input devices |
| 🖥️ Capture X11 screen region | ffmpeg -f x11grab -framerate 25 -video_size cif -i :0.0 out.mpg | Grab X11 display area |
| 🎬 Record from DirectShow (Windows) | ffmpeg -f dshow -i video="Camera":audio="Microphone" out.avi | Capture video and audio from named devices |
| 🔊 Play audio to ALSA output | ffmpeg -i INPUT -f alsa default | Play audio on default ALSA device |
| 🖼️ Show video in SDL window | ffmpeg -i INPUT -f sdl "SDL output" | Display video in an SDL window |
This document describes the input and output devices provided by the libavdevice library.
The libavdevice library provides the same interface as libavformat. Namely, an input device is considered like a demuxer, and an output device like a muxer, and the interface and generic device options are the same provided by libavformat (see the ffmpeg-formats manual).
In addition each input or output device may support so-called private options, which are specific for that component.
Options may be set by specifying -option value in the FFmpeg tools, or by setting the value explicitly in the device "AVFormatContext" options or using the libavutil/opt.h API for programmatic use.
Input devices are configured elements in FFmpeg which enable accessing the data coming from a multimedia device attached to your system.
When you configure your FFmpeg build, all the supported input devices are enabled by default. You can list all available ones using the configure option "--list-indevs".
You can disable all the input devices using the configure option "--disable-indevs", and selectively enable an input device using the option "--enable-indev=INDEV", or you can disable a particular input device using the option "--disable-indev=INDEV".
The option "-devices" of the ff* tools will display the list of supported input devices.
ALSA (Advanced Linux Sound Architecture) input device.
To enable this input device during configuration you need libasound installed on your system.
This device allows capturing from an ALSA device. The name of the device to capture has to be an ALSA card identifier.
An ALSA identifier has the syntax:
hw:<CARD>[,<DEV>[,<SUBDEV>]]
where the DEV and SUBDEV components are optional.
The three arguments (in order: CARD,DEV,SUBDEV) specify card number or identifier, device number and subdevice number (-1 means any).
To see the list of cards currently recognized by your system check the files /proc/asound/cards and /proc/asound/devices.
For example to capture with ffmpeg from an ALSA device with card id 0, you may run the command:
ffmpeg -f alsa -i hw:0 alsaout.wav
For more information see: http://www.alsa-project.org/alsa-doc/alsa-lib/pcm.html
Android camera input device.
This input devices uses the Android Camera2 NDK API which is available on devices with API level 24+. The availability of android_camera is autodetected during configuration.
This device allows capturing from all cameras on an Android device, which are integrated into the Camera2 NDK API.
The available cameras are enumerated internally and can be selected with the camera_index parameter. The input file string is discarded.
Generally the back facing camera has index 0 while the front facing camera has index 1.
AVFoundation input device.
AVFoundation is the currently recommended framework by Apple for streamgrabbing on OSX >= 10.7 as well as on iOS.
The input filename has to be given in the following syntax:
-i "[[VIDEO]:[AUDIO]]"
The first entry selects the video input while the latter selects the audio input. The stream has to be specified by the device name or the device index as shown by the device list. Alternatively, the video and/or audio input device can be chosen by index using the
-video_device_index <INDEX>
and/or
-audio_device_index <INDEX>
overriding any device name or index given in the input filename.
All available devices can be enumerated by using -list_devices true, listing all device names and corresponding indices.
There are two device name aliases:
$ ffmpeg -f avfoundation -list_devices true -i ""
$ ffmpeg -f avfoundation -i "0:0" out.avi
$ ffmpeg -f avfoundation -video_device_index 2 -i ":1" out.avi
$ ffmpeg -f avfoundation -pixel_format bgr0 -i "default:none" out.avi
$ ffmpeg -f avfoundation -capture_raw_data true -i "zr100:none" out.dv
BSD video input device.
The decklink input device provides capture capabilities for Blackmagic DeckLink devices.
To enable this input device, you need the Blackmagic DeckLink SDK and you need to configure with the appropriate "--extra-cflags" and "--extra-ldflags". On Windows, you need to run the IDL files through widl.
DeckLink is very picky about the formats it supports. Pixel format of the input can be set with raw_format. Framerate and video size must be determined for your device with -list_formats 1. Audio sample rate is always 48 kHz and the number of channels can be 2, 8 or 16. Note that all audio channels are bundled in one single audio track.
ffmpeg -sources decklink
ffmpeg -f decklink -list_formats 1 -i 'Intensity Pro'
ffmpeg -format_code Hi50 -f decklink -i 'Intensity Pro' -c:a copy -c:v copy output.avi
ffmpeg -raw_format yuv422p10 -format_code Hi50 -f decklink -i 'UltraStudio Mini Recorder' -c:a copy -c:v copy output.avi
ffmpeg -channels 16 -format_code Hi50 -f decklink -i 'UltraStudio Mini Recorder' -c:a copy -c:v copy output.avi
Windows DirectShow input device.
DirectShow support is enabled when FFmpeg is built with the mingw-w64 project. Currently only audio and video devices are supported.
Multiple devices may be opened as separate inputs, but they may also be opened on the same input, which should improve synchronism between them.
The input name should be in the format:
<TYPE>=<NAME>[:<TYPE>=<NAME>]
where TYPE can be either audio or video, and NAME is the device's name or alternative name.
$ ffmpeg -list_devices true -f dshow -i dummy
$ ffmpeg -f dshow -i video="Camera"
$ ffmpeg -f dshow -video_device_number 1 -i video="Camera"
$ ffmpeg -f dshow -i video="Camera":audio="Microphone"
$ ffmpeg -list_options true -f dshow -i video="Camera"
$ 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"
$ ffmpeg -f dshow -show_video_device_dialog true -crossbar_video_input_pin_number 0 -crossbar_audio_input_pin_number 3 -i video="AVerMedia BDA Analog Capture":audio="AVerMedia BDA Analog Capture"
Linux framebuffer input device.
The Linux framebuffer is a graphic hardware-independent abstraction layer to show graphics on a computer monitor, typically on the console. It is accessed through a file device node, usually /dev/fb0.
For more detailed information read the file Documentation/fb/framebuffer.txt included in the Linux source tree.
See also http://linux-fbdev.sourceforge.net/, and fbset(1).
To record from the framebuffer device /dev/fb0 with ffmpeg:
ffmpeg -f fbdev -framerate 10 -i /dev/fb0 out.avi
You can take a single screenshot image with the command:
ffmpeg -f fbdev -framerate 1 -i /dev/fb0 -frames:v 1 screenshot.jpeg
Win32 GDI-based screen capture device.
This device allows you to capture a region of the display on Windows.
There are two options for the input filename:
desktop
or
title=<window_title>
The first option will capture the entire desktop, or a fixed region of the desktop. The second option will instead capture the contents of a single window, regardless of its position on the screen.
For example, to grab the entire desktop using ffmpeg:
ffmpeg -f gdigrab -framerate 6 -i desktop out.mpg
Grab a 640x480 region at position "10,20":
ffmpeg -f gdigrab -framerate 6 -offset_x 10 -offset_y 20 -video_size vga -i desktop out.mpg
Grab the contents of the window named "Calculator"
ffmpeg -f gdigrab -framerate 6 -i title=Calculator out.mpg
FireWire DV/HDV input device using libiec61883.
To enable this input device, you need libiec61883, libraw1394 and libavc1394 installed on your system. Use the configure option "--enable-libiec61883" to compile with the device enabled.
The iec61883 capture device supports capturing from a video device connected via IEEE1394 (FireWire), using libiec61883 and the new Linux FireWire stack (juju). This is the default DV/HDV input method in Linux Kernel 2.6.37 and later, since the old FireWire stack was removed.
Specify the FireWire port to be used as input file, or "auto" to choose the first port connected.
ffplay -f iec61883 -i auto
ffmpeg -f iec61883 -i auto -dvbuffer 100000 out.mpg
JACK input device.
To enable this input device during configuration you need libjack installed on your system.
A JACK input device creates one or more JACK writable clients, one for each audio channel, with name client_name:input_N, where client_name is the name provided by the application, and N is a number which identifies the channel. Each writable client will send the acquired data to the FFmpeg input device.
Once you have created one or more JACK readable clients, you need to connect them to one or more JACK writable clients.
To connect or disconnect JACK clients you can use the jack_connect and jack_disconnect programs, or do it through a graphical interface, for example with qjackctl.
To list the JACK clients and their properties you can invoke the command jack_lsp.
Follows an example which shows how to capture a JACK readable client with ffmpeg.
# Create a JACK writable client with name "ffmpeg".
$ ffmpeg -f jack -i ffmpeg -y out.wav
# Start the sample jack_metro readable client.
$ jack_metro -b 120 -d 0.2 -f 4000
# List the current JACK clients.
$ jack_lsp -c
system:capture_1
system:capture_2
system:playback_1
system:playback_2
ffmpeg:input_1
metro:120_bpm
# Connect metro to the ffmpeg writable client.
$ jack_connect metro:120_bpm ffmpeg:input_1
For more information read: http://jackaudio.org/
KMS video input device.
Captures the KMS scanout framebuffer associated with a specified CRTC or plane as a DRM object that can be passed to other hardware functions.
Requires either DRM master or CAP_SYS_ADMIN to run.
If you don't understand what all of that means, you probably don't want this. Look at x11grab instead.
ffmpeg -f kmsgrab -i - -vf 'hwdownload,format=bgr0' output.mp4
ffmpeg -crtc_id 42 -framerate 60 -f kmsgrab -i - -vf 'hwmap=derive_device=vaapi,scale_vaapi=w=1920:h=1080:format=nv12' -c:v h264_vaapi output.mp4
ffmpeg -f kmsgrab -i - -vf 'hwmap=derive_device=vaapi,crop=960:540:480:270,scale_vaapi=960:540:nv12' -c:v h264_vaapi output.mp4
Libavfilter input virtual device.
This input device reads data from the open output pads of a libavfilter filtergraph.
For each filtergraph open output, the input device will create a corresponding stream which is mapped to the generated output. Currently only video data is supported. The filtergraph is specified through the option graph.
ffplay -f lavfi -graph "color=c=pink [out0]" dummy
ffplay -f lavfi color=c=pink
ffplay -f lavfi -graph "testsrc [out0]; testsrc,hflip [out1]; testsrc,negate [out2]" test3
ffplay -f lavfi "amovie=test.wav"
ffplay -f lavfi "movie=test.avi[out0];amovie=test.wav[out1]"
ffmpeg -f lavfi -i "movie=test.ts[out0+subcc]" -map v frame%08d.png -map s -c copy -f rawvideo subcc.bin
Audio-CD input device based on libcdio.
To enable this input device during configuration you need libcdio installed on your system. It requires the configure option "--enable-libcdio".
This device allows playing and grabbing from an Audio-CD.
For example to copy with ffmpeg the entire Audio-CD in /dev/sr0, you may run the command:
ffmpeg -f libcdio -i /dev/sr0 cd.wav
IIDC1394 input device, based on libdc1394 and libraw1394.
Requires the configure option "--enable-libdc1394".
The OpenAL input device provides audio capture on all systems with a working OpenAL 1.1 implementation.
To enable this input device during configuration, you need OpenAL headers and libraries installed on your system, and need to configure FFmpeg with "--enable-openal".
OpenAL headers and libraries should be provided as part of your OpenAL implementation, or as an additional download (an SDK). Depending on your installation you may need to specify additional flags via the "--extra-cflags" and "--extra-ldflags" for allowing the build system to locate the OpenAL headers and libraries.
An incomplete list of OpenAL implementations follows:
This device allows one to capture from an audio input device handled through OpenAL.
You need to specify the name of the device to capture in the provided filename. If the empty string is provided, the device will automatically select the default device. You can get the list of the supported devices by using the option list_devices.
$ ffmpeg -list_devices true -f openal -i dummy out.ogg
$ ffmpeg -f openal -i 'DR-BT101 via PulseAudio' out.ogg
$ ffmpeg -f openal -i '' out.ogg
$ ffmpeg -f openal -i 'DR-BT101 via PulseAudio' out1.ogg -f openal -i 'ALSA Default' out2.ogg
Open Sound System input device.
The filename to provide to the input device is the device node representing the OSS input device, and is usually set to /dev/dsp.
For example to grab from /dev/dsp using ffmpeg use the command:
ffmpeg -f oss -i /dev/dsp /tmp/oss.wav
For more information about OSS see: http://manuals.opensound.com/usersguide/dsp.html
PulseAudio input device.
To enable this output device you need to configure FFmpeg with "--enable-libpulse".
The filename to provide to the input device is a source device or the string "default"
To list the PulseAudio source devices and their properties you can invoke the command pactl list sources.
More information about PulseAudio can be found on http://www.pulseaudio.org.
ffmpeg -f pulse -i default /tmp/pulse.wav
sndio input device.
To enable this input device during configuration you need libsndio installed on your system.
The filename to provide to the input device is the device node representing the sndio input device, and is usually set to /dev/audio0.
For example to grab from /dev/audio0 using ffmpeg use the command:
ffmpeg -f sndio -i /dev/audio0 /tmp/oss.wav
Video4Linux2 input video device.
"v4l2" can be used as alias for "video4linux2".
If FFmpeg is built with v4l-utils support (by using the "--enable-libv4l2" configure option), it is possible to use it with the "-use_libv4l2" input device option.
The name of the device to grab is a file device node, usually Linux systems tend to automatically create such nodes when the device (e.g. an USB webcam) is plugged into the system, and has a name of the kind /dev/videoN, where N is a number associated to the device.
Video4Linux2 devices usually support a limited set of widthxheight sizes and frame rates. You can check which are supported using -list_formats all for Video4Linux2 devices. Some devices, like TV cards, support one or more standards. It is possible to list all the supported standards using -list_standards all.
The time base for the timestamps is 1 microsecond. Depending on the kernel version and configuration, the timestamps may be derived from the real time clock (origin at the Unix Epoch) or the monotonic clock (origin usually at boot time, unaffected by NTP or manual changes to the clock). The -timestamps abs or -ts abs option can be used to force conversion into the real time clock.
Some usage examples of the video4linux2 device with ffmpeg and ffplay:
ffplay -f video4linux2 -list_formats all /dev/video0
ffplay -f video4linux2 -framerate 30 -video_size hd720 /dev/video0
ffmpeg -f video4linux2 -input_format mjpeg -i /dev/video0 out.mpeg
For more information about Video4Linux, check http://linuxtv.org/.
VfW (Video for Windows) capture input device.
The filename passed as input is the capture driver number, ranging from 0 to 9. You may use "list" as filename to print a list of drivers. Any other filename will be interpreted as device number 0.
X11 video input device.
To enable this input device during configuration you need libxcb installed on your system. It will be automatically detected during configuration.
This device allows one to capture a region of an X11 display.
The filename passed as input has the syntax:
[<hostname>]:<display_number>.<screen_number>[+<x_offset>,<y_offset>]
hostname:display_number.screen_number specifies the X11 display name of the screen to grab from. hostname can be omitted, and defaults to "localhost". The environment variable DISPLAY contains the default display name.
x_offset and y_offset specify the offsets of the grabbed area with respect to the top-left border of the X11 screen. They default to 0.
Check the X11 documentation (e.g. man X) for more detailed information.
Use the xdpyinfo program for getting basic information about the properties of your X11 display (e.g. grep for "name" or "dimensions").
For example to grab from :0.0 using ffmpeg:
ffmpeg -f x11grab -framerate 25 -video_size cif -i :0.0 out.mpg
Grab at position "10,20":
ffmpeg -f x11grab -framerate 25 -video_size cif -i :0.0+10,20 out.mpg
Output devices are configured elements in FFmpeg that can write multimedia data to an output device attached to your system.
When you configure your FFmpeg build, all the supported output devices are enabled by default. You can list all available ones using the configure option "--list-outdevs".
You can disable all the output devices using the configure option "--disable-outdevs", and selectively enable an output device using the option "--enable-outdev=OUTDEV", or you can disable a particular input device using the option "--disable-outdev=OUTDEV".
The option "-devices" of the ff* tools will display the list of enabled output devices.
ALSA (Advanced Linux Sound Architecture) output device.
ffmpeg -i INPUT -f alsa default
ffmpeg -i INPUT -f alsa hw:1,7
AudioToolbox output device.
Allows native output to CoreAudio devices on OSX.
The output filename can be empty (or "-") to refer to the default system output device or a number that refers to the device index as shown using: "-list_devices true".
Alternatively, the audio input device can be chosen by index using the
-audio_device_index <INDEX>
overriding any device name or index given in the input filename.
All available devices can be enumerated by using -list_devices true, listing all device names, UIDs and corresponding indices.
$ ffmpeg -f lavfi -i sine=r=44100 -f audiotoolbox -list_devices true -
$ ffmpeg -f lavfi -i sine=r=44100 -f audiotoolbox -audio_device_index 2 -
CACA output device.
This output device allows one to show a video stream in CACA window. Only one CACA window is allowed per application, so you can have only one instance of this output device in an application.
To enable this output device you need to configure FFmpeg with "--enable-libcaca". libcaca is a graphics library that outputs text instead of pixels.
For more information about libcaca, check: http://caca.zoy.org/wiki/libcaca
ffmpeg -i INPUT -c:v rawvideo -pix_fmt rgb24 -window_size 80x25 -f caca -
ffmpeg -i INPUT -pix_fmt rgb24 -f caca -list_drivers true -
ffmpeg -i INPUT -pix_fmt rgb24 -f caca -list_dither colors -
The decklink output device provides playback capabilities for Blackmagic DeckLink devices.
To enable this output device, you need the Blackmagic DeckLink SDK and you need to configure with the appropriate "--extra-cflags" and "--extra-ldflags". On Windows, you need to run the IDL files through widl.
DeckLink is very picky about the formats it supports. Pixel format is always uyvy422, framerate, field order and video size must be determined for your device with -list_formats 1. Audio sample rate is always 48 kHz.
ffmpeg -sinks decklink
ffmpeg -i test.avi -f decklink -list_formats 1 'DeckLink Mini Monitor'
ffmpeg -i test.avi -f decklink -pix_fmt uyvy422 'DeckLink Mini Monitor'
ffmpeg -i test.avi -f decklink -pix_fmt uyvy422 -s 720x486 -r 24000/1001 'DeckLink Mini Monitor'
Linux framebuffer output device.
The Linux framebuffer is a graphic hardware-independent abstraction layer to show graphics on a computer monitor, typically on the console. It is accessed through a file device node, usually /dev/fb0.
For more detailed information read the file Documentation/fb/framebuffer.txt included in the Linux source tree.
ffmpeg -re -i INPUT -c:v rawvideo -pix_fmt bgra -f fbdev /dev/fb0
See also http://linux-fbdev.sourceforge.net/, and fbset(1).
OpenGL output device.
To enable this output device you need to configure FFmpeg with "--enable-opengl".
This output device allows one to render to OpenGL context. Context may be provided by application or default SDL window is created.
When device renders to external context, application must implement handlers for following messages: "AV_DEV_TO_APP_CREATE_WINDOW_BUFFER", "AV_DEV_TO_APP_PREPARE_WINDOW_BUFFER", "AV_DEV_TO_APP_DISPLAY_WINDOW_BUFFER", "AV_DEV_TO_APP_DESTROY_WINDOW_BUFFER". Application is also required to inform a device about current resolution by sending "AV_APP_TO_DEV_WINDOW_SIZE" message.
ffmpeg -i INPUT -f opengl "window title"
OSS (Open Sound System) output device.
(No additional options listed in the original.)
PulseAudio output device.
To enable this output device you need to configure FFmpeg with "--enable-libpulse".
More information about PulseAudio can be found on http://www.pulseaudio.org
ffmpeg -i INPUT -f pulse "stream name"
SDL (Simple DirectMedia Layer) output device.
"sdl2" can be used as alias for "sdl".
This output device allows one to show a video stream in an SDL window. Only one SDL window is allowed per application, so you can have only one instance of this output device in an application.
To enable this output device you need libsdl installed on your system when configuring your build.
For more information about SDL, check: http://www.libsdl.org/
ffmpeg -i INPUT -c:v rawvideo -pix_fmt yuv420p -window_size qcif -f sdl "SDL output"
sndio audio output device.
(No additional options listed in the original.)
Video4Linux2 output device.
(No additional options listed in the original.)
XV (XVideo) output device.
This output device allows one to show a video stream in a X Window System window.
ffmpeg -i INPUT OUTPUT -f xv display
ffmpeg -i INPUT -f xv normal -vf negate -f xv negated
ffmpeg(1), ffplay(1), ffprobe(1), libavdevice(3)
The FFmpeg developers.
For details about the authorship, see the Git history of the project (git://source.ffmpeg.org/ffmpeg), e.g. by typing the command git log in the FFmpeg source directory, or browsing the online repository at http://source.ffmpeg.org.
Maintainers for the specific components are listed in the file MAINTAINERS in the source code tree.
Generated by phpman v4.10.0-7-g98e9fd5 · Markdown · JSON · MCP Author: Che Dong Under GNU General Public License
2026-09-04 14:42 @216.73.216.128
CrawledBy Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)