<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Xiaomi on Mi&amp;Bee Blog</title><link>/en/tags/xiaomi/</link><description>Recent content in Xiaomi on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Sun, 14 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/xiaomi/rss.xml" rel="self" type="application/rss+xml"/><item><title>MiBeeNvr v0.7.0: Timelapse v2 + Dual-Lens Xiaomi + H.265 Muxing + Release Hardening</title><link>/en/posts/mibee-oss/mibee-nvr-v0.7/</link><pubDate>Sun, 14 Jun 2026 00:00:00 +0000</pubDate><guid>/en/posts/mibee-oss/mibee-nvr-v0.7/</guid><description>&lt;p&gt;After v0.6.0 put the timelapse pipeline in place, community feedback quickly pointed out several hard problems: the JPEG sequence consumed too much storage, H.265 cameras couldn&amp;rsquo;t generate playable timelapse segments, dual-lens Xiaomi devices could only capture the main lens, and H.265 HLS would occasionally panic outright. None of these are edge cases — the dual-lens CW500 and Outdoor Cam 4 ship in large volumes in China, and H.265 is the de facto standard for mid-to-high-end cameras. The v0.7.0 mainline was built around exactly this feedback.&lt;/p&gt;</description></item></channel></rss>