Humm, I’ll admit that I didn’t do a lot of tests with 2D.
The goal of the Height parameters was mostly to reduce VR video size.
But for small videos (ex. 720x404), it might also help to increase the size to have more motion ‘sensors’.
The ffmpegfilter parameters accept 3 predefined values:
-
VRLeft: keep only left eye
-filter:v crop=in_w/2:in_h:0:0,scale=-1:{HEIGHT} -
VRMosaic: keep left eye, and add a smaller -20 pitch and -55 pitch projections to the right
-filter_complex [0:v]crop=in_w/2:in_h:0:0,scale=-1:{HEIGHT}[A]; [0:v]v360=input=he:in_stereo=sbs:pitch=-20:yaw=0:roll=0:output=flat:d_fov=90:w={HEIGHT}/2:h={HEIGHT}/2[B1]; [0:v]v360=input=he:in_stereo=sbs:pitch=-55:yaw=0:roll=0:output=flat:d_fov=90:w={HEIGHT}/2:h={HEIGHT}/2[B2]; [B1][B2]vstack=inputs=2[B]; [A][B]hstack=inputs=2(I added newlines to make the ffmpeg ‘graph’ more clear.
-
2D: only scale
-filter:v \"scale=-1:{HEIGHT}\"
But it also accepts any ffmpeg filter directly (in that case, if you don’t include {HEIGHT} in your filter, it will simply ignore Height parameter, ).
I did a quick test on a 720x404 video with:
--ffmpegfilter=-filter:v scale=-1:-1 (i.e. no scaling)
It worked, and the rest of the application/plugin seems to work fine too, even if it was not divisible by 16. I will probably remove the ‘divisible by 16’ check in the application in the next release.
If you need to change the size, and one of the dimensions is not divisible by 2 (i.e. your first test 3641x2048), you could specify the width and height:
--ffmpegfilter=-filter:v scale=3640:2048