Editer le fichier de configuration:
/etc/samba/smb.conf
exemple pour le répertoire in_imx50:
[in_imx50]
path = /var/www/html/wp-content/transcode/imx/in_imx50
writeable = yes
; browseable = yes
valid users = jpde, rtbf
Attention les passwords de samba pour les utilisateurs sont à introduire via:
smbpasswd -a <username>
Démarrage du service via:
service smb start
The command line entries are really simple.
To save a partition:
fsarchiver savefs /mnt/backup/gentoo-rootfs.fsa /dev/sda1 Where ‘/mnt/backup/gentoo-rootfs.fsa’ is the path being saved to and ‘/dev/sda1’ is the partition being cloned.
To restore a partition:
fsarchiver restfs /mnt/backup/gentoo-rootfs.fsa id=0,dest=/dev/sda1 Just reverse the options above. From what I understand (in the documentation), it looks like the id=0 is necessary because an image can contain multiple partitions. For more directions on usage (such as saving multiple partitions) checkout the QuickStart guide.
Pour backuper:
cd /
tar cvpzf backup.tgz –exclude=/proc –exclude=/lost+found –exclude=/backup.tgz –exclude=/mnt –exclude=/sys –exclude=/media –exclude=/home /
Pour restorer:
tar xvpfz backup.tgz -C /
Instruction de base:
ffmpeg -i in.mp4 -vf « drawtext=fontfile=/usr/share/fonts/truetype/DroidSans.ttf: timecode=’09\:57\:00\:00′: r=25: \
x=(w-tw)/2: y=h-(2*lh): fontcolor=white: box=1: boxcolor=0x00000000@1 » -an -y out.mp4
drawtext n’est pas reconnu si ffmbc n’est pas compilé avec:
–enable-libfreetype –enable-filter=drawtext
Attention pour ubuntu 12.04, télécharger libfreetype6-dev sinon error could find libfreetype2
Le fichiers mp4 transcodés par ffmbc ne sont pas optimisés pour le streaming. Il faut attendre la fin du fichier pour avoir accès aux metadatas.
mp4creator permet de les placer au début et il n’est plus nécessaire d’attendre que le fichier soit downloadé avant de le lire.
Ligne de commande:
mp4creator -optimize « fichier »
Pour que la commande soit opérationnelle, il faut avoir à bord mpeg4ip-server qu’il suffit d’installer avec synaptic.
/opt/lampp/lampp security
Pour lancer xampp au démarrage:
- créer un fichier xampp_start.sh à placer dans /etc/init.d/
- insérer la ligne suivante: /opt/lampp/lampp start
- sauver
- chmod 755 xampp_start.sh
- update-rc.d xampp_start.sh defaults
Installer wordpress, blog qui servira d'interface web pour le transcodage
-créer la base de données wordpress dans mysql
-Télécharger wordpress: http://wordpress.org/download/
-Décompresser et copier coller le contenu dans le répertoire /opt/lampp/htdocs
-Installer le blog par localhost
-Installer les plugins: inline-javascript, inline-upload, list-yo-files et search-everything
-Installer le thême suffusion
./configure –prefix=/opt/ffmbc –enable-gpl –enable-nonfree –enable-shared –enable-postproc –enable-avfilter –enable-pthreads –enable-x11grab –enable-bzlib –enable-libfaac –enable-libmp3lame –enable-libschroedinger –enable-libtheora –enable-libvorbis –enable-libx264 –enable-libxvid –enable-zlib
– Attention: Lot of people are facing error on loading shared libraries libavdevice.so.52, solution is: editer /etc/ld.so.conf et ajouter /opt/ffmbc/lib. Ensuite taper ldconfig
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Fichier de configuration FTP:
/opt/lampp/etc/proftpd.conf
Préciser le répertoire d’upload : /opt/lampp/htdocs/wp-contents/uploads
Référence:
http://wordpress.org/support/topic/how-to-increase-file-size-for-media-upload
Il faut éditer le fichier php.ini qui se trouve:
/opt/lampp/etc/php.ini
Editer les valeurs suivantes pour une limitation à 20 GB
memory_limit = 128M
upload_max_filesize = 20000M
post_max_size = 20000M
file_uploads = On
Sous Linux, il est facile d’automatiser des tâches, avec init pour lancer une tâche au démarrage, ou bien avec cron pour lancer une tâche à un moment précis.
Il y a plusieurs logiciels gérant les crons, ici le logiciel crontab est présenté.
Avant tout, il faut créer un nouveau fichier qui exécutera le code que l’on veut.
Pour cela, il suffit d’ouvrir un éditeur (en tant que root), et d’enregistrer le fichier dans le dossier voulu (voir plus bas). N’oubliez pas d’indiquer l’interpréteur à utiliser au début du fichier.
Par exemple (avec bash) :
#!/bin/bash commande; ...
Il est possible d’utiliser un autre interpréteur, en changeant simplement #!/bin/bash par l’interpréteur choisi : #!/bin/python, #!/bin/perl, etc.
Ensuite, il faut rendre le fichier exécutable :
# chmod 755 /repertoire/monfichier
init est le premier processus, exécuté par le noyau, qui est père de tous les autres (son PID est donc 1).
Au démarrage, il lance divers scripts contenus dans /etc/init.d/ ou /etc/rc*.d/.
C’est dans le dossier /etc/init.d qu’il faut enregistrer les fichiers à lancer au démarrage.
Il faut ensuite ajouter le fichier à la liste des processus lancés au démarrage :
# update-rc.d mon-fichier defaults
Tapez dans un terminal :
The generic syntax is:
ffmbc[[infile options][‘-i’ infile]]... {[outfile options] outfile}...
|
FFmbc is a very fast video and audio converter. It can also grab from a live audio/video source.
The command line interface is designed to be intuitive, in the sense that FFmpeg tries to figure out all parameters that can possibly be derived automatically. You usually only have to specify the target bitrate you want.
FFmbc can also convert from any sample rate to any other, and resize video on the fly with a high quality polyphase filter.
As a general rule, options are applied to the next specified file. Therefore, order is important, and you can have the same option on the command line multiple times. Each occurrence is then applied to the next input or output file.
ffmbc -i input.avi -b 64k output.avi |
ffmbc -i input.avi -r 24 output.avi |
ffmbc -r 1 -i input.m2v -r 24 output.avi |
The format option may be needed for raw input files.
By default, FFmbc tries to convert as losslessly as possible: It uses the same audio and video parameters for the outputs as the one specified for the inputs.
All the numerical options, if not specified otherwise, accept in input a string representing a number, which may contain one of the International System number postfixes, for example ’K’, ’M’, ’G’. If ’i’ is appended after the postfix, powers of 2 are used instead of powers of 10. The ’B’ postfix multiplies the value for 8, and can be appended after another postfix or used alone. This allows using for example ’KB’, ’MiB’, ’G’ and ’B’ as postfix.
Options which do not take arguments are boolean options, and set the corresponding value to true. They can be set to false by prefixing with « no » the option name, for example using « -nofoo » in the commandline will set to false the boolean option with name « foo ».
These options are shared amongst the ff* tools.
The fields preceding the format names have the following meanings:
The fields preceding the codec names have the following meanings:
By default the program logs to stderr, if coloring is supported by the terminal, colors are used to mark errors and warnings. Log coloring can be disabled setting the environment variable FFMPEG_FORCE_NOCOLOR or NO_COLOR, or can be forced setting the environment variable FFMPEG_FORCE_COLOR. The use of the environment variable NO_COLOR is deprecated and will be dropped in a following FFmpeg version.
Emplacement des fichiershh:mm:ss[.xxx] syntax is also supported.
hh:mm:ss[.xxx] syntax is also supported.
[-]hh:mm:ss[.xxx] syntax is also supported. This option affects all the input files that follow it. The offset is added to the timestamps of the input files. Specifying a positive offset means that the corresponding streams are delayed by ’offset’ seconds.
now|([(YYYY-MM-DD|YYYYMMDD)[T|t| ]]((HH[:MM[:SS[.m...]]])|(HH[MM[SS[.m...]]]))[Z|z]) |
If the value is « now » it takes the current time. Time is local time unless ’Z’ or ’z’ is appended, in which case it is interpreted as UTC. If the year-month-day part is not specified it takes the current year-month-day.
For example, for setting the title in the output file:
ffmpeg -i in.avi -metadata title="my title" out.flv |
ffmpeg -i myfile.avi -target vcd /tmp/vcd.mpg |
Nevertheless you can specify additional options as long as you know they do not conflict with the standard, as in:
ffmpeg -i myfile.avi -target vcd -bf 2 /tmp/vcd.mpg |
ffmpeg -i myfile.avi -b 4000k -minrate 4000k -maxrate 4000k -bufsize 1835k out.m2v |
It is of little use elsewise.
copy special value to tell that the raw codec data must be copied as is.
ffmpeg -i foo.mov -vcodec libxvid -pass 1 -an -f rawvideo -y NUL ffmpeg -i foo.mov -vcodec libxvid -pass 1 -an -f rawvideo -y /dev/null |
These four options (lmin, lmax, mblmin, mblmax) use ’lambda’ units, but you may use the QP2LAMBDA constant to easily convert from ’q’ units:
ffmpeg -i src.ext -lmax 21*QP2LAMBDA dst.ext |
tex^qComp).
When computing the rate control equation expression, besides the standard functions defined in the section « Expression Evaluation », the following functions are available:
and the following constants are available:
ffmpeg -i h264.mp4 -vcodec copy -vbsf h264_mp4toannexb -an out.h264 |
copy special value to specify that the raw codec data must be copied as is.
-newaudio (-acodec, -ab, etc..).
Mapping will be done automatically, if the number of output streams is equal to the number of input streams, else it will pick the first one that matches. You can override the mapping using -map as usual.
Example:
ffmpeg -i file.mpg -vcodec copy -acodec ac3 -ab 384k test.mpg -acodec mp2 -ab 192k -newaudio |
ffmpeg -i file.mov -an -vn -sbsf mov2textsub -scodec copy -f rawvideo sub.txt |
By default, global metadata is copied from the first input file to all output files, per-stream and per-chapter metadata is copied along with streams/chapters. These default mappings are disabled by creating any mapping of the relevant type. A negative file index can be used to create a dummy mapping that just disables automatic copying.
For example to copy metadata from the first stream of the input file to global metadata of the output file:
ffmpeg -i in.ogg -map_metadata 0:0,s0 out.mp3 |
With -map you can select from which stream the timestamps should be taken. You can leave either video or audio unchanged and sync the remaining stream(s) to the unchanged one.
For example, to set the stream 0 PID to 33 and the stream 1 PID to 36 for an output mpegts file:
ffmpeg -i infile -streamid 0:33 -streamid 1:36 out.ts |
A preset file contains a sequence of option=value pairs, one for each line, specifying a sequence of options which would be awkward to specify on the command line. Lines starting with the hash (’#’) character are ignored and are used to provide comments. Check the ‘ffpresets’ directory in the FFmpeg source tree for examples.
Preset files are specified with the vpre, apre, spre, and fpre options. The fpre option takes the filename of the preset instead of a preset name as input and can be used for any kind of codec. For the vpre, apre, and spre options, the options specified in a preset file are applied to the currently selected codec of the same type as the preset option.
The argument passed to the vpre, apre, and spre preset options identifies the preset file to use according to the following rules:
First ffmpeg searches for a file named arg.ffpreset in the directories ‘$FFMPEG_DATADIR’ (if set), and ‘$HOME/.ffmpeg’, and in the datadir defined at configuration time (usually ‘PREFIX/share/ffmpeg’) in that order. For example, if the argument is libx264-max, it will search for the file ‘libx264-max.ffpreset’.
If no such file is found, then ffmpeg will search for a file named codec_name–arg.ffpreset in the above-mentioned directories, where codec_name is the name of the codec to which the preset file options will be applied. For example, if you select the video codec with -vcodec libx264 and use -vpre max, then it will search for the file ‘libx264-max.ffpreset’.
ffmpeg -g 3 -r 3 -t 10 -b 50k -s qcif -f rv10 /tmp/b.rm |
FFmpeg can grab video and audio from devices given that you specify the input format and device.
ffmpeg -f oss -i /dev/dsp -f video4linux2 -i /dev/video0 /tmp/out.mpg |
Note that you must activate the right video source and channel before launching FFmpeg with any TV viewer such as xawtv (http://linux.bytesex.org/xawtv/) by Gerd Knorr. You also have to set the audio recording levels correctly with a standard mixer.
FFmpeg can grab the X11 display.
ffmpeg -f x11grab -s cif -r 25 -i :0.0 /tmp/out.mpg |
0.0 is display.screen number of your X11 server, same as the DISPLAY environment variable.
ffmpeg -f x11grab -s cif -r 25 -i :0.0+10,20 /tmp/out.mpg |
0.0 is display.screen number of your X11 server, same as the DISPLAY environment variable. 10 is the x-offset and 20 the y-offset for the grabbing.
FFmpeg can use any supported file format and protocol as input:
Examples:
ffmpeg -i /tmp/test%d.Y /tmp/out.mpg |
It will use the files:
/tmp/test0.Y, /tmp/test0.U, /tmp/test0.V, /tmp/test1.Y, /tmp/test1.U, /tmp/test1.V, etc... |
The Y files use twice the resolution of the U and V files. They are raw files, without header. They can be generated by all decent video decoders. You must specify the size of the image with the ‘-s’ option if FFmpeg cannot guess it.
ffmpeg -i /tmp/test.yuv /tmp/out.avi |
test.yuv is a file containing raw YUV planar data. Each frame is composed of the Y plane followed by the U and V planes at half vertical and horizontal resolution.
ffmpeg -i mydivx.avi hugefile.yuv |
ffmpeg -i /tmp/a.wav -s 640x480 -i /tmp/a.yuv /tmp/a.mpg |
Converts the audio file a.wav and the raw YUV video file a.yuv to MPEG file a.mpg.
ffmpeg -i /tmp/a.wav -ar 22050 /tmp/a.mp2 |
Converts a.wav to MPEG audio at 22050 Hz sample rate.
ffmpeg -i /tmp/a.wav -ab 64k /tmp/a.mp2 -ab 128k /tmp/b.mp2 -map 0:0 -map 0:0 |
Converts a.wav to a.mp2 at 64 kbits and to b.mp2 at 128 kbits. ’-map file:index’ specifies which input stream is used for each output stream, in the order of the definition of output streams.
ffmpeg -i snatch_1.vob -f avi -vcodec mpeg4 -b 800k -g 300 -bf 2 -acodec libmp3lame -ab 128k snatch.avi |
This is a typical DVD ripping example; the input is a VOB file, the output an AVI file with MPEG-4 video and MP3 audio. Note that in this command we use B-frames so the MPEG-4 stream is DivX5 compatible, and GOP size is 300 which means one intra frame every 10 seconds for 29.97fps input video. Furthermore, the audio stream is MP3-encoded so you need to enable LAME support by passing --enable-libmp3lame to configure. The mapping is particularly useful for DVD transcoding to get the desired audio language.
NOTE: To see the supported input formats, use ffmpeg -formats.
ffmpeg -i foo.avi -r 1 -s WxH -f image2 foo-%03d.jpeg |
This will extract one video frame per second from the video and will output them in files named ‘foo-001.jpeg’, ‘foo-002.jpeg’, etc. Images will be rescaled to fit the new WxH values.
If you want to extract just a limited number of frames, you can use the above command in combination with the -vframes or -t option, or in combination with -ss to start extracting from a certain point in time.
For creating a video from many images:
ffmpeg -f image2 -i foo-%03d.jpeg -r 12 -s WxH foo.avi |
The syntax foo-%03d.jpeg specifies to use a decimal number composed of three digits padded with zeroes to express the sequence number. It is the same syntax supported by the C printf function, but only formats accepting a normal integer are suitable.
ffmpeg -i test1.avi -i test2.avi -vcodec copy -acodec copy -vcodec copy -acodec copy test12.avi -newvideo -newaudio |
In addition to the first video and audio streams, the resulting output file ‘test12.avi’ will contain the second video and the second audio stream found in the input streams list.
The -newvideo, -newaudio and -newsubtitle options have to be specified immediately after the name of the output file to which you want to add them.
When evaluating an arithemetic expression, FFmpeg uses an internal formula evaluator, implemented through the ‘libavutil/eval.h’ interface.
An expression may contain unary, binary operators, constants, and functions.
Two expressions expr1 and expr2 can be combined to form another expression « expr1;expr2« . expr1 and expr2 are evaluated in turn, and the new expression evaluates to the value of expr2.
The following binary operators are available: +, -, *, /, ^.
The following unary operators are available: +, -.
The following functions are available:
Note that:
* works like AND
+ works like OR
thus
if A then B else C |
is equivalent to
A*B + not(A)*C |
When A evaluates to either 1 or 0, that is the same as
A*B + eq(A,0)*C |
In your C code, you can extend the list of unary and binary functions, and define recognized constants, so that they are available for your expressions.
The evaluator also recognizes the International System number postfixes. If ’i’ is appended after the postfix, powers of 2 are used instead of powers of 10. The ’B’ postfix multiplies the value for 8, and can be appended after another postfix or used alone. This allows using for example ’KB’, ’MiB’, ’G’ and ’B’ as postfix.
Follows the list of available International System postfixes, with indication of the corresponding powers of 10 and of 2.
Demuxers are configured elements in FFmpeg which allow to read the multimedia streams from a particular type of file.
When you configure your FFmpeg build, all the supported demuxers are enabled by default. You can list all available ones using the configure option « –list-demuxers ».
You can disable all the demuxers using the configure option « –disable-demuxers », and selectively enable a single demuxer with the option « –enable-demuxer=DEMUXER« , or disable it with the option « –disable-demuxer=DEMUXER« .
The option « -formats » of the ff* tools will display the list of enabled demuxers.
The description of some of the currently available demuxers follows.
Image file demuxer.
This demuxer reads from a list of image files specified by a pattern.
The pattern may contain the string « %d » or « %0Nd », which specifies the position of the characters representing a sequential number in each filename matched by the pattern. If the form « %d0Nd » is used, the string representing the number in each filename is 0-padded and N is the total number of 0-padded digits representing the number. The literal character ’%’ can be specified in the pattern with the string « %% ».
If the pattern contains « %d » or « %0Nd », the first filename of the file list specified by the pattern must contain a number inclusively contained between 0 and 4, all the following numbers must be sequential. This limitation may be hopefully fixed.
The pattern may contain a suffix which is used to automatically determine the format of the images contained in the files.
For example the pattern « img-%03d.bmp » will match a sequence of filenames of the form ‘img-001.bmp’, ‘img-002.bmp’, …, ‘img-010.bmp’, etc.; the pattern « i%%m%%g-%d.jpg » will match a sequence of filenames of the form ‘i%m%g-1.jpg’, ‘i%m%g-2.jpg’, …, ‘i%m%g-10.jpg’, etc.
The size, the pixel format, and the format of each image must be the same for all the files in the sequence.
The following example shows how to use ‘ffmpeg’ for creating a video from the images in the file sequence ‘img-001.jpeg’, ‘img-002.jpeg’, …, assuming an input framerate of 10 frames per second:
ffmpeg -r 10 -f image2 -i 'img-%03d.jpeg' out.avi |
Note that the pattern must not necessarily contain « %d » or « %0Nd », for example to convert a single image file ‘img.jpeg’ you can employ the command:
ffmpeg -f image2 -i img.jpeg img.png |
Muxers are configured elements in FFmpeg which allow writing multimedia streams to a particular type of file.
When you configure your FFmpeg build, all the supported muxers are enabled by default. You can list all available muxers using the configure option --list-muxers.
You can disable all the muxers with the configure option --disable-muxers and selectively enable / disable single muxers with the options --enable-muxer=MUXER / --disable-muxer=MUXER.
The option -formats of the ff* tools will display the list of enabled muxers.
A description of some of the currently available muxers follows.
CRC (Cyclic Redundancy Check) testing format.
This muxer computes and prints the Adler-32 CRC of all the input audio and video frames. By default audio frames are converted to signed 16-bit raw audio and video frames to raw video before computing the CRC.
The output of the muxer consists of a single line of the form: CRC=0xCRC, where CRC is a hexadecimal number 0-padded to 8 digits containing the CRC for all the decoded input frames.
For example to compute the CRC of the input, and store it in the file ‘out.crc’:
ffmpeg -i INPUT -f crc out.crc |
You can print the CRC to stdout with the command:
ffmpeg -i INPUT -f crc - |
You can select the output format of each frame with ‘ffmpeg’ by specifying the audio and video codec and format. For example to compute the CRC of the input audio converted to PCM unsigned 8-bit and the input video converted to MPEG-2 video, use the command:
ffmpeg -i INPUT -acodec pcm_u8 -vcodec mpeg2video -f crc - |
See also the framecrc muxer (see framecrc).
Per-frame CRC (Cyclic Redundancy Check) testing format.
This muxer computes and prints the Adler-32 CRC for each decoded audio and video frame. By default audio frames are converted to signed 16-bit raw audio and video frames to raw video before computing the CRC.
The output of the muxer consists of a line for each audio and video frame of the form: stream_index, frame_dts, frame_size, 0xCRC, where CRC is a hexadecimal number 0-padded to 8 digits containing the CRC of the decoded frame.
For example to compute the CRC of each decoded frame in the input, and store it in the file ‘out.crc’:
ffmpeg -i INPUT -f framecrc out.crc |
You can print the CRC of each decoded frame to stdout with the command:
ffmpeg -i INPUT -f framecrc - |
You can select the output format of each frame with ‘ffmpeg’ by specifying the audio and video codec and format. For example, to compute the CRC of each decoded input audio frame converted to PCM unsigned 8-bit and of each decoded input video frame converted to MPEG-2 video, use the command:
ffmpeg -i INPUT -acodec pcm_u8 -vcodec mpeg2video -f framecrc - |
See also the crc muxer (see crc).
Image file muxer.
The image file muxer writes video frames to image files.
The output filenames are specified by a pattern, which can be used to produce sequentially numbered series of files. The pattern may contain the string « %d » or « %0Nd », this string specifies the position of the characters representing a numbering in the filenames. If the form « %0Nd » is used, the string representing the number in each filename is 0-padded to N digits. The literal character ’%’ can be specified in the pattern with the string « %% ».
If the pattern contains « %d » or « %0Nd », the first filename of the file list specified will contain the number 1, all the following numbers will be sequential.
The pattern may contain a suffix which is used to automatically determine the format of the image files to write.
For example the pattern « img-%03d.bmp » will specify a sequence of filenames of the form ‘img-001.bmp’, ‘img-002.bmp’, …, ‘img-010.bmp’, etc. The pattern « img%%-%d.jpg » will specify a sequence of filenames of the form ‘img%-1.jpg’, ‘img%-2.jpg’, …, ‘img%-10.jpg’, etc.
The following example shows how to use ‘ffmpeg’ for creating a sequence of files ‘img-001.jpeg’, ‘img-002.jpeg’, …, taking one image every second from the input video:
ffmpeg -i in.avi -r 1 -f image2 'img-%03d.jpeg' |
Note that with ‘ffmpeg’, if the format is not specified with the -f option and the output filename specifies an image file format, the image2 muxer is automatically selected, so the previous command can be written as:
ffmpeg -i in.avi -r 1 'img-%03d.jpeg' |
Note also that the pattern must not necessarily contain « %d » or « %0Nd », for example to create a single image file ‘img.jpeg’ from the input video you can employ the command:
ffmpeg -i in.avi -f image2 -vframes 1 img.jpeg |
MPEG transport stream muxer.
This muxer implements ISO 13818-1 and part of ETSI EN 300 468.
The muxer options are:
The recognized metadata settings in mpegts muxer are service_provider and service_name. If they are not set the default for service_provider is « FFmpeg » and the default for service_name is « Service01 ».
ffmpeg -i file.mpg -acodec copy -vcodec copy \
-mpegts_original_network_id 0x1122 \
-mpegts_transport_stream_id 0x3344 \
-mpegts_service_id 0x5566 \
-mpegts_pmt_start_pid 0x1500 \
-mpegts_start_pid 0x150 \
-metadata service_provider="Some provider" \
-metadata service_name="Some Channel" \
-y out.ts
|
Null muxer.
This muxer does not generate any output file, it is mainly useful for testing or benchmarking purposes.
For example to benchmark decoding with ‘ffmpeg’ you can use the command:
ffmpeg -benchmark -i INPUT -f null out.null |
Note that the above command does not read or write the ‘out.null’ file, but specifying the output file is required by the ‘ffmpeg’ syntax.
Alternatively you can write the command as:
ffmpeg -benchmark -i INPUT -f null - |
Input devices are configured elements in FFmpeg which allow to access 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 « -formats » of the ff* tools will display the list of supported input devices (amongst the demuxers).
A description of the currently available input devices follows.
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
BSD video input device.
Linux DV 1394 input device.
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/
IIDC1394 input device, based on libdc1394 and libraw1394.
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
Video4Linux and Video4Linux2 input video devices.
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.
Video4Linux and Video4Linux2 devices only support a limited set of widthxheight sizes and framerates. You can check which are supported for example with the command ‘dov4l’ for Video4Linux devices and the command ‘v4l-info’ for Video4Linux2 devices.
If the size for the device is set to 0x0, the input device will try to autodetect the size to use. Only for the video4linux2 device, if the frame rate is set to 0/0 the input device will use the frame rate value already set in the driver.
Video4Linux support is deprecated since Linux 2.6.30, and will be dropped in later versions.
Follow some usage examples of the video4linux devices with the ff* tools.
# Grab and show the input of a video4linux device, frame rate is set # to the default of 25/1. ffplay -s 320x240 -f video4linux /dev/video0 # Grab and show the input of a video4linux2 device, autoadjust size. ffplay -f video4linux2 /dev/video0 # Grab and record the input of a video4linux2 device, autoadjust size, # frame rate value defaults to 0/0 so it is read from the video4linux2 # driver. ffmpeg -f video4linux2 -i /dev/video0 out.mpeg |
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.
This device allows 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 ommitted, 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 ‘dpyinfo’ 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 -r 25 -s cif -i :0.0 out.mpg # Grab at position 10,20. ffmpeg -f x11grab -25 -s cif -i :0.0+10,20 out.mpg |
Output devices are configured elements in FFmpeg which allow to 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 « -formats » of the ff* tools will display the list of enabled output devices (amongst the muxers).
A description of the currently available output devices follows.
ALSA (Advanced Linux Sound Architecture) output device.
OSS (Open Sound System) output device.
Protocols are configured elements in FFmpeg which allow to access resources which require the use of a particular protocol.
When you configure your FFmpeg build, all the supported protocols are enabled by default. You can list all available ones using the configure option « –list-protocols ».
You can disable all the protocols using the configure option « –disable-protocols », and selectively enable a protocol using the option « –enable-protocol=PROTOCOL« , or you can disable a particular protocol using the option « –disable-protocol=PROTOCOL« .
The option « -protocols » of the ff* tools will display the list of supported protocols.
A description of the currently available protocols follows.
Physical concatenation protocol.
Allow to read and seek from many resource in sequence as if they were a unique resource.
A URL accepted by this protocol has the syntax:
concat:URL1|URL2|...|URLN |
where URL1, URL2, …, URLN are the urls of the resource to be concatenated, each one possibly specifying a distinct protocol.
For example to read a sequence of files ‘split1.mpeg’, ‘split2.mpeg’, ‘split3.mpeg’ with ‘ffplay’ use the command:
ffplay concat:split1.mpeg\|split2.mpeg\|split3.mpeg |
Note that you may need to escape the character « | » which is special for many shells.
File access protocol.
Allow to read from or read to a file.
For example to read from a file ‘input.mpeg’ with ‘ffmpeg’ use the command:
ffmpeg -i file:input.mpeg output.mpeg |
The ff* tools default to the file protocol, that is a resource specified with the name « FILE.mpeg » is interpreted as the URL « file:FILE.mpeg ».
Gopher protocol.
HTTP (Hyper Text Transfer Protocol).
MMS (Microsoft Media Server) protocol over TCP.
MMS (Microsoft Media Server) protocol over HTTP.
The required syntax is:
mmsh://server[:port][/app][/playpath] |
MD5 output protocol.
Computes the MD5 hash of the data to be written, and on close writes this to the designated output or stdout if none is specified. It can be used to test muxers without writing an actual file.
Some examples follow.
# Write the MD5 hash of the encoded AVI file to the file output.avi.md5. ffmpeg -i input.flv -f avi -y md5:output.avi.md5 # Write the MD5 hash of the encoded AVI file to stdout. ffmpeg -i input.flv -f avi -y md5: |
Note that some formats (typically MOV) require the output protocol to be seekable, so they will fail with the MD5 output protocol.
UNIX pipe access protocol.
Allow to read and write from UNIX pipes.
The accepted syntax is:
pipe:[number] |
number is the number corresponding to the file descriptor of the pipe (e.g. 0 for stdin, 1 for stdout, 2 for stderr). If number is not specified, by default the stdout file descriptor will be used for writing, stdin for reading.
For example to read from stdin with ‘ffmpeg’:
cat test.wav | ffmpeg -i pipe:0 # ...this is the same as... cat test.wav | ffmpeg -i pipe: |
For writing to stdout with ‘ffmpeg’:
ffmpeg -i test.wav -f avi pipe:1 | cat > test.avi # ...this is the same as... ffmpeg -i test.wav -f avi pipe: | cat > test.avi |
Note that some formats (typically MOV), require the output protocol to be seekable, so they will fail with the pipe output protocol.
Real-Time Messaging Protocol.
The Real-Time Messaging Protocol (RTMP) is used for streaming multime‐ dia content across a TCP/IP network.
The required syntax is:
rtmp://server[:port][/app][/playpath] |
The accepted parameters are:
For example to read with ‘ffplay’ a multimedia resource named « sample » from the application « vod » from an RTMP server « myserver »:
ffplay rtmp://myserver/vod/sample |
Real-Time Messaging Protocol and its variants supported through librtmp.
Requires the presence of the librtmp headers and library during configuration. You need to explicitely configure the build with « –enable-librtmp ». If enabled this will replace the native RTMP protocol.
This protocol provides most client functions and a few server functions needed to support RTMP, RTMP tunneled in HTTP (RTMPT), encrypted RTMP (RTMPE), RTMP over SSL/TLS (RTMPS) and tunneled variants of these encrypted types (RTMPTE, RTMPTS).
The required syntax is:
rtmp_proto://server[:port][/app][/playpath] options |
where rtmp_proto is one of the strings « rtmp », « rtmpt », « rtmpe », « rtmps », « rtmpte », « rtmpts » corresponding to each RTMP variant, and server, port, app and playpath have the same meaning as specified for the RTMP native protocol. options contains a list of space-separated options of the form key=val.
See the librtmp manual page (man 3 librtmp) for more information.
For example, to stream a file in real-time to an RTMP server using ‘ffmpeg’:
ffmpeg -re -i myfile -f flv rtmp://myserver/live/mystream |
To play the same stream using ‘ffplay’:
ffplay "rtmp://myserver/live/mystream live=1" |
Real-Time Protocol.
RTSP is not technically a protocol handler in libavformat, it is a demuxer and muxer. The demuxer supports both normal RTSP (with data transferred over RTP; this is used by e.g. Apple and Microsoft) and Real-RTSP (with data transferred over RDT).
The muxer can be used to send a stream using RTSP ANNOUNCE to a server supporting it (currently Darwin Streaming Server and Mischa Spiegelmock’s RTSP server, http://github.com/revmischa/rtsp-server).
The required syntax for a RTSP url is:
rtsp://hostname[:port]/path[?options] |
options is a &-separated list. The following options are supported:
Multiple lower transport protocols may be specified, in that case they are tried one at a time (if the setup of one fails, the next one is tried). For the muxer, only the tcp and udp options are supported.
When receiving data over UDP, the demuxer tries to reorder received packets (since they may arrive out of order, or packets may get lost totally). In order for this to be enabled, a maximum delay must be specified in the max_delay field of AVFormatContext.
When watching multi-bitrate Real-RTSP streams with ‘ffplay’, the streams to display can be chosen with -vst n and -ast n for video and audio respectively, and can be switched on the fly by pressing v and a.
Example command lines:
To watch a stream over UDP, with a max reordering delay of 0.5 seconds:
ffplay -max_delay 500000 rtsp://server/video.mp4?udp |
To watch a stream tunneled over HTTP:
ffplay rtsp://server/video.mp4?http |
To send a stream in realtime to a RTSP server, for others to watch:
ffmpeg -re -i input -f rtsp -muxdelay 0.1 rtsp://server/live.sdp |
Session Announcement Protocol (RFC 2974). This is not technically a protocol handler in libavformat, it is a muxer and demuxer. It is used for signalling of RTP streams, by announcing the SDP for the streams regularly on a separate port.
The syntax for a SAP url given to the muxer is:
sap://destination[:port][?options] |
The RTP packets are sent to destination on port port, or to port 5004 if no port is specified. options is a &-separated list. The following options are supported:
Example command lines follow.
To broadcast a stream on the local subnet, for watching in VLC:
ffmpeg -re -i input -f sap sap://224.0.0.255?same_port=1 |
Similarly, for watching in ffplay:
ffmpeg -re -i input -f sap sap://224.0.0.255 |
And for watching in ffplay, over IPv6:
ffmpeg -re -i input -f sap sap://[ff0e::1:2:3:4] |
The syntax for a SAP url given to the demuxer is:
sap://[address][:port] |
address is the multicast address to listen for announcements on, if omitted, the default 224.2.127.254 (sap.mcast.net) is used. port is the port that is listened on, 9875 if omitted.
The demuxers listens for announcements on the given address and port. Once an announcement is received, it tries to receive that particular stream.
Example command lines follow.
To play back the first stream announced on the normal SAP multicast address:
ffplay sap:// |
To play back the first stream announced on one the default IPv6 SAP multicast address:
ffplay sap://[ff0e::2:7ffe] |
Trasmission Control Protocol.
User Datagram Protocol.
The required syntax for a UDP url is:
udp://hostname:port[?options] |
options contains a list of &-seperated options of the form key=val. Follow the list of supported options.
connect(). In this case, the destination address can’t be changed with udp_set_remote_url later. If the destination address isn’t known at the start, this option can be specified in udp_set_remote_url, too. This allows finding out the source address for the packets with getsockname, and makes writes return with AVERROR(ECONNREFUSED) if « destination unreachable » is received. For receiving, this gives the benefit of only receiving packets from the specified peer address/port.
Some usage examples of the udp protocol with ‘ffmpeg’ follow.
To stream over UDP to a remote endpoint:
ffmpeg -i input -f format udp://hostname:port |
To stream in mpegts format over UDP using 188 sized UDP packets, using a large input buffer:
ffmpeg -i input -f mpegts udp://hostname:port?pkt_size=188&buffer_size=65535 |
To receive over UDP from a remote endpoint:
ffmpeg -i udp://[multicast-address]:port |
When you configure your FFmpeg build, all the supported bitstream filters are enabled by default. You can list all available ones using the configure option --list-bsfs.
You can disable all the bitstream filters using the configure option --disable-bsfs, and selectively enable any bitstream filter using the option --enable-bsf=BSF, or you can disable a particular bitstream filter using the option --disable-bsf=BSF.
The option -bsfs of the ff* tools will display the list of all the supported bitstream filters included in your build.
Below is a description of the currently available bitstream filters.
Convert MJPEG/AVI1 packets to full JPEG/JFIF packets.
MJPEG is a video codec wherein each video frame is essentially a JPEG image. The individual frames can be extracted without loss, e.g. by
ffmpeg -i ../some_mjpeg.avi -vcodec copy frames_%d.jpg |
Unfortunately, these chunks are incomplete JPEG images, because they lack the DHT segment required for decoding. Quoting from http://www.digitalpreservation.gov/formats/fdd/fdd000063.shtml:
Avery Lee, writing in the rec.video.desktop newsgroup in 2001, commented that « MJPEG, or at least the MJPEG in AVIs having the MJPG fourcc, is restricted JPEG with a fixed – and *omitted* – Huffman table. The JPEG must be YCbCr colorspace, it must be 4:2:2, and it must use basic Huffman encoding, not arithmetic or progressive. . . . You can indeed extract the MJPEG frames and decode them with a regular JPEG decoder, but you have to prepend the DHT segment to them, or else the decoder won’t have any idea how to decompress the data. The exact table necessary is given in the OpenDML spec. »
This bitstream filter patches the header of frames extracted from an MJPEG stream (carrying the AVI1 header ID and lacking a DHT segment) to produce fully qualified JPEG images.
ffmpeg -i mjpeg-movie.avi -vcodec copy -vbsf mjpeg2jpeg frame_%d.jpg exiftran -i -9 frame*.jpg ffmpeg -i frame_%d.jpg -vcodec copy rotated.avi |
A filtergraph is a directed graph of connected filters. It can contain cycles, and there can be multiple links between a pair of filters. Each link has one input pad on one side connecting it to one filter from which it takes its input, and one output pad on the other side connecting it to the one filter accepting its output.
Each filter in a filtergraph is an instance of a filter class registered in the application, which defines the features and the number of input and output pads of the filter.
A filter with no input pads is called a « source », a filter with no output pads is called a « sink ».
A filtergraph can be represented using a textual representation, which is recognized by the -vf and -af options of the ff* tools, and by the av_parse_graph() function defined in ‘libavfilter/avfiltergraph’.
A filterchain consists of a sequence of connected filters, each one connected to the previous one in the sequence. A filterchain is represented by a list of « , »-separated filter descriptions.
A filtergraph consists of a sequence of filterchains. A sequence of filterchains is represented by a list of « ; »-separated filterchain descriptions.
A filter is represented by a string of the form: [in_link_1]…[in_link_N]filter_name=arguments[out_link_1]…[out_link_M]
filter_name is the name of the filter class of which the described filter is an instance of, and has to be the name of one of the filter classes registered in the program. The name of the filter class is optionally followed by a string « =arguments« .
arguments is a string which contains the parameters used to initialize the filter instance, and are described in the filter descriptions below.
The list of arguments can be quoted using the character « ’ » as initial and ending mark, and the character ’\’ for escaping the characters within the quoted text; otherwise the argument string is considered terminated when the next special character (belonging to the set « []=;, ») is encountered.
The name and arguments of the filter are optionally preceded and followed by a list of link labels. A link label allows to name a link and associate it to a filter output or input pad. The preceding labels in_link_1 … in_link_N, are associated to the filter input pads, the following labels out_link_1 … out_link_M, are associated to the output pads.
When two link labels with the same name are found in the filtergraph, a link between the corresponding input and output pad is created.
If an output pad is not labelled, it is linked by default to the first unlabelled input pad of the next filter in the filterchain. For example in the filterchain:
nullsrc, split[L1], [L2]overlay, nullsink |
the split filter instance has two output pads, and the overlay filter instance two input pads. The first output pad of split is labelled « L1 », the first input pad of overlay is labelled « L2 », and the second output pad of split is linked to the second input pad of overlay, which are both unlabelled.
In a complete filterchain all the unlabelled filter input and output pads must be connected. A filtergraph is considered valid if all the filter input and output pads of all the filterchains are connected.
Follows a BNF description for the filtergraph syntax:
NAME ::= sequence of alphanumeric characters and '_' LINKLABEL ::= "[" NAME "]" LINKLABELS ::= LINKLABEL [LINKLABELS] FILTER_ARGUMENTS ::= sequence of chars (eventually quoted) FILTER ::= [LINKNAMES] NAME ["=" ARGUMENTS] [LINKNAMES] FILTERCHAIN ::= FILTER [,FILTERCHAIN] FILTERGRAPH ::= FILTERCHAIN [;FILTERGRAPH] |
When you configure your FFmpeg build, you can disable any of the existing filters using –disable-filters. The configure output will show the audio filters included in your build.
Below is a description of the currently available audio filters.
Pass the audio source unchanged to the output.
Below is a description of the currently available audio sources.
Null audio source, never return audio frames. It is mainly useful as a template and to be employed in analysis / debugging tools.
It accepts as optional parameter a string of the form sample_rate:channel_layout.
sample_rate specify the sample rate, and defaults to 44100.
channel_layout specify the channel layout, and can be either an integer or a string representing a channel layout. The default value of channel_layout is 3, which corresponds to CH_LAYOUT_STEREO.
Check the channel_layout_map definition in ‘libavcodec/audioconvert.c’ for the mapping between strings and channel layout values.
Follow some examples:
# set the sample rate to 48000 Hz and the channel layout to CH_LAYOUT_MONO. anullsrc=48000:4 # same as anullsrc=48000:mono |
Below is a description of the currently available audio sinks.
Null audio sink, do absolutely nothing with the input audio. It is mainly useful as a template and to be employed in analysis / debugging tools.
When you configure your FFmpeg build, you can disable any of the existing filters using –disable-filters. The configure output will show the video filters included in your build.
Below is a description of the currently available video filters.
Detect frames that are (almost) completely black. Can be useful to detect chapter transitions or commercials. Output lines consist of the frame number of the detected frame, the percentage of blackness, the position in the file if known or -1 and the timestamp in seconds.
In order to display the output lines, you need to set the loglevel at least to the AV_LOG_INFO value.
The filter accepts the syntax:
blackframe[=amount:[threshold]] |
amount is the percentage of the pixels that have to be below the threshold, and defaults to 98.
threshold is the threshold below which a pixel value is considered black, and defaults to 32.
Copy the input source unchanged to the output. Mainly useful for testing purposes.
Crop the input video to out_w:out_h:x:y.
The parameters are expressions containing the following constants:
The out_w and out_h parameters specify the expressions for the width and height of the output (cropped) video. They are evaluated just at the configuration of the filter.
The default value of out_w is « in_w », and the default value of out_h is « in_h ».
The expression for out_w may depend on the value of out_h, and the expression for out_h may depend on out_w, but they cannot depend on x and y, as x and y are evaluated after out_w and out_h.
The x and y parameters specify the expressions for the position of the top-left corner of the output (non-cropped) area. They are evaluated for each frame. If the evaluated value is not valid, it is approximated to the nearest valid value.
The default value of x is « (in_w-out_w)/2 », and the default value for y is « (in_h-out_h)/2 », which set the cropped area at the center of the input image.
The expression for x may depend on y, and the expression for y may depend on x.
Follow some examples:
# crop the central input area with size 100x100 crop=100:100 # crop the central input area with size 2/3 of the input video "crop=2/3*in_w:2/3*in_h" # crop the input video central square crop=in_h # delimit the rectangle with the top-left corner placed at position # 100:100 and the right-bottom corner corresponding to the right-bottom # corner of the input image. crop=in_w-100:in_h-100:100:100 # crop 10 pixels from the left and right borders, and 20 pixels from # the top and bottom borders "crop=in_w-2*10:in_h-2*20" # keep only the bottom right quarter of the input image "crop=in_w/2:in_h/2:in_w/2:in_h/2" # crop height for getting Greek harmony "crop=in_w:1/PHI*in_w" # trembling effect "crop=in_w/2:in_h/2:(in_w-out_w)/2+((in_w-out_w)/2)*sin(n/10):(in_h-out_h)/2 +((in_h-out_h)/2)*sin(n/7)" # erratic camera effect depending on timestamp "crop=in_w/2:in_h/2:(in_w-out_w)/2+((in_w-out_w)/2)*sin(t*10):(in_h-out_h)/2 +((in_h-out_h)/2)*sin(t*13)" # set x depending on the value of y "crop=in_w/2:in_h/2:y:10+10*sin(n/10)" |
Auto-detect crop size.
Calculate necessary cropping parameters and prints the recommended parameters through the logging system. The detected dimensions correspond to the non-black area of the input video.
It accepts the syntax:
cropdetect[=limit[:round[:reset]]] |
This can be useful when channel logos distort the video area. 0 indicates never reset and return the largest area encountered during playback.
Draw a colored box on the input image.
It accepts the syntax:
drawbox=x:y:width:height:color |
Follow some examples:
# draw a black box around the edge of the input image drawbox # draw a box with color red and an opacity of 50% drawbox=10:20:200:60:red@0.5" |
Buffer input images and send them when they are requested.
This filter is mainly useful when auto-inserted by the libavfilter framework.
The filter does not take parameters.
Convert the input video to one of the specified pixel formats. Libavfilter will try to pick one that is supported for the input to the next filter.
The filter accepts a list of pixel format names, separated by « : », for example « yuv420p:monow:rgb24 ».
Some examples follow:
# convert the input video to the format "yuv420p" format=yuv420p # convert the input video to any of the formats in the list format=yuv420p:yuv444p:yuv410p |
Apply a frei0r effect to the input video.
To enable compilation of this filter you need to install the frei0r header and configure FFmpeg with –enable-frei0r.
The filter supports the syntax:
filter_name[{:|=}param1:param2:...:paramN]
|
filter_name is the name to the frei0r effect to load. If the environment variable FREI0R_PATH is defined, the frei0r effect is searched in each one of the directories specified by the colon separated list in FREIOR_PATH, otherwise in the standard frei0r paths, which are in this order: ‘HOME/.frei0r-1/lib/’, ‘/usr/local/lib/frei0r-1/’, ‘/usr/lib/frei0r-1/’.
param1, param2, … , paramN specify the parameters for the frei0r effect.
A frei0r effect parameter can be a boolean (whose values are specified with « y » and « n »), a double, a color (specified by the syntax R/G/B, R, G, and B being float numbers from 0.0 to 1.0) or by an av_parse_color() color description), a position (specified by the syntax X/Y, X and Y being float numbers) and a string.
The number and kind of parameters depend on the loaded effect. If an effect parameter is not specified the default value is set.
Some examples follow:
# apply the distort0r effect, set the first two double parameters frei0r=distort0r:0.5:0.01 # apply the colordistance effect, takes a color as first parameter frei0r=colordistance:0.2/0.3/0.4 frei0r=colordistance:violet frei0r=colordistance:0x112233 # apply the perspective effect, specify the top left and top right # image positions frei0r=perspective:0.2/0.2:0.8/0.2 |
For more information see: http://piksel.org/frei0r
Fix the banding artifacts that are sometimes introduced into nearly flat regions by truncation to 8bit colordepth. Interpolate the gradients that should go where the bands are, and dither them.
The filter takes two optional parameters, separated by ’:’: strength:radius
strength is the maximum amount by which the filter will change any one pixel. Also the threshold for detecting nearly flat regions. Acceptable values range from .51 to 255, default value is 1.2, out-of-range values will be clipped to the valid range.
radius is the neighborhood to fit the gradient to. A larger radius makes for smoother gradients, but also prevents the filter from modifying the pixels near detailed regions. Acceptable values are 8-32, default value is 16, out-of-range values will be clipped to the valid range.
# default parameters gradfun=1.2:16 # omitting radius gradfun=1.2 |
Flip the input video horizontally.
For example to horizontally flip the video in input with ‘ffmpeg’:
ffmpeg -i in.avi -vf "hflip" out.avi |
High precision/quality 3d denoise filter. This filter aims to reduce image noise producing smooth images and making still images really still. It should enhance compressibility.
It accepts the following optional parameters: luma_spatial:chroma_spatial:luma_tmp:chroma_tmp
Force libavfilter not to use any of the specified pixel formats for the input to the next filter.
The filter accepts a list of pixel format names, separated by « : », for example « yuv420p:monow:rgb24 ».
Some examples follow:
# force libavfilter to use a format different from "yuv420p" for the # input to the vflip filter noformat=yuv420p,vflip # convert the input video to any of the formats not contained in the list noformat=yuv420p:yuv444p:yuv410p |
Pass the video source unchanged to the output.
Apply video transform using libopencv.
To enable this filter install libopencv library and headers and configure FFmpeg with –enable-libopencv.
The filter takes the parameters: filter_name{:=}filter_params.
filter_name is the name of the libopencv filter to apply.
filter_params specifies the parameters to pass to the libopencv filter. If not specified the default values are assumed.
Refer to the official libopencv documentation for more precise informations: http://opencv.willowgarage.com/documentation/c/image_filtering.html
Follows the list of supported libopencv filters.
Dilate an image by using a specific structuring element. This filter corresponds to the libopencv function cvDilate.
It accepts the parameters: struct_el:nb_iterations.
struct_el represents a structuring element, and has the syntax: colsxrows+anchor_xxanchor_y/shape
cols and rows represent the number of colums and rows of the structuring element, anchor_x and anchor_y the anchor point, and shape the shape for the structuring element, and can be one of the values « rect », « cross », « ellipse », « custom ».
If the value for shape is « custom », it must be followed by a string of the form « =filename« . The file with name filename is assumed to represent a binary image, with each printable character corresponding to a bright pixel. When a custom shape is used, cols and rows are ignored, the number or columns and rows of the read file are assumed instead.
The default value for struct_el is « 3×3+0x0/rect ».
nb_iterations specifies the number of times the transform is applied to the image, and defaults to 1.
Follow some example:
# use the default values ocv=dilate # dilate using a structuring element with a 5x5 cross, iterate two times ocv=dilate=5x5+2x2/cross:2 # read the shape from the file diamond.shape, iterate two times # the file diamond.shape may contain a pattern of characters like this: # * # *** # ***** # *** # * # the specified cols and rows are ignored (but not the anchor point coordinates) ocv=0x0+2x2/custom=diamond.shape:2 |
Erode an image by using a specific structuring element. This filter corresponds to the libopencv function cvErode.
The filter accepts the parameters: struct_el:nb_iterations, with the same meaning and use of those of the dilate filter (see dilate).
Smooth the input video.
The filter takes the following parameters: type:param1:param2:param3:param4.
type is the type of smooth filter to apply, and can be one of the following values: « blur », « blur_no_scale », « median », « gaussian », « bilateral ». The default value is « gaussian ».
param1, param2, param3, and param4 are parameters whose meanings depend on smooth type. param1 and param2 accept integer positive values or 0, param3 and param4 accept float values.
The default value for param1 is 3, the default value for the other parameters is 0.
These parameters correspond to the parameters assigned to the libopencv function cvSmooth.
Overlay one video on top of another.
It takes two inputs and one output, the first input is the « main » video on which the second input is overlayed.
It accepts the parameters: x:y.
x is the x coordinate of the overlayed video on the main video, y is the y coordinate. The parameters are expressions containing the following parameters:
Be aware that frames are taken from each input video in timestamp order, hence, if their initial timestamps differ, it is a a good idea to pass the two inputs through a setpts=PTS-STARTPTS filter to have them begin in the same zero timestamp, as it does the example for the movie filter.
Follow some examples:
# draw the overlay at 10 pixels from the bottom right # corner of the main video. overlay=main_w-overlay_w-10:main_h-overlay_h-10 # insert a transparent PNG logo in the bottom left corner of the input movie=logo.png [logo]; [in][logo] overlay=10:main_h-overlay_h-10 [out] # insert 2 different transparent PNG logos (second logo on bottom # right corner): movie=logo1.png [logo1]; movie=logo2.png [logo2]; [in][logo1] overlay=10:H-h-10 [in+logo1]; [in+logo1][logo2] overlay=W-w-10:H-h-10 [out] # add a transparent color layer on top of the main video, # WxH specifies the size of the main input to the overlay filter color=red.3:WxH [over]; [in][over] overlay [out] |
You can chain togheter more overlays but the efficiency of such approach is yet to be tested.
Add paddings to the input image, and places the original input at the given coordinates x, y.
It accepts the following parameters: width:height:x:y:color.
Follows the description of the accepted parameters.
The default value of width and height is 0.
The default value of x and y is 0.
The default value of color is « black ».
For example:
# Add paddings with color "violet" to the input video. Output video # size is 640x480, the top-left corner of the input video is placed at # row 0, column 40. pad=640:480:0:40:violet |
Pixel format descriptor test filter, mainly useful for internal testing. The output video should be equal to the input video.
For example:
format=monow, pixdesctest |
can be used to test the monowhite pixel format descriptor definition.
Scale the input video to width:height and/or convert the image format.
For example the command:
./ffmpeg -i in.avi -vf "scale=200:100" out.avi |
will scale the input video to a size of 200×100.
If the input image format is different from the format requested by the next filter, the scale filter will convert the input to the requested format.
If the value for width or height is 0, the respective input size is used for the output.
If the value for width or height is -1, the scale filter will use, for the respective output size, a value that maintains the aspect ratio of the input image.
The default value of width and height is 0.
Change the PTS (presentation timestamp) of the input video frames.
Accept in input an expression evaluated through the eval API, which can contain the following constants:
Some examples follow:
# start counting PTS from zero setpts=PTS-STARTPTS # fast motion setpts=0.5*PTS # slow motion setpts=2.0*PTS # fixed rate 25 fps setpts=N/(25*TB) # fixed rate 25 fps with some jitter setpts='1/(25*TB) * (N + 0.05 * sin(N*2*PI/25))' |
Set the timebase to use for the output frames timestamps. It is mainly useful for testing timebase configuration.
It accepts in input an arithmetic expression representing a rational. The expression can contain the constants « PI », « E », « PHI », « AVTB » (the default timebase), and « intb » (the input timebase).
The default value for the input is « intb ».
Follow some examples.
# set the timebase to 1/25 settb=1/25 # set the timebase to 1/10 settb=0.1 #set the timebase to 1001/1000 settb=1+0.001 #set the timebase to 2*intb settb=2*intb #set the default timebase value settb=AVTB |
Pass the images of input video on to next video filter as multiple slices.
./ffmpeg -i in.avi -vf "slicify=32" out.avi |
The filter accepts the slice height as parameter. If the parameter is not specified it will use the default value of 16.
Adding this in the beginning of filter chains should make filtering faster due to better use of the memory cache.
Transpose rows with columns in the input video and optionally flip it.
It accepts a parameter representing an integer, which can assume the values:
L.R L.l . . -> . . l.r R.r |
L.R l.L . . -> . . l.r r.R |
L.R R.r . . -> . . l.r L.l |
L.R r.R . . -> . . l.r l.L |
Sharpen or blur the input video.
It accepts the following parameters: luma_msize_x:luma_msize_y:luma_amount:chroma_msize_x:chroma_msize_y:chroma_amount
Negative values for the amount will blur the input video, while positive values will sharpen. All parameters are optional and default to the equivalent of the string ’5:5:1.0:0:0:0.0’.
# Strong luma sharpen effect parameters
unsharp=7:7:2.5
# Strong blur of both luma and chroma parameters
unsharp=7:7:-2:7:7:-2
# Use the default values with
|
Flip the input video vertically.
./ffmpeg -i in.avi -vf "vflip" out.avi |
Deinterlace the input video (« yadif » means « yet another deinterlacing filter »).
It accepts the optional parameters: mode:parity.
mode specifies the interlacing mode to adopt, accepts one of the following values:
Default value is 0.
parity specifies the picture field parity assumed for the input interlaced video, accepts one of the following values:
Default value is -1. If interlacing is unknown or decoder does not export this information, top field first will be assumed.
Below is a description of the currently available video sources.
Buffer video frames, and make them available to the filter chain.
This source is mainly intended for a programmatic use, in particular through the interface defined in ‘libavfilter/vsrc_buffer.h’.
It accepts the following parameters: width:height:pix_fmt_string:timebase_num:timebase_den:sample_aspect_ratio_num:sample_aspect_ratio.den
All the parameters need to be explicitely defined.
Follows the list of the accepted parameters.
For example:
buffer=320:240:yuv410p:1:24:1:1 |
will instruct the source to accept video frames with size 320×240 and with format « yuv410p », assuming 1/24 as the timestamps timebase and square pixels (1:1 sample aspect ratio). Since the pixel format with name « yuv410p » corresponds to the number 6 (check the enum PixelFormat definition in ‘libavutil/pixfmt.h’), this example corresponds to:
buffer=320:240:6:1:24 |
Provide an uniformly colored input.
It accepts the following parameters: color:frame_size:frame_rate
Follows the description of the accepted parameters.
For example the following graph description will generate a red source with an opacity of 0.2, with size « qcif » and a frame rate of 10 frames per second, which will be overlayed over the source connected to the pad with identifier « in ».
"color=red@0.2:qcif:10 [color]; [in][color] overlay [out]" |
Read a video stream from a movie container.
It accepts the syntax: movie_name[:options] where movie_name is the name of the resource to read (not necessarily a file but also a device or a stream accessed through some protocol), and options is an optional sequence of key=value pairs, separated by « : ».
The description of the accepted options follows.
av_strtod so the numerical value may be suffixed by an IS postfix. Default value is « 0 ».
This filter allows to overlay a second video on top of main input of a filtergraph as shown in this graph:
input -----------> deltapts0 --> overlay --> output
^
|
movie --> scale--> deltapts1 -------+
|
Some examples follow:
# skip 3.2 seconds from the start of the avi file in.avi, and overlay it # on top of the input labelled as "in". movie=in.avi:seek_point=3.2, scale=180:-1, setpts=PTS-STARTPTS [movie]; [in] setpts=PTS-STARTPTS, [movie] overlay=16:16 [out] # read from a video4linux2 device, and overlay it on top of the input # labelled as "in" movie=/dev/video0:f=video4linux2, scale=180:-1, setpts=PTS-STARTPTS [movie]; [in] setpts=PTS-STARTPTS, [movie] overlay=16:16 [out] |
Null video source, never return images. It is mainly useful as a template and to be employed in analysis / debugging tools.
It accepts as optional parameter a string of the form width:height:timebase.
width and height specify the size of the configured source. The default values of width and height are respectively 352 and 288 (corresponding to the CIF size format).
timebase specifies an arithmetic expression representing a timebase. The expression can contain the constants « PI », « E », « PHI », « AVTB » (the default timebase), and defaults to the value « AVTB ».
Provide a frei0r source.
To enable compilation of this filter you need to install the frei0r header and configure FFmpeg with –enable-frei0r.
The source supports the syntax:
size:rate:src_name[{=|:}param1:param2:...:paramN]
|
size is the size of the video to generate, may be a string of the form widthxheight or a frame size abbreviation. rate is the rate of the video to generate, may be a string of the form num/den or a frame rate abbreviation. src_name is the name to the frei0r source to load. For more information regarding frei0r and how to set the parameters read the section « frei0r » (see frei0r) in the description of the video filters.
Some examples follow:
# generate a frei0r partik0l source with size 200x200 and framerate 10 # which is overlayed on the overlay filter main input frei0r_src=200x200:10:partik0l=1234 [overlay]; [in][overlay] overlay |
Below is a description of the currently available video sinks.
Null video sink, do absolutely nothing with the input video. It is mainly useful as a template and to be employed in analysis / debugging tools.
FFmpeg is able to dump metadata from media files into a simple UTF-8-encoded INI-like text file and then load it back using the metadata muxer/demuxer.
The file format is as follows:
A ffmetadata file might look like this:
;FFMETADATA1 title=bike\\shed ;this is a comment artist=FFmpeg troll team [CHAPTER] TIMEBASE=1/1000 START=0 #chapter ends at 0:01:00 END=60000 title=chapter \#1 [STREAM] title=multi\ line |
This document was generated by root on May 16, 2011 using texi2html 1.82.
Infos ubuntu/centos 