jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2016-10-02 22:26:37 UTC

Browse source
This commit is contained in:
Travis CI 2016-10-02 22:26:37 +00:00
parent 1021714df4
commit 2fd680bc8b
23 changed files with 44 additions and 44 deletions
Download patch file Download diff file Expand all files Collapse all files

16
components/ffmpeg/index.html
View file

@ -89,10 +89,10 @@
<hr class="divider">
<p>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.</p>
<p>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.</p>
<p class="note">
You need a <code class="highlighter-rouge">ffmpeg</code> 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 <a href="http://www.ffmpeg.org/">FFmpeg</a> website.
You need the <code class="highlighter-rouge">ffmpeg</code> binary in your system path. On Debian 8 or Raspbian (Jessie) you can install it from <a href="https://backports.debian.org/Instructions/">debian-backports</a>. 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 <a href="http://www.ffmpeg.org/">FFmpeg</a> website.
</p>
<p>To set it up, add the following information to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
@ -106,25 +106,25 @@ You need a <code class="highlighter-rouge">ffmpeg</code> binary in your system p
<p>Configuration variables:</p>
<ul>
<li><strong>ffmpeg_bin</strong> (<em>Optional</em>): Default ‘ffmpeg’. Set the ffmpeg binary.</li>
<li><strong>ffmpeg_bin</strong> (<em>Optional</em>): Default ‘ffmpeg’. The name or path to the <code class="highlighter-rouge">ffmpeg</code> binary.</li>
<li><strong>run_test</strong> (<em>Optional</em>): Default True. Check if <code class="highlighter-rouge">input</code> is usable by ffmpeg.</li>
</ul>
<h3><a class="title-link" name="troubleshooting" href="#troubleshooting"></a> Troubleshooting</h3>
<p>In most of case, <code class="highlighter-rouge">ffmpeg</code> 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 <code class="highlighter-rouge">ffmpeg</code>. Per default <code class="highlighter-rouge">ffmpeg</code> use 5 seconds to detect all options or abort.</p>
<p>In most cases, <code class="highlighter-rouge">ffmpeg</code> 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 <code class="highlighter-rouge">ffmpeg</code> out.</p>
<p>First check, if your stream playable by <code class="highlighter-rouge">ffmpeg</code> with (use option <code class="highlighter-rouge">-an</code> or <code class="highlighter-rouge">-vn</code> to disable video or audio stream):</p>
<p>First check that your stream is playable by <code class="highlighter-rouge">ffmpeg</code> outside of Home Assistant with (use option <code class="highlighter-rouge">-an</code> or <code class="highlighter-rouge">-vn</code> to disable video or audio stream):</p>
<div class="highlighter-rouge"><pre class="highlight"><code>$ ffmpeg -i INPUT -an -f null -
</code></pre>
</div>
<p>Now you can see what going wrong. Following list could be help to solve your trouble:</p>
<p>Now you should be able to see what is going wrong. The following list contains some common problems and solutions:</p>
<ul>
<li><code class="highlighter-rouge">[rtsp @ ...] UDP timeout, retrying with TCP</code>: You need to set RTSP transport in the configuration with: <code class="highlighter-rouge">input: -rtsp_transport tcp -i INPUT</code></li>
<li><code class="highlighter-rouge">[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size</code>: FFmpeg need more data or time for autodetect. You can set the <code class="highlighter-rouge">analyzeduration</code> and/or <code class="highlighter-rouge">probesize</code> option, play with this value. If you know the needed value you can set it with: <code class="highlighter-rouge">input: -analyzeduration xy -probesize xy -i INPUT</code>. More information about that can be found on <a href="https://www.ffmpeg.org/ffmpeg-formats.html#Description">FFmpeg</a>.</li>
<li><code class="highlighter-rouge">[rtsp @ ...] UDP timeout, retrying with TCP</code>: You need to set an RTSP transport in the configuration with: <code class="highlighter-rouge">input: -rtsp_transport tcp -i INPUT</code></li>
<li><code class="highlighter-rouge">[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size</code>: FFmpeg needs more data or time for autodetection (the default is 5 seconds). You can set the <code class="highlighter-rouge">analyzeduration</code> and/or <code class="highlighter-rouge">probesize</code> options to experiment with giving FFmpeg more leeway. If you find the needed value, you can set it with: <code class="highlighter-rouge">input: -analyzeduration xy -probesize xy -i INPUT</code>. More information about this can be found <a href="https://www.ffmpeg.org/ffmpeg-formats.html#Description">here</a>.</li>
</ul>