Hi,
Here is my case:
I have a MPEG-TS video file with one video and one audio stream and i am
trying to create a direct video convert with adding a DVBSUB stream inside
it. My original subs file is a stl file.
After many workarounds i finally managed to add the DVBSUB stream, after
converting t
Hi, there,
Here is what the compiler said:
{
In file include from libavformat/os_support.h:112:0
From libavformat/os_support.c:29:
libavformat/os_support.c: in function 'ff_gai_strerror':
libavformat/os_support.c:230:10 error: 'ERROR_NOT_ENOUGH_MEMORY'
und
Hi
Where can i find the options & metadata for the webvtt & dvbsub encoders
Thank you!
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffm
Hello,
I would like to show an audio meter from an audio file (something like what
edit software display
or like Audacity display)
I try the showvolume filter, but the result is not what i would like to
have.
My command line :
"C:\ffmpeg-20180329-af043b8-win64-static\bin\ffmpeg.exe" -i
"D:\RefSo
On 3/30/18, Martin Vignali wrote:
> Hello,
>
> I would like to show an audio meter from an audio file (something like what
> edit software display
> or like Audacity display)
>
> I try the showvolume filter, but the result is not what i would like to
> have.
>
> My command line :
> "C:\ffmpeg-2018
> >
> > Is there another filter for that ?
>
> Only ebur128 meter.
>
> The peak meter, is just that peak, if you want more dynamics incrase
> rate option to 60fps.
> Default 25 is very low :)
>
> I'm not happy with rms option, so if you can improve this and add
> others meter that would be great.
>
When trying to build the latest Git build of FFmpeg with libaom enabled, I'm
getting the following error:
CC libavcodec/libaomdec.o
In file included from
./libavutil/common.h:105:0
,
from
libavcodec/libaomdec.c:29
:
./config.h:38:0:
warning:
"ARCH_X86" redefined
#def
On Thu, 11 Jan 2018, Frank Tetzel wrote:
The thing I am trying to achieve is a compromise between these two
extremes, eg. a method which gives less cropping at the LH & RH
picture edges for the price of a little padding above and below the
picture. I'm presuming this (ideally) involves scaling