diff --git a/atom.xml b/atom.xml index bb78cc87dc..b413ededd0 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@
It allow other Home-Assistant components to process video/audio streams. It need a ffmpeg binary in your system path. It support all ffmpeg version since 3.0.0. If you have a older version, please update.
+The FFmpeg component allows other Home Assistant components to process video and audio streams. This component supports all FFmpeg versions since 3.0.0; if you have a older version, please update.
-You need a ffmpeg
binary in your system path. On Debain 8 or Raspbian (Jessie) you can install it from backports. If you want Hardware support on a Raspberry Pi you need to build from source by yourself. Windows binary are avilable on the FFmpeg website.
+You need the ffmpeg
binary in your system path. On Debian 8 or Raspbian (Jessie) you can install it from debian-backports. If you want hardware acceleration support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are avilable on the FFmpeg website.
To set it up, add the following information to your configuration.yaml
file:
ffmpeg
binary in your system p
Configuration variables:
ffmpeg
binary.input
is usable by ffmpeg.In most of case, ffmpeg
autodetect all needed options to read a video/audio stream or file. But it is possible in rare cases that’s needed to set a option to help ffmpeg
. Per default ffmpeg
use 5 seconds to detect all options or abort.
In most cases, ffmpeg
automatically detects all needed options to read a video or audio stream or file. But it is possible in rare cases that you will need to set options to help ffmpeg
out.
First check, if your stream playable by ffmpeg
with (use option -an
or -vn
to disable video or audio stream):
First check that your stream is playable by ffmpeg
outside of Home Assistant with (use option -an
or -vn
to disable video or audio stream):
$ ffmpeg -i INPUT -an -f null -
Now you can see what going wrong. Following list could be help to solve your trouble:
+Now you should be able to see what is going wrong. The following list contains some common problems and solutions:
[rtsp @ ...] UDP timeout, retrying with TCP
: You need to set RTSP transport in the configuration with: input: -rtsp_transport tcp -i INPUT
[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size
: FFmpeg need more data or time for autodetect. You can set the analyzeduration
and/or probesize
option, play with this value. If you know the needed value you can set it with: input: -analyzeduration xy -probesize xy -i INPUT
. More information about that can be found on FFmpeg.[rtsp @ ...] UDP timeout, retrying with TCP
: You need to set an RTSP transport in the configuration with: input: -rtsp_transport tcp -i INPUT
[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size
: FFmpeg needs more data or time for autodetection (the default is 5 seconds). You can set the analyzeduration
and/or probesize
options to experiment with giving FFmpeg more leeway. If you find the needed value, you can set it with: input: -analyzeduration xy -probesize xy -i INPUT
. More information about this can be found here.