<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FFmpeg on Mi&amp;Bee Blog</title><link>/en/tags/ffmpeg/</link><description>Recent content in FFmpeg on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Thu, 02 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/ffmpeg/rss.xml" rel="self" type="application/rss+xml"/><item><title>gortmplib vs go2rtc vs FFmpeg: RTMP Push Source Comparison &amp; Integrating with Chinese Live-Streaming Platforms</title><link>/en/posts/mibee-oss/douyu-rtmp-handshake-analysis/</link><pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate><guid>/en/posts/mibee-oss/douyu-rtmp-handshake-analysis/</guid><description>&lt;p&gt;To push camera feeds from the MiBee NVR project to a domestic live-streaming platform, there are three candidates: call FFmpeg directly, use the pure-Go gortmplib, or use go2rtc. All three &amp;ldquo;do RTMP&amp;rdquo;, but their behaviour against Chinese live-streaming platforms differs wildly — some disconnect instantly, some after a few seconds, some are rock solid. This post tears all three apart at the source level, and walks through the pitfalls and fixes for integrating with FMS-compatible domestic platforms.&lt;/p&gt;</description></item></channel></rss>