<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Video on VibePapa — Tech from the Boseong River</title>
    <link>https://boseonggang.com/tags/video/</link>
    <description>Recent content in Video on VibePapa — Tech from the Boseong River</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 14 Jul 2026 07:32:12 +0900</lastBuildDate>
    <atom:link href="https://boseonggang.com/tags/video/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your Phone Saves H.265. The Browser Wants H.264.</title>
      <link>https://boseonggang.com/posts/h265-vs-h264-why-the-videos-wouldnt-play/</link>
      <pubDate>Tue, 14 Jul 2026 07:32:12 +0900</pubDate>
      <guid>https://boseonggang.com/posts/h265-vs-h264-why-the-videos-wouldnt-play/</guid>
      <description>My daughter&amp;#39;s videos backed up fine but wouldn&amp;#39;t play in the browser — sound, no picture — and the big ones buffered forever. The cause was the video codec (H.265) and the file size. Here&amp;#39;s how a one-time ffmpeg conversion to H.264 720p fixed both.</description>
    </item>
  </channel>
</rss>
