Updated to newest version but still has errors, different from before
ffmpeg version 4.2.3-static https://johnvansickle.com/ffmpeg/ Copyright (c)
2000-2020 the FFmpeg developers
built with gcc 8 (Debian 8.3.0-6)
configuration: --enable-gpl --enable-version3 --enable-static
--disable-debug
"-probesize 100M -analyzeduration 100M " these options are from others'
suggestions but they won't work.
I will try the latest version.
Thanks,
Ming
On Tue, Jun 9, 2020 at 3:13 PM Moritz Barsnick wrote:
> On Tue, Jun 09, 2020 at 14:00:56 -0700, Ming Tu wrote:
> > ffmpeg version
On Tue, Jun 09, 2020 at 14:00:56 -0700, Ming Tu wrote:
> ffmpeg version 3.2.14-1~deb9u1 Copyright (c) 2000-2019 the FFmpeg developers
This version is (functionally) almost ancient. Could you please retry
with latest git? You can grab a static binary here:
https://johnvansickle.com/ffmpeg/
(Left
Hi,
I noticed the different outputs of ffprobe for file input and binary data
input.
ffprobe -v error -show_streams -print_format xml Y001BAQ9k3SU-140.mp4
Output:
cat
Thank you.
My apologies for not going to the latest before posting here. I should know
this by now. I even have targets in the makefile for building the git
version.
nonfree - left from an experiment with AAC, perhaps? Definitely needed to
go.
cpudetect - not sure why I thought I need it. Perhaps
Am Di., 9. Juni 2020 um 16:01 Uhr schrieb Michael Kohne via
ffmpeg-user :
> I'm pretty sure the extra-ldflags have to do with strange layout
> choices in my build tree.
> If you properly install the libraries into your system, I don't think that
> it is needed. I don't do so because I'm afraid of
Hi,
I asked the same question on stackoverflow but no one answers. So I come
here and hope it can be answered.
The question is:
https://stackoverflow.com/questions/62226122/ffmpeg-ffprobe-different-outputs-for-file-input-and-binary-data-input
Thanks,
Ming
Am Di., 9. Juni 2020 um 21:11 Uhr schrieb Ming Tu :
>
> Hi,
>
> I asked the same question on stackoverflow but no one answers. So I come
> here and hope it can be answered.
Please ask your question here on the mailing list, don't forget
to provide the command line(s) you tested including the
Hi Nuno,
On Tue, Jun 09, 2020 at 09:04:53 +0100, Nuno Santos wrote:
> > Oh, you mean using the libav* libraries? Then you're basically on the
> > wrong mailing list.
>
> What’s the correct mailing list for this?
It's pretty clearly outlined here:
On Mon, Jun 08, 2020 at 22:28:55 +0100, Nuno Santos wrote:
> Sorry if this is a basic question, but how does one know the
> available the options for the h264_videotoolbox?
Usually with something like
$ ffmpeg -h encoder=h264_videotoolbox
> I want to set them programmatically and not via ffmpeg
Moritz,
Thanks for your reply.
> On 9 Jun 2020, at 09:00, Moritz Barsnick wrote:
>
> On Mon, Jun 08, 2020 at 22:28:55 +0100, Nuno Santos wrote:
>> Sorry if this is a basic question, but how does one know the
>> available the options for the h264_videotoolbox?
>
> Usually with something like
>
Moritz,
> On 9 Jun 2020, at 10:24, Moritz Barsnick wrote:
>
> Hi Nuno,
>
> On Tue, Jun 09, 2020 at 09:04:53 +0100, Nuno Santos wrote:
>>> Oh, you mean using the libav* libraries? Then you're basically on the
>>> wrong mailing list.
>>
>> What’s the correct mailing list for this?
>
> It's
12 matches
Mail list logo
