Modified Owncast for RKMPP hardware acceleration (RK3588) successfully, what next?

[okazaki0yumemi1]

Hello!
I have Orange Pi 5 Plus (RK3588 system-on-a-chip) SBC as a home server with Owncast behind reverse proxy. I am also very new to open-source community, so I have no idea what I should and should not do with code.

The current 0.1.3dev version have no support for RKMPP encoder (hardware RK3588 encoder), but I managed to enable it by adding few lines to owncast/core/transcoder/codecs.go file.

Of course, you need to compile FFMPEG with RKMPP support & make sure you have /dev/rga and /dev/mpp_service.

I ran a few streams, everything was fine (no dropped frames, no lags and other errors during 2 hour stream). Input stream was:
Nvenc H.264, 1920x1080 @ 60 FPS and 4Mbps bitrate
output was set to: 1280x720 @ 50FPS and 2Mbps bitrate

I want to help RK3588 users with enabling HW acceleration in Owncast. Should I write instructions for enabling RKMPP in my Github, or I can just fork Owncast project & maintain RKMPP support for as long as I can? What is the best way to help Owncast?

[gabek]

Yeah, definitely, it sounds like you're half way there. Thanks for looking into it!

I'm not sure how much you did with codecs.go, but you probably saw the pattern of how other codecs are added there.

This is a bit of bad timing, since there's currently a PR up for some changes on this front. So any changes you make will have to be forked off that, but that should be no big deal. You can also look at #3476 as a model of how to create a new codec model from scratch.

But if you fork the repo. Change to the gek/ffmpeg-6 branch, create your new branch from that, you can create the new codec in codec.go and create the test alongside of its respective _test.go file, you can create a PR against the gek/ffmpeg-6 branch.

I don't have an Orange Pi myself to test, but maybe I can get my hands on one.