example_render.mp4
- Takes gopro hero *.mp4 parts
- renders overlay metadata, which is taken from .mp4 stream (gps track, spd, time, lat, long, distance)
- renders overlays over parts
- concats all parts to one track as .mp4
- Overlay frame rate can be changed - Default 2 FPS
- Lat/Long auto detect timezone for overlay
- Custom data can be rendered on a per frame basis
- utilizing nodejs-canvas and ffmpeg for most parts
- small codebase
- can be used in a CI/CD for auto ingressing of new files
- if required this app can also be put into a docker container for removing setup steps
git clone https://github.com/kc1r74p/autorender.gitnpm inpm run build
- Create following folders: in, out, final in the dist folder after the build
- Copy your .mp4 parts into the in directory
- Run
npm startin the main app dir - Logging will tell when it is done (or when your CPU fan stops going haywire)
- In the final directory you will find the result video
- The out dir is used as temp location for overlay and parts and should be cleaned after each run
- GPS Fix state not considered for track length or track rendering
- Each overlay frame gets rendered on the disk, this is required for ffmpeg but may be improved
- Concat and overlay apply can be proccessed by ffmpeg in one command to save render time instead of seperated runs
- Typings incomplete
- Where are the tests at ?
- Clunky logging, file path construction, ...
- gopro-telemetry which allows extraction of gopro data from video https://github.com/JuanIrache/gopro-telemetry
- ffmpeg packages which make it possible to do all required rendering work right out of nodejs
- canvas via nodejs which makes rendering an easy task while staying on server side