On 8/12/2017 8:28 PM, Reindl Harald [via FFmpeg-users] wrote:
>
> Am 13.08.2017 um 02:23 schrieb Ted Lum:
> > I'm sure there is only one copy of all the executables. They are
> > actually deployed to /root/bin so they're kept highly isolated from the
> > rest of the system.
> >
> > So, we have:
> >
Am 13.08.2017 um 02:23 schrieb Ted Lum:
I'm sure there is only one copy of all the executables. They are
actually deployed to /root/bin so they're kept highly isolated from the
rest of the system.
So, we have:
[root@san1srvp01 ~]# which ffmpeg
/root/bin/ffmpeg
jesus christ don't run *espe
On 8/12/2017 4:27 PM, Moritz Barsnick wrote:
On Fri, Aug 11, 2017 at 16:27:16 -0700, tlum wrote:
Wow, how did you manage to compose this email? See here, this is what
the users get:
http://ffmpeg.org/pipermail/ffmpeg-user/2017-August/036951.html
I can see it here though:
http://www.ffmpeg-archi
Am 12.08.2017 um 22:27 schrieb Moritz Barsnick:
On Fri, Aug 11, 2017 at 16:27:16 -0700, tlum wrote:
I'm having trouble adding OpenJPEG to my ffmpeg build. I'm doing a static
build, still I'm getting:
ffmpeg: error while loading shared libraries: libopenjp2.so.7: cannot open
shared object fil
Mettavihari D writes:
> Greetings
>
> I note you did not have a reply to this long and exhaustive mail
>
> if you have solved it I would be happy to know the solution
I don´t have a solution with ffmpeg yet, so I´m planning to write
something myself that figures out which snippets to get from th
On Thu, Aug 03, 2017 at 13:59:13 +0530, akash kulkarni wrote:
> ffmpeg -i input -c:v copy -c:a aac -b:a 256k output.mp4
>
> it gaves me error saying
> [aac @ 02a802e0]
> The encoder 'aac' is experimental but experimental codecs
> are not enabled, add '-strict -2' if you wan
On Thu, Aug 03, 2017 at 05:10:20 -0400, Karen Norton wrote:
> would hardly be noticeable. From everything I read about libvo_aacenc I
> think for most purposes it's pretty close to aac so I don't know that you
> would notice much difference if you had to stay with that encoder.
Recent ffmpeg has a
On Fri, Aug 11, 2017 at 16:27:16 -0700, tlum wrote:
Wow, how did you manage to compose this email? See here, this is what
the users get:
http://ffmpeg.org/pipermail/ffmpeg-user/2017-August/036951.html
I can see it here though:
http://www.ffmpeg-archive.org/ffmpeg-built-static-yet-quot-libopenjp2-
On Thu, Aug 10, 2017 at 09:50:48 -0700, James Girotti wrote:
> > > Supported hwaccels: vdpau vaapi cuvid " same time if i request
> > > "/usr/local/bin/ffmpeg -decoders |grep -i h264 " i get this result:
> > >
> > > ffmpeg version N-86054-g2171dfa Copyright (c) 2000-2017 the FFmpeg
> > > developers
On Tue, Aug 08, 2017 at 08:43:27 +0200, Jon bae wrote:
> The problem is now that the both streams have a little delay from ~1
> second. I found out, that when I would encode both stream new and send them
> via the *tee *output from one ffmpeg instance it would be sync. But I don't
> want to transco
On Tue, Aug 08, 2017 at 20:54:17 +0300, Daniel wrote:
> i get the following error : "Unrecognized hwaccel: h264_cuvid.
> Supported hwaccels: vdpau vaapi cuvid " same time if i request
> "/usr/local/bin/ffmpeg -decoders |grep -i h264 " i get this result:
Well, since you are trying to use a hwaccel
On Sat, Aug 12, 2017 at 12:15:01 +0530, Mettavihari D wrote:
> if you have solved it I would be happy to know the solution
> If not try to put -report into the command line.
>
> ffmpeg -n -loglevel 8 -report -i http://example.com/foo.m3u8 -codec
> copy -t 00:10:00 -f mpegts example
>
> and post t
12 matches
Mail list logo
