Yes. Confirmed. Sorry about that, I had an issue with one shell using a
cached ffmpeg binary, while the other one was using the fresh build. My bad.
On Sun, Jan 12, 2020 at 4:30 PM Gyan wrote:
>
>
> On 12-01-2020 08:48 pm, Yellow Penguin wrote:
> > Thanks. That solved my issue, but I should note
On 12-01-2020 08:48 pm, Yellow Penguin wrote:
Thanks. That solved my issue, but I should note that you still can't use
'oh' in the expression for 'ow'. I can only do it the other way around. Ie,
"crop=100:ow:0:0" works fine, but "crop=oh:100:0:0" still gives me the same
error. That also happens
Thanks. That solved my issue, but I should note that you still can't use
'oh' in the expression for 'ow'. I can only do it the other way around. Ie,
"crop=100:ow:0:0" works fine, but "crop=oh:100:0:0" still gives me the same
error. That also happens if I explicitly name the options, and change the
On 12-01-2020 07:01 pm, Yellow Penguin wrote:
It says in the docs for the "crop" filter, you can use "out_w" in "out_h"
and vice versa, but I can't get that to work. Anyone know if this is
actually not possible and a mistake in the docs? When I use the command
'ffmpeg -i test.mp4 -vf "crop=out_
It says in the docs for the "crop" filter, you can use "out_w" in "out_h"
and vice versa, but I can't get that to work. Anyone know if this is
actually not possible and a mistake in the docs? When I use the command
'ffmpeg -i test.mp4 -vf "crop=out_h:100:0:0" testout.mp4' I get the message
'Error w
