Using that version of the Raspberry Pi operating system it’s actually quite easy to get Owncast running in a hardware accelerated fashion. Use the previous version of the OS by downloading it, unzipping it, and using the Raspberry Pi Imager to save it to your SD card for installation.

Note: The most recent version of the Raspberry Pi OS has a bug with the OpenMax codec. If you have Intel integrated graphics you may be able to use it using VA-API. There’s likely a lot of information already online, so please do your research. Any questions you have about your particular hardware should be directed to your hardware manufacturer or whoever provides the drivers and libraries to utilize it. Very little of what is required to get your hardware working has anything to do with Owncast.It simply means Owncast believes that codec to be available. Just because a specific hardware accelerated codec shows in the Owncast admin does not mean your machine is configured to support it.Most people won’t be able to take advantage of this unless you’re running your own hardware.You have a copy of ffmpeg that is version 4.1.5 or greater that is specifically built to utilize these drivers and libraries.You installed and configured any drivers and libraries needed to take advantage of your hardware.

You have compatible hardware and have direct access to it.

You are not running on a VPS provided to you by a hosting provider, as shared virtual servers do not allow for direct access to hardware.

RequirementsĪll four of these things need to be true to support hardware accelerated encoding with Owncast. Outside of this document you are mostly on your own. It is unlikely that any specific support can be provided to help you, as it very much depends on the hardware you have and the software, drivers and versions of libraries you have installed.

H264_omx