If you’ve been following my blog post series on the development of my ever so useful cat cam, powered by a Raspberry Pi, you’ll know I’ve made several attempts at a more stable and scalable streaming solution for my Cat Cam. As it stands today, I’ve been using Motion. While it’s a decent tool, Bandwidth has been my primary concern and I’d like to be able to stream real-time without sucking up what measly bits my ISP gives me if more than a few folks decide to show interest.
So far we’ve tried
ffserver and that turned out exactly how you probably thought it would. Next, I tried swapping
ffserver with an Nginx-powered RTMP server. While not an entirely fruitless endeavor, there were some blockages that I just couldn’t get past.
I received a suggestion from a colleague to fire up the Raspberry Pi’s hardware encoder/decoder. Up until yesterday, I didn’t know this was a thing. Shame on me for not looking into it. So that’s what we’re going to cover in tonight’s post: taking some of what we learned from our first RTMP attempt and make the hardware do all the work. With any luck, we should see some real perf gains, possibly enough for live streams to start instantly (which would make web players happy).
Since I felt like including it here would deviate from the purpose of this post too much, I wrote up how to Add RTMP Support to Nginx if you installed it via
apt-get like me. If you’re in that boat, take a moment to read over that post then come back to this one.
ffmpeg to use hardware
H.264 encoding used to be a fat challenge, but they’ve since added support to the official codebase. If you followed my original ffmpeg post, you’ll have a recent enough version that includes this code, but we’ll still need to compile it.
What we’re looking for this time is the OpenMAX IL (Integration Layer) acceleration module.
[email protected]:/usr/src/ffmpeg $ sudo ./configure --enable-omx --enable-omx-rpisudo makesudo make install
That’ll take some time, as I’ve said before. You’ll have enough free time on your hands to get make something to eat. Come back in an hour or so and it should be done.
NOTE: If you run into ERROR: OpenMAX IL headers not found, then you’ll need to run
apt-get install libomxil-bellagio-dev. Thanks, lordofduct in the comments for that one!
From this point forward, we’ll be starting
ffmpeg similarly to how we did it before but with a slightly different codec.
ffmpeg -i /dev/video0 -framerate 30 -video_size 720x404 -vcodec h264_omx -maxrate 768k -bufsize 8080k -vf "format=yuv420p" -g 60 -f flv rtmp://example.com:8081/hls/live
I confirmed VLC is able to play the stream, which is excellent, and there are no lag or jitter issues. It’s about 10-15 seconds behind live, which is totally fine.
I was able to set up an HTML5 player using tools from Bitmovin. I’m not entirely happy with this setup, though, as the player isn’t free and only HLS is supported, right now1. In my next post I’ll cover a new idea that came to mind when looking into the coolness of Ruby on Rails 5: WebSockets.
Update July 11, 2017: @HPGMiskin pointed out
libomxil-bellagio-bin is not a thing. I’ve pulled that from the optional step for missing OpenMAX headers.
This article is over a year old, that's entirely possible.
I've made many changes to this site over the last few years and sometimes things get missed when I sweep for updates. I wrote this post 716 days ago and might need updating or we're in a situation where I've explained something that is no longer accurate. If you found something incorrect or needs refreshing, let me know and I'll get it fixed.
No ad available
Something went wrong and nothing could be rendered here.