James Richardson
James Richardson
This would be a new feature.. its something that I think could be quite useful.
This does make sense - the file metadata (from ffprobe) is the one that doesn't come from GPS - its from an internal clock.. so it will drift over time,...
Hi! Thanks for your interest in the software! There's a lot going on here... and getting the best performance is a bit tricky. You might find that using `--show-ffmpeg` gives...
hi - yes - its as I said - docker version of ffmpeg doesn't support GPU. You can see this from the error: > Unknown encoder 'h264_nvenc' In any case,...
I do appreciate and agree that the error messages are hard to decipher! - It is a lot of work to interpret all the various error codes that all the...
I think perhaps I could make the docker image differently so that it will support GPUs.
This is now working in version 0.116.0 - there are some docs in [docs/docker.md](https://github.com/time4tea/gopro-dashboard-overlay/blob/main/docs/docker.md)
It should be supported for Windows - there is some information here: https://www.docker.com/blog/wsl-2-gpu-support-for-docker-desktop-on-nvidia-gpus/
OK... bit more debugging required. The image *does* work Linux, so there is a bit of different behaviour here. So far I have found that this gets a bit futher......
Starting the container to get a prompt ``` docker run --gpus all -it -v "$(pwd):/work" --entrypoint /bin/bash xx ``` and then getting ffmpeg to show the gpus ``` ffmpeg -vsync...