On 26-11-2019 10:53 pm, Michael Koch wrote:
Am 26.11.2019 um 17:48 schrieb Michael Koch:
Am 26.11.2019 um 17:32 schrieb Michael Koch:
Am 26.11.2019 um 14:26 schrieb Paul B Mahol:
I have a new example with testsrc2 and anoisesrc. There is no
input file
required for reproducing.
There are
Am 26.11.2019 um 17:48 schrieb Michael Koch:
Am 26.11.2019 um 17:32 schrieb Michael Koch:
Am 26.11.2019 um 14:26 schrieb Paul B Mahol:
I have a new example with testsrc2 and anoisesrc. There is no input
file
required for reproducing.
There are two graphs: The first one uses signalstats and
Am 26.11.2019 um 17:32 schrieb Michael Koch:
Am 26.11.2019 um 14:26 schrieb Paul B Mahol:
I have a new example with testsrc2 and anoisesrc. There is no input
file
required for reproducing.
There are two graphs: The first one uses signalstats and drawgraph, and
the second one uses astats and
Am 26.11.2019 um 14:26 schrieb Paul B Mahol:
I have a new example with testsrc2 and anoisesrc. There is no input file
required for reproducing.
There are two graphs: The first one uses signalstats and drawgraph, and
the second one uses astats and adrawgraph. The problem is that the two
graphs
On 11/26/19, Michael Koch wrote:
>
>>> Thanks for your suggestion. Adding -r 25 does indeed solve the problem.
>>> Although I don't understand why it is required. The input framerate is
>>> 25 and it's detected correctly when I use the simpler filter chain.
>>>
>> Ah, I know why this happens, you
Thanks for your suggestion. Adding -r 25 does indeed solve the problem.
Although I don't understand why it is required. The input framerate is
25 and it's detected correctly when I use the simpler filter chain.
Ah, I know why this happens, you need to use settb=1/FPS filter after vstack.
This
On 11/26/19, Michael Koch wrote:
> Am 26.11.2019 um 09:55 schrieb Carl Eugen Hoyos:
>>
>>> Am 26.11.2019 um 09:40 schrieb Michael Koch
>>> :
>>>
Am 26.11.2019 um 07:11 schrieb Carl Eugen Hoyos:
> Am 25.11.2019 um 23:36 schrieb Michael Koch
> :
>
> [mp4 @
Am 26.11.2019 um 09:55 schrieb Carl Eugen Hoyos:
Am 26.11.2019 um 09:40 schrieb Michael Koch :
Am 26.11.2019 um 07:11 schrieb Carl Eugen Hoyos:
Am 25.11.2019 um 23:36 schrieb Michael Koch :
[mp4 @ 006288c0] Frame rate very high for a muxer not efficiently
supporting it.
Please
> Am 26.11.2019 um 09:40 schrieb Michael Koch :
>
>> Am 26.11.2019 um 07:11 schrieb Carl Eugen Hoyos:
>>
>>> Am 25.11.2019 um 23:36 schrieb Michael Koch :
>>>
>>> [mp4 @ 006288c0] Frame rate very high for a muxer not efficiently
>>> supporting it.
>>> Please consider specifying a
Am 26.11.2019 um 07:11 schrieb Carl Eugen Hoyos:
Am 25.11.2019 um 23:36 schrieb Michael Koch :
[mp4 @ 006288c0] Frame rate very high for a muxer not efficiently
supporting it.
Please consider specifying a lower framerate, a different muxer
Did you see this?
I did not read the whole
> Am 25.11.2019 um 23:36 schrieb Michael Koch :
>
> [mp4 @ 006288c0] Frame rate very high for a muxer not efficiently
> supporting it.
> Please consider specifying a lower framerate, a different muxer
Did you see this?
I did not read the whole thread but if your issue is a broken
Am 25.11.2019 um 23:36 schrieb Michael Koch:
Am 25.11.2019 um 22:46 schrieb Paul B Mahol:
On 11/25/19, Michael Koch wrote:
Am 25.11.2019 um 12:04 schrieb Paul B Mahol:
On 11/25/19, Michael Koch wrote:
Am 25.11.2019 um 00:08 schrieb Michael Koch:
I just found the solution to this problem
Am 25.11.2019 um 22:46 schrieb Paul B Mahol:
On 11/25/19, Michael Koch wrote:
Am 25.11.2019 um 12:04 schrieb Paul B Mahol:
On 11/25/19, Michael Koch wrote:
Am 25.11.2019 um 00:08 schrieb Michael Koch:
I just found the solution to this problem myself:
On 11/25/19, Michael Koch wrote:
> Am 25.11.2019 um 12:04 schrieb Paul B Mahol:
>> On 11/25/19, Michael Koch wrote:
>>> Am 25.11.2019 um 00:08 schrieb Michael Koch:
I just found the solution to this problem myself:
astats=metadata=1:reset=1,adrawgraph=m1=lavfi.astats.1.RMS_level
Am 25.11.2019 um 12:04 schrieb Paul B Mahol:
On 11/25/19, Michael Koch wrote:
Am 25.11.2019 um 00:08 schrieb Michael Koch:
I just found the solution to this problem myself:
astats=metadata=1:reset=1,adrawgraph=m1=lavfi.astats.1.RMS_level
The underline character is missing in the
On 11/25/19, Michael Koch wrote:
> Am 25.11.2019 um 00:08 schrieb Michael Koch:
>>
>> I just found the solution to this problem myself:
>> astats=metadata=1:reset=1,adrawgraph=m1=lavfi.astats.1.RMS_level
>>
>> The underline character is missing in the documentation, where the
>> option is called
Am 25.11.2019 um 00:08 schrieb Michael Koch:
I just found the solution to this problem myself:
astats=metadata=1:reset=1,adrawgraph=m1=lavfi.astats.1.RMS_level
The underline character is missing in the documentation, where the
option is called "RMS level dB". Same problem for most other
Am 24.11.2019 um 22:17 schrieb Michael Koch:
Hello all,
I'd like to draw a curve of the RMS audio level with the following
command line. The problem is that the output is a black video and no
curve is visible.
c://ffmpeg/ffmpeg -i P1000479.mov -lavfi astats,adrawgraph=
m1="lavfi.astats.RMS
Hello all,
I'd like to draw a curve of the RMS audio level with the following
command line. The problem is that the output is a black video and no
curve is visible.
c://ffmpeg/ffmpeg -i P1000479.mov -lavfi astats,adrawgraph=
m1="lavfi.astats.RMS level
19 matches
Mail list logo
