On 04/09/2020 05:16 AM, Nicolas George wrote:
Mark Filipak (12020-04-08):
Try this, Ben:
ffmpeg -loglevel warning
Ben, do not follow that advice: you will not get help with reduced log
level.
Regards,
Ben, by all means, follow Nicolas's recommendation.
I gave you information on analyzeduration & probesize. Did you try them? Did
they help?
On 04/08/2020 10:01 PM, Mark Filipak wrote:
> On 04/08/2020 06:47 PM, Ben Edwards wrote:
>> Now I could increase analyzeduration & probesize, but no idea to what.
>>
>> Any help greatly apreciated.
>>
>> Ben
>
> Try this, Ben:
>
> ffmpeg -loglevel warning -analyzeduration 5000000000 -probesize 5000000000 -i
input.mp4 -flags
> +global_header -vcodec copy -acodec libmp3lame -ar
> > 44100 -b:a 128k out.mp4
>
> Reference:
> https://ffmpeg.org/ffmpeg-all.html
>
> analyzeduration integer (input)
>
> Specify how many microseconds are analyzed to probe the input. A higher
value will enable
> detecting more accurate information, but will increase latency. It defaults
to 5,000,000
> microseconds = 5 seconds
>
> probesize integer (input)
>
> Set probing size in bytes, i.e. the size of the data to analyze to get
stream information. A
> higher value will enable detecting more information in case it is dispersed
into the stream, but
> will increase latency. Must be an integer not lesser than 32. It is 5000000
by default.
>
> HTH - Mark.
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
