hn-88 / ocvwarp Goto Github PK

Warping images and videos for planetarium fulldome display using OpenCV

License: MIT License

C++ 34.08% C 65.92%

planetarium fulldome opencv cpp image-processing 360-video equirectanguar-projection fisheye-image

ocvwarp's Introduction

OCVWarp

Warping images and videos for planetarium fulldome display using OpenCV. Windows and Linux binaries are available in Releases. The wiki has some more information.

In case you want to build your own binaries, if OpenCV and CMake are installed on your system, instructions for building:

cd build
cmake ..
make OCVWarp.bin

Only OCVWarp.bin is strictly necessary. If desired,

make OCVWarpNorth.bin
make getfourcc.bin

Initial behaviour and parameters are set using OCVWarp.ini in the build folder. Please see transformtype.txt for supported transforms.

A file open dialog asks you for the input file. The output file is put in the same directory, with F.avi appended to the input filename. The codec used for the output is the same codec as for the input if available on your system, or as chosen in the ini file. (If the input file's codec is not available, the output is saved as an uncompressed avi, which can quickly become huge.)

Keyboard commands are

ESC, x or X to exit
u, + or =   to increase angley by 1 degree - the angle seen vertically in output
m, - or _   to decrease angley by 1 degree 
U           to increase angley by 10 degrees
M           to decrease angley by 10 degrees
k, ] or }   to increase anglex by 1 degree - the angle seen horizontally in output
h, [ or {   to decrease anglex by 1 degree - the angle seen horizontally in output
K           to increase anglex by 10 degrees
H           to decrease anglex by 10 degrees
d or D      to toggle display of warped file. Turning off display marginally increases processing speed.

ocvwarp's People

Contributors

Stargazers

Watchers

ocvwarp's Issues

language shown as mercury in github

Maybe can fix using the technique at https://dev.to/katkelly/changing-your-repo-s-language-in-github-5gjo

bottom 10 pixels in transformtype=5

Seem to be discontinuous with the pixels above. Check map file.

support for single frame input and output

Currently, single frame input seems to work OK on Linux, to be tested on Windows. Output filename like output.mp4 works, from which the single frame can be extracted with avidemux.

generate the ini file with gui

If we want support for multiple still image files + position each of them individually + animate each of them individually, it may be easier to enter all the details using a ui?

explore options to use stills as input

We could possibly add some parameters to ini file like
fps
number of frames
which would decide how long the video needs to be, instead of outputting just a single frame.

Of course, this can be worked around using avisynth, so this is just an enhancement.

issue

Submitter: HN
Testing gitreports.com

bottom ten pixels in transformtype=5

Bottom ten pixels are black. This seems to be due to clipping in transformtype=1 When transformtype=1 mapping is changed to allow r<=1.01, the extra pixels are not continuous.

new issue created with ifttt

This is the body of the message

via Email

January 16, 2021 at 09:08PM

add support for animating anglex and angley

Currently anglex and angley - the viewing angles inside the 3d scene - can be varied on the fly using keyboard shortcuts. It would be easier to use if we can give initial anglex/y and final anglex/y, with a spline to ramp up rotation ... or at least constant velocity rotation.