FFmpeg optimizations and GPU support #2352
Replies: 2 comments
-
|
First, let me say, that is a fantastic image quality! I have had a few others test accelerated encoding, but you are probably the first to test this on an Nvidia GPU. The Raspberry Pi can also do GPU accelerated encoding, but the resolution was always limited to FHD [1920x1080] in my testing. I can add the Nvidia |
Beta Was this translation helpful? Give feedback.
-
|
Merged #2355 with the new Nvidia and AMD options. These are not extensive changes, just basic options. I updated the timelapse wiki to include links related to upgrading ffmpeg. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Background
I recently lifted my indi-allsky installation into my homelab workstation from my Raspberry Pi 5 and converted it into a remote indiserver setup. Since my workstation has a GPU, I wanted to try playing around with the FFmpeg options to see if I could improve the timelapse processing, and got some good results.
Timelapse Settings
FFmpeg upgrade
I am on Debian 12, and the default installation of ffmpeg is quite old at 5.1.7, so I installed jellyfin-ffmpeg instead and changed the symlink to point to it:
Indi Allsky Settings
FFMPEG Framerate: 30
FFMPEG Bitrate: 40000k
FFMPEG Scaling: No scaling
FFMPEG Codec: x264
FFMPEG Extra Options:
I found out that if I include
-c:v h264_nvenc, it will respect the precedence and use the GPU accelerated encoder instead of the default that gets set by indi. Some of the other options were just trial and error to improve the playback and reduce the flickering at the beginning and end of the timelapse.Results
Specifications
Beta Was this translation helpful? Give feedback.
All reactions