From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/tvheadend: select libvpx/x264 for transcoding support
Date: Fri, 10 Jun 2016 00:15:20 +0200 [thread overview]
Message-ID: <20160610001520.62c9432e@free-electrons.com> (raw)
In-Reply-To: <1463505862-3783-1-git-send-email-bernd.kuhls@t-online.de>
Hello,
On Tue, 17 May 2016 19:24:22 +0200, Bernd Kuhls wrote:
> ffmpeg needs libvpx and x264 to support transcoding.
>
> Fixes this error message from tvheadend log:
> 2016-05-14 22:52:21.962 [ ERROR]:transcode: 0006: Unable to find libx264 encoder
> 2016-05-14 22:52:21.962 [ INFO]:transcode: 0006: 1:H264 ==> Passthrough
> 2016-05-14 22:52:21.963 [ INFO]:transcode: 0006: 2:MPEG2AUDIO ==> AAC (aac)
>
> or
>
> 2016-05-14 22:58:01.529 [ ERROR]:transcode: 0009: Unable to find libvpx encoder
> 2016-05-14 22:58:01.529 [ INFO]:transcode: 0009: 1:H264 ==> Passthrough
> 2016-05-14 22:58:01.529 [ INFO]:transcode: 0009: 2:MPEG2AUDIO ==> VORBIS (libvorbis)
>
> With this patch transcoding is logged like this:
>
> 2016-05-16 20:14:56.515 [ INFO]:transcode: 0004: 1:TELETEXT ==> Filtered
> 2016-05-16 20:14:56.516 [ INFO]:transcode: 0004: 2:MPEG2VIDEO 720x576 ==> H264 640x512 (libx264)
> 2016-05-16 20:14:56.516 [ INFO]:transcode: 0004: 3:MPEG2AUDIO ==> AAC (aac)
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/tvheadend/Config.in | 2 ++
> 1 file changed, 2 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-06-09 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 17:24 [Buildroot] [PATCH 1/1] package/tvheadend: select libvpx/x264 for transcoding support Bernd Kuhls
2016-06-09 21:01 ` Yann E. MORIN
2016-06-09 22:15 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160610001520.62c9432e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox