<?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>AVI on File Format Blog</title>
    <link>https://blog.fileformat.com/ms/tag/avi/</link>
    <description>Recent content in AVI on File Format Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>ms</language>
    <lastBuildDate>Mon, 22 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.fileformat.com/ms/tag/avi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Menyahkod AVI: Di Dalam Seni Bina Kontena Warisan Microsoft</title>
      <link>https://blog.fileformat.com/ms/video/decoding-avi-inside-microsoft-s-legacy-container-architecture/</link>
      <pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.fileformat.com/ms/video/decoding-avi-inside-microsoft-s-legacy-container-architecture/</guid>
      <description>Pelajari asas AVI: struktur fail, susun atur chunk, kod FourCC, dan sambungan OpenDML untuk mengendalikan video warisan melebihi had 2 GB.</description>
      <content:encoded><![CDATA[<p><strong>Kemas Kini Terakhir</strong>: 30 Jun, 2026</p>
<figure class="align-center ">
    <img loading="lazy" src="images/decoding-avi-inside-microsoft-s-legacy-container-architecture.webp#center"
         alt="Title - Decoding AVI: Inside Microsoft’s Legacy Container Architecture"/> 
</figure>

<p><strong>TL;DR</strong> – AVI (Audio Video Interleave) ialah kontena “video digital” pertama Microsoft, lahir bersama Windows 95. Ia ialah fail berasaskan RIFF yang menyelitkan kepingan video dan audio termampat supaya pemain dapat membacanya secara serentak. Format ini masih difahami oleh Windows Media Player dan pelbagai alat sumber terbuka, tetapi ia tidak mempunyai ciri moden seperti HDR, warna 10‑bit, dan metadata penstriman yang kukuh. Jika anda perlu meneliti rakaman warisan, fahami susun atur kepingan, kod FourCC, dan sambungan OpenDML yang mengangkat had 2 GB – itulah inti AVI.</p>
<hr>
<h2 id="1-apa-itu-fail-avi-sebenarnya">1. Apa Itu Fail AVI Sebenarnya?</h2>
<ul>
<li><strong>Nama penuh:</strong> <em>Audio Video Interleave</em></li>
<li><strong>Penampilan pertama:</strong> Windows 95 (1995) – Jawapan Microsoft kepada “video digital” pada PC pengguna.</li>
<li><strong>Spesifikasi:</strong> Dibina atas spesifikasi <strong>RIFF</strong> (Resource Interchange File Format) sejak 1991. RIFF ialah kontena generik berasaskan “kepingan”; AVI hanya mentakrifkan satu set kepingan yang menyimpan audio, video, dan data indeks.</li>
<li><strong>Sambungan fail / MIME:</strong> <code>.avi</code> – <code>video/x-msvideo</code>.</li>
<li><strong>Matlamat utama:</strong> Menyimpan aliran audio dan video berinterleasi rapat pada cakera supaya gelung main balik yang naïve dapat membaca satu bingkai video, kemudian sampel audio yang sepadan, tanpa pencarian yang mahal.</li>
<li><strong>Status warisan:</strong> Masih boleh dimainkan dalam Windows Media Player, DirectShow, VLC, dan banyak lagi pemain lain, tetapi ia bukan kontena “moden”. Tiada sokongan HDR asli, 10‑bit, kadar bit berubah-ubah, atau metadata kaya.</li>
</ul>
<hr>
<h2 id="2-di-dalam-kotak--bagaimana-avi-berfungsi">2. Di Dalam Kotak – Bagaimana AVI Berfungsi</h2>
<h3 id="rangka-chunk-riff">Rangka Chunk RIFF</h3>
<p>Fail AVI hanyalah satu siri <strong>bahagian</strong>:</p>
<pre tabindex="0"><code>RIFF &lt;size&gt; &#34;AVI &#34;          ; file header
  LIST &#34;hdrl&#34;               ; header list
    avih ...                ; main AVI header (global info)
    LIST &#34;strl&#34;             ; stream list (one per stream)
      strh ...              ; stream header (type, codec, timing)
      strf ...              ; stream format (codec‑specific data)
  LIST &#34;movi&#34;               ; interleaved media data
    00dc &lt;size&gt; &lt;video frame&gt;
    01wb &lt;size&gt; &lt;audio block&gt;
    …
  idx1 ...                  ; optional index for fast seeking
</code></pre><ul>
<li><strong>ID Bahagian (4 bait)</strong> – contohnya <code>avih</code>, <code>strh</code>, <code>movi</code>.</li>
<li><strong>Saiz Bahagian (4 bait)</strong> – panjang data yang mengikutnya (tidak termasuk medan ID dan saiz).</li>
<li><strong>Data</strong> – muatan sebenar (pengepala, bingkai mentah, dll.).</li>
</ul>
<p>Kerana RIFF boleh diperluas, anda boleh menambah jenis bahagian baru tanpa merosakkan pengurai lama – satu reka bentuk yang mengekalkan AVI hidup selama beberapa dekad.</p>
<h3 id="fourcc--pembisik-codec">FourCC – Pembisik Codec</h3>
<p>Kod empat aksara (FourCC) adalah pengikat yang memberitahu pemain <em>yang mana</em> decoder untuk dimuatkan. Beberapa contoh biasa yang anda akan lihat dalam fail AVI:</p>
<table>
<thead>
<tr>
<th>FourCC</th>
<th>Kodek (ffmpeg)</th>
<th>Penggunaan Biasa</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>DIVX</code></td>
<td><code>mpeg4</code> (DivX)</td>
<td>MPEG‑4 Bahagian 2 Awal</td>
</tr>
<tr>
<td><code>XVID</code></td>
<td><code>mpeg4</code> (Xvid)</td>
<td>Sumber terbuka MPEG‑4</td>
</tr>
<tr>
<td><code>MJPG</code></td>
<td><code>mjpeg</code></td>
<td>Motion‑JPEG (kamera video digital)</td>
</tr>
<tr>
<td><code>H264</code></td>
<td><code>h264</code></td>
<td>H.264/AVC (jarang tetapi mungkin)</td>
</tr>
<tr>
<td><code>MP3 </code></td>
<td><code>mp3</code></td>
<td>Strim audio MP3</td>
</tr>
<tr>
<td><code>PCM </code></td>
<td><code>pcm_s16le</code></td>
<td>Audio PCM tidak dimampatkan</td>
</tr>
</tbody>
</table>
<p>FourCC berada dalam bahagian <strong><code>strh</code></strong> (pengenal codec) dan kadang‑kadang dalam blok <strong><code>strf</code></strong> (format piksel, format sampel audio).</p>
<h3 id="masa--penyelarasan">Masa &amp; Penyelarasan</h3>
<p>AVI menggunakan sistem <strong>time‑base</strong> yang mudah:</p>
<ul>
<li><strong>Pengepala global (<code>avih</code>)</strong>: <code>dwRate</code> / <code>dwScale</code> → bingkai per saat.</li>
<li><strong>Pengepala per‑stream (<code>strh</code>)</strong>: <code>dwRate</code> / <code>dwScale</code> sendiri untuk aliran audio atau video sekunder.</li>
</ul>
<p>Pemain menggandakan nombor bingkai dengan <code>scale/rate</code> untuk mengira tanda masa persembahan (PTS). Jika skala tidak sepadan, anda akan melihat pepijat klasik “audio melayang keluar dari sinkronisasi” yang menghantui alat warisan.</p>
<h3 id="bahagian-movi--di-mana-media-tinggal">Bahagian <code>movi</code> – Di Mana Media Tinggal</h3>
<p>Semua bingkai termampat berada dalam LIST <strong><code>movi</code></strong>. Setiap bingkai didahului oleh <strong>ID bahagian</strong> yang memberitahu anda sama ada ia video (<code>00dc</code>) atau audio (<code>01wb</code>). ID tersebut juga mengekodkan nombor aliran, jadi fail dengan dua trek audio akan mempunyai <code>01wb</code> dan <code>02wb</code>.</p>
<p>Oleh kerana data sudah diinterleav, pemain boleh membaca satu bingkai video, kemudian blok audio seterusnya, dan memaparkannya bersama tanpa perlu mencari jauh ke depan. Corak penulisan deterministik itu menjadikan AVI popular untuk peranti rakaman awal yang memerlukan penulisan cakera latensi rendah.</p>
<h3 id="pengindeksan-idx1--majukan-cepat-undur-cepat">Pengindeksan (<code>idx1</code>) – Majukan Cepat, Undur Cepat</h3>
<p>Bahagian <strong><code>idx1</code></strong> pilihan ialah jadual ofset dan saiz bagi setiap bingkai dalam <code>movi</code>. Apabila ada, pencarian menjadi hanya carian jadual mudah. Jika tiada, pemain mesti mengimbas fail secara langsung – yang boleh menyebabkan jeda “penyangga” yang ketara pada fail besar.</p>
<h3 id="opendml-avi-20--memecahkan-halangan-2gb">OpenDML (<code>AVI 2.0</code>) – Memecahkan Halangan 2 GB</h3>
<p>Spesifikasi RIFF asal mengehadkan medan saiz chunk kepada integer tak bertanda 32‑bit → <strong>2 GB</strong> saiz fail maksimum. OpenDML (kadang‑kadang dipanggil <em>AVI 2.0</em>) memperkenalkan:</p>
<ul>
<li><strong><code>AVIX</code></strong> LISTs – bahagian RIFF “lanjutan” tambahan yang boleh mengikut 2 GB pertama.</li>
<li><strong><code>indx</code></strong> chunk – indeks yang menyokong 64‑bit.</li>
<li>Medan pengepala tambahan untuk durasi yang lebih panjang.</li>
</ul>
<p>Kebanyakan alat moden (ffmpeg, VLC) secara automatik beralih ke OpenDML apabila output melebihi 2 GB, tetapi banyak pemain lama masih mengalami masalah dengan chunk <code>AVIX</code>, jadi anda kadang‑kadang akan melihat hack keserasian yang memecah rakaman panjang menjadi beberapa fail AVI 2 GB.</p>
<hr>
<h2 id="3-di-mana-avi-berada-pada-2024">3. Di Mana AVI Berada pada 2024?</h2>
<table>
<thead>
<tr>
<th>Trend</th>
<th>Apa Maksudnya untuk AVI</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Beralih ke MP4/MKV/ProRes</strong></td>
<td>Pengeluaran baru lebih suka kontena yang secara asli menyokong HDR, 10‑bit, VBR, dan metadata yang kaya. AVI jarang dipilih untuk kandungan baru.</td>
</tr>
<tr>
<td><strong>Perkakasan warisan</strong></td>
<td>Kamera CCTV lama, camcorder awal‑2000an, dan beberapa enjin permainan masih menghasilkan AVI. Anda masih perlu memasukkan fail‑fail tersebut dalam aliran kerja moden.</td>
</tr>
<tr>
<td><strong>Sokongan sumber terbuka</strong></td>
<td><code>ffmpeg</code>, <code>libav</code>, <code>VLC</code>, <code>HandBrake</code>, dan <code>GStreamer</code> mengekalkan parser AVI tetap hidup, tetapi mereka sering <strong>menyahkod semula</strong> kepada MP4/MKV untuk pengedaran.</td>
</tr>
<tr>
<td><strong>Kebangkitan OpenDML</strong></td>
<td>Rakaman pengawasan 4K yang berjalan selama berhari‑hari melebihi 2 GB dengan cepat. OpenDML (<code>AVIX</code>) masih menjadi penyelesaian utama, walaupun banyak alat tidak mengendalikannya dengan betul.</td>
</tr>
<tr>
<td><strong>Pengukuhan keselamatan</strong></td>
<td>Pengurai AVI bersejarah menerima saiz kepingan yang cacat, menyebabkan CVE (contohnya, CVE‑2020‑13144). Windows kini lebih suka Media Foundation, yang menolak banyak keanehan warisan, mendorong pembangun ke arah saluran yang lebih selamat.</td>
</tr>
<tr>
<td><strong>Saluran bebas kontena</strong></td>
<td>Kerangka media moden menganggap AVI sebagai elemen sumber lain. Setelah data di-demux menjadi penampan mentah, bekas kontena menjadi tidak relevan untuk pemprosesan hiliran.</td>
</tr>
</tbody>
</table>
<p>Ringkasnya, AVI <strong>masih hidup tetapi menua</strong> – ia bertahan di mana perkakasan lama atau penyimpanan berselang sederhana diperlukan, tetapi ia bukan pilihan utama untuk projek baru.</p>
<hr>
<h2 id="4-praktikal-bekerja-dengan-avi-hari-ini">4. Praktikal: Bekerja dengan AVI Hari Ini</h2>
<h3 id="a-intip-header-minimum-hex">A. Intip Header Minimum (hex)</h3>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text"><span style="display:flex;"><span>52 49 46 46  00 00 00 00  41 56 49 20   ; &#34;RIFF&#34; + size + &#34;AVI &#34;
</span></span><span style="display:flex;"><span>4C 49 53 54  20 00 00 00  68 64 72 6C   ; LIST &#34;hdrl&#34;
</span></span><span style="display:flex;"><span>...
</span></span></code></pre></div><p>Magik <code>RIFF</code> (<code>52 49 46 46</code>) memberitahu mana-mana pengurai “ini adalah fail RIFF”. Empat bait seterusnya ialah saiz fail keseluruhan (tolak 8). Pengenal <code>&quot;AVI &quot;</code> mengunci fail ke dalam keluarga AVI.</p>
<h3 id="b-menukar-mp4-moden--avi-warisan">B. Menukar MP4 Moden → AVI Warisan</h3>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ffmpeg -i input.mp4 <span style="color:#ae81ff">\
</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>       -c:v mpeg4 -q
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span style="color:#e6db74">```</span>bash
</span></span><span style="display:flex;"><span>ffmpeg -i input.mp4 <span style="color:#ae81ff">\\</span> -c:v mpeg4 -qscale:v <span style="color:#ae81ff">5</span> <span style="color:#ae81ff">\\</span>   <span style="color:#75715e"># MPEG‑4 Bahagian 2 (serasi dengan DivX/Xvid) -c:a mp3 -b:a 192k \\      # audio MP3 (kebanyakan pemain AVI memahami ini) -f avi output.avi</span>
</span></span></code></pre></div><p>The command above forces <strong>MPEG‑4 Part 2</strong> video (the codec most legacy AVI players recognize) and <strong>MP3</strong> audio, then writes an AVI container. If you need <strong>OpenDML</strong> support for files larger than 2 GB, add the <code>-movflags +faststart</code>‑style flag that tells FFmpeg to use the extended <code>AVIX</code> chunks:</p>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ffmpeg -i input.mp4 <span style="color:#ae81ff">\\</span> -c:v mpeg4 -qscale:v <span style="color:#ae81ff">5</span> <span style="color:#ae81ff">\\</span> -c:a mp3 -b:a 192k <span style="color:#ae81ff">\\</span> -f avi -flags +global_header -movflags +faststart output.avi
</span></span></code></pre></div><blockquote>
<p><strong>Tip:</strong> Some older Windows Media Player versions still choke on the <code>AVIX</code> extension. If you must stay under 2 GB, split the source into multiple AVIs using the <code>-segment_time</code> and <code>-f segment</code> muxer.</p>
</blockquote>
<hr>
<h2 id="5-common-pitfalls--how-to-fix-them">5. Common Pitfalls &amp; How to Fix Them</h2>
<table>
<thead>
<tr>
<th>Symptom</th>
<th>Likely Cause</th>
<th>Fix</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Audio drifts out of sync after a few minutes</strong></td>
<td>Mismatched <code>dwRate/dwScale</code> between <code>avih</code> and <code>strh</code> (or a VBR audio stream)</td>
<td>Re‑encode audio to a constant‑bitrate format (e.g., MP3 128 kbps) or use <code>-vsync 2</code> in FFmpeg to force frame‑accurate timestamps.</td>
</tr>
<tr>
<td><strong>“Cannot play this video” on Windows Media Player</strong></td>
<td>Missing or corrupt <code>idx1</code> index, or OpenDML (<code>AVIX</code>) chunks not recognized</td>
<td>Run <code>ffmpeg -i broken.avi -c copy -map 0 -f avi repaired.avi</code> to rebuild the index; or use <code>aviindex</code> (part of <code>mplayer</code>) to generate a fresh <code>idx1</code>.</td>
</tr>
<tr>
<td><strong>File size capped at 2 GB despite long footage</strong></td>
<td>Encoder used classic AVI (no OpenDML)</td>
<td>Add <code>-use\_open\_dml 1</code> (FFmpeg) or <code>-format avi2</code> (VirtualDub) to enable OpenDML extensions.</td>
</tr>
<tr>
<td><strong>Green or corrupted frames</strong></td>
<td>Incompatible FourCC (e.g., H.264 in an AVI without proper headers)</td>
<td>Stick to codecs known to work in AVI (<code>mpeg4</code>, <code>msmpeg4v2</code>, <code>MJPG</code>, <code>XVID</code>). If you must store H.264, use the <code>h264</code> FourCC and ensure the <code>strf</code> chunk contains the SPS/PPS extradata.</td>
</tr>
<tr>
<td><strong>Playback stalls on network streams</strong></td>
<td>AVI’s lack of robust streaming metadata (no <code>moov</code> atom)</td>
<td>Wrap the AVI in a streaming protocol (e.g., RTSP) that handles byte‑range requests, or convert to MP4/MKV for smoother streaming.</td>
</tr>
</tbody>
</table>
<hr>
<h2 id="6-debugging-tools-you-should-keep-handy">6. Debugging Tools You Should Keep Handy</h2>
<table>
<thead>
<tr>
<th>Tool</th>
<th>Platform</th>
<th>What It Does</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>ffprobe / ffmpeg</strong></td>
<td>Cross‑platform</td>
<td>Dumps every chunk, FourCC, timestamps, and can rebuild indexes (<code>-c copy</code>).</td>
</tr>
<tr>
<td><strong>MediaInfo</strong></td>
<td>Windows/macOS/Linux</td>
<td>Human‑readable summary of streams, codecs, and container flags.</td>
</tr>
<tr>
<td><strong>VirtualDub</strong></td>
<td>Windows</td>
<td>Classic AVI editor; can rebuild headers, add OpenDML, and preview frame‑by‑frame.</td>
</tr>
<tr>
<td><strong>GSpot (legacy)</strong></td>
<td>Windows</td>
<td>Identifies obscure FourCCs and suggests appropriate codecs.</td>
</tr>
<tr>
<td><strong>aviindex</strong> (part of MPlayer)</td>
<td>Linux/macOS</td>
<td>Generates a fresh <code>idx1</code> chunk for broken files.</td>
</tr>
<tr>
<td><strong>Hex editors (HxD, Bless)</strong></td>
<td>Any</td>
<td>Directly inspect RIFF headers when you suspect malformed chunk sizes.</td>
</tr>
</tbody>
</table>
<p>A typical workflow when an AVI refuses to play:</p>
<ol>
<li><strong>Inspect</strong> with <code>ffprobe -show_format -show_streams file.avi</code>.</li>
<li><strong>Check</strong> the index: <code>ffmpeg -i file.avi -c copy -f avi -y temp.avi</code> (FFmpeg will rebuild it automatically).</li>
<li><strong>Validate</strong> FourCCs: <code>mediainfo file.avi</code>. If you see an unknown codec, consider re‑encoding that stream.</li>
<li><strong>Repair</strong> with VirtualDub → “File → Re‑open as AVI (OpenDML)”. Save a fresh copy.</li>
</ol>
<hr>
<h2 id="7-when-and-when-not-to-use-avi">7. When (and When Not) to Use AVI</h2>
<h3 id="good-usecases">Good Use‑Cases</h3>
<table>
<thead>
<tr>
<th>Scenario</th>
<th>Why AVI Works</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Legacy camcorder ingest</strong></td>
<td>The device outputs native AVI; transcoding adds unnecessary quality loss.</td>
</tr>
<tr>
<td><strong>Simple interleaved capture</strong></td>
<td>Low‑latency write to disk without needing complex container features.</td>
</tr>
<tr>
<td><strong>Compatibility with old Windows‑only software</strong></td>
<td>Some industrial automation tools only understand AVI.</td>
</tr>
<tr>
<td><strong>Archiving raw, uncompressed video</strong></td>
<td>AVI can hold PCM audio and uncompressed RGB24 video without extra overhead.</td>
</tr>
</tbody>
</table>
<h3 id="bad-usecases">Bad Use‑Cases</h3>
<table>
<thead>
<tr>
<th>Scenario</th>
<th>Why AVI Fails</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>HDR or 10‑bit color</strong></td>
<td>No standard way to store those pixel formats; you’d need a custom FourCC that most players ignore.</td>
</tr>
<tr>
<td><strong>Variable‑bit‑rate streaming</strong></td>
<td>Lack of a proper <code>moov</code>‑like atom makes adaptive bitrate impossible.</td>
</tr>
<tr>
<td><strong>Rich metadata (chapters, subtitles, tags)</strong></td>
<td>AVI’s chunk model doesn’t define standard containers for subtitles or extensive tags.</td>
</tr>
<tr>
<td><strong>Cross‑platform mobile distribution</strong></td>
<td>Modern mobile players expect MP4/MKV; AVI may not be hardware‑accelerated.</td>
</tr>
</tbody>
</table>
<p>If you’re starting a new project, treat AVI as a <strong>fallback</strong> for legacy pipelines, not a primary delivery format.</p>
<hr>
<h2 id="8-future-outlook--will-avi-ever-make-a-comeback">8. Future Outlook – Will AVI Ever Make a Comeback?</h2>
<p>The short answer: <strong>unlikely</strong>. The industry has coalesced around <strong>ISO‑BMFF‑based</strong> containers (MP4, MOV, HEVC‑MP4, etc.) because they support:</p>
<ul>
<li><strong>Extensible metadata</strong> (ISO‑UserData, UUID boxes).</li>
<li><strong>Fragmented streaming</strong> (moof/mdat) for adaptive bitrate.</li>
<li><strong>Native HDR/10‑bit/12‑bit</strong> video definitions.</li>
</ul>
<p>AVI’s design, while elegant for its time, is fundamentally limited by its 32‑bit size fields and its reliance on external FourCC‑driven codecs. Even though OpenDML extended the size limit, it never gained widespread adoption beyond niche surveillance and archival tools.</p>
<p>That said, <strong>software preservation</strong> will keep AVI parsers alive for decades. Projects like <strong>FFmpeg</strong>, <strong>GStreamer</strong>, and <strong>VLC</strong> will continue to support the format, ensuring that the massive archive of 1990s‑2000s footage remains accessible. In a world where “digital archaeology” is becoming a real discipline, knowing how to read and repair AVI files is still a valuable skill.</p>
<hr>
<h2 id="9-quick-reference-cheatsheet">9. Quick Reference Cheat‑Sheet</h2>
<table>
<thead>
<tr>
<th>Item</th>
<th>Command / Setting</th>
<th>Explanation</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Create classic AVI</strong></td>
<td><code>ffmpeg -i src -c:v mpeg4 -qscale:v 5 -c:a mp3 -b:a 192k -f avi out.avi</code></td>
<td>Simple, widely compatible.</td>
</tr>
<tr>
<td><strong>Enable OpenDML</strong></td>
<td><code>ffmpeg -i src -c:v mpeg4 -qscale:v 5 -c:a mp3 -b:a 192k -f avi -use_open_dml 1 out.avi</code></td>
<td>Allows &gt;2 GB files.</td>
</tr>
<tr>
<td><strong>Re‑index broken AVI</strong></td>
<td><code>ffmpeg -i broken.avi -c copy -f avi repaired.avi</code></td>
<td>Rewrites <code>idx1</code>.</td>
</tr>
<tr>
<td><strong>Split &gt;2 GB into chunks</strong></td>
<td><code>ffmpeg -i long.avi -c copy -map 0 -segment_time 1800 -f segment part_%03d.avi</code></td>
<td>30‑minute segments stay under the limit.</td>
</tr>
<tr>
<td><strong>Inspect header</strong></td>
<td><code>ffprobe -show_format -show_streams file.avi</code></td>
<td>Dumps all RIFF chunks and stream info.</td>
</tr>
<tr>
<td><strong>Add a subtitle track (non‑standard)</strong></td>
<td><code>ffmpeg -i video.avi -i subs.srt -c copy -metadata:s:s:0 language=eng out.avi</code></td>
<td>Works only with players that read the <code>txt</code> stream; not universally supported.</td>
</tr>
</tbody>
</table>
<p>Keep this table bookmarked; it covers 80 % of everyday AVI tasks.</p>
<hr>
<h2 id="10-best-practices-for-archiving-avi-files">10. Best Practices for Archiving AVI Files</h2>
<p>Even though AVI is a legacy container, many institutions still have petabytes of it sitting on tape or in cold‑storage. Treating those assets with a disciplined workflow will save you headaches down the line.</p>
<table>
<thead>
<tr>
<th>Practice</th>
<th>Why It Matters</th>
<th>How to Implement</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Validate on ingest</strong></td>
<td>Corrupt headers or missing indexes can go unnoticed until playback.</td>
<td>Run <code>ffprobe -v error -show_format -show_streams file.avi</code> immediately after copying. Log any non‑zero exit codes.</td>
</tr>
<tr>
<td><strong>Generate a checksum</strong></td>
<td>Guarantees bit‑exact preservation across media migrations.</td>
<td>Use SHA‑256 (<code>sha256sum file.avi &gt; file.avi.sha256</code>). Store the checksum alongside the file in your catalog.</td>
</tr>
<tr>
<td><strong>Create a modern proxy</strong></td>
<td>Most downstream workflows (editing, streaming) expect MP4/MKV.</td>
<td>Encode a low‑bitrate MP4 proxy (<code>ffmpeg -i file.avi -c:v libx264 -crf 23 -c:a aac -b:a 128k proxy.mp4</code>). Keep the proxy in the same directory with a clear naming convention (<code>*_proxy.mp4</code>).</td>
</tr>
<tr>
<td><strong>Document FourCCs and codec versions</strong></td>
<td>Some FourCCs map to multiple codec implementations (e.g., <code>DIVX</code> could be DivX 5, 6, or 7).</td>
<td>Extract the codec private data (<code>ffprobe -show_private_data</code>) and store it in a side‑car JSON file (<code>file.avi.codec.json</code>).</td>
</tr>
<tr>
<td><strong>Migrate to OpenDML for large files</strong></td>
<td>Files &gt;2 GB will become unreadable on older players.</td>
<td>When transcoding, always pass <code>-use_open_dml 1</code>. If you’re only copying, use <code>aviindex</code> to rebuild an OpenDML‑compatible index.</td>
</tr>
<tr>
<td><strong>Store metadata in a side‑car</strong></td>
<td>AVI has no standard for extensive tags (e.g., creator, location).</td>
<td>Use XMP side‑car files (<code>file.avi.xmp</code>) or embed a small <code>INFO</code> LIST chunk manually if you need minimal in‑container metadata.</td>
</tr>
<tr>
<td><strong>Regularly test playback</strong></td>
<td>Bit‑rot can affect codecs as well as containers.</td>
<td>Schedule a quarterly job that runs a headless player (e.g., <code>ffplay -autoexit -frames 10 file.avi</code>) and reports any failures.</td>
</tr>
</tbody>
</table>
<p>By applying these steps at the moment of acquisition, you avoid costly “repair‑the‑archive” projects later.</p>
<hr>
<h2 id="11-frequently-asked-questions-faq">11. Frequently Asked Questions (FAQ)</h2>
<p><strong>Q1: Can I store H.265/HEVC video inside an AVI file?</strong><br>
<em>Short answer:</em> Technically yes, if you supply the correct FourCC (<code>HEVC</code> or <code>HVC1</code>) and include the SPS/PPS NAL units in the <code>strf</code> chunk. In practice, very few players support it, and many will treat the stream as unknown. For reliable playback, stick to MPEG‑4 Part 2 or Motion‑JPEG.</p>
<p><strong>Q2: Why does Windows Media Player sometimes show a black screen but still plays audio?</strong><br>
<em>Explanation:</em> The player has successfully opened the audio stream but failed to locate a usable video decoder for the FourCC. This can happen when the FourCC is custom or when the required codec isn’t installed. Installing a codec pack (e.g., K-Lite) or re‑encoding the video to a known FourCC resolves the issue.</p>
<p><strong>Q3: Is there any way to embed subtitles directly into an AVI file?</strong><br>
<em>Answer:</em> AVI does not define a standard subtitle stream. Some tools cheat by adding a “txt” stream (FourCC <code>txt </code>) that contains plain‑text subtitles, but only a handful of players (e.g., VirtualDub with a plugin) will render them. The recommended approach is to keep subtitles in a separate <code>.srt</code> or <code>.ass</code> file, or to re‑mux into a container that officially supports subtitles (MP4, MKV).</p>
<p><strong>Q4: My video shows a “frame rate mismatch” warning in MediaInfo. What should I do?</strong><br>
<em>Solution:</em> Verify that the <code>dwRate</code>/<code>dwScale</code> values in both the global <code>avih</code> and per‑stream <code>strh</code> headers are consistent. If they differ, re‑mux with FFmpeg using <code>-video_track_timescale</code> to force a uniform time base:</p>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ffmpeg -i broken.avi -c copy -video_track_timescale <span style="color:#ae81ff">1000</span> fixed.avi
</span></span></code></pre></div><p><strong>Q5: Does AVI support multiple audio languages?</strong><br>
<em>Yes, but with caveats.</em> You can add several audio streams, each with its own <code>strh</code>/<code>strf</code> pair and a distinct stream number (<code>01wb</code>, <code>02wb</code>, …). However, there is no standardized way to label the language; you must rely on external metadata (e.g., an accompanying <code>.xml</code> file) or embed a custom <code>INFO</code> chunk.</p>
<p><strong>Q6: How can I extract raw frames from an AVI without re‑encoding?</strong><br>
<em>Command:</em></p>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ffmpeg -i source.avi -c:v copy -f image2 frame_%05d.bmp
</span></span></code></pre></div><p>Replace <code>bmp</code> with <code>png</code> or <code>tiff</code> if you prefer lossless image formats. The <code>-c:v copy</code> flag tells FFmpeg to dump the compressed frames as‑is; if the codec is MJPEG, the output will already be JPEG images.</p>
<p><strong>Q7: Are there any security concerns when opening AVI files from untrusted sources?</strong><br>
<em>Yes.</em> Malformed chunk sizes can trigger buffer overflows in legacy parsers (e.g., older DirectShow filters). Always open unknown AVIs in a sandboxed environment or use a modern library like FFmpeg that performs strict bounds checking. Updating Windows Media Foundation and disabling legacy DirectShow filters further mitigates risk.</p>
<hr>
<h2 id="12-tldr-ringkasan-untuk-yang-tidak-sabar">12. TL;DR Ringkasan (untuk yang Tidak Sabar)</h2>
<ul>
<li><strong>AVI = RIFF‑based, interleaved container</strong> introduced with Windows 95.</li>
<li><strong>FourCC</strong> tells the player which codec to use; common ones are <code>DIVX</code>, <code>XVID</code>, <code>MJPG</code>, <code>H264</code>, <code>MP3 </code>.</li>
<li><strong>Timing</strong> is driven by <code>dwRate/dwScale</code> in the global and stream headers.</li>
<li><strong><code>movi</code></strong> holds the actual media; <strong><code>idx1</code></strong> (optional) speeds up seeking.</li>
<li><strong>OpenDML (<code>AVIX</code>)</strong> lifts the 2 GB limit but isn’t universally supported.</li>
<li><strong>Use cases today:</strong> legacy camcorder ingest, simple interleaved capture, archival of raw PCM video.</li>
<li><strong>Avoid for new projects:</strong> no HDR, 10‑bit, VBR, subtitles, or rich metadata.</li>
<li><strong>Toolbox:</strong> <code>ffprobe</code>, <code>ffmpeg</code>, MediaInfo, VirtualDub, aviindex, hex editors.</li>
<li><strong>Best practice:</strong> validate, checksum, generate modern proxies, and migrate large files to OpenDML.</li>
</ul>
<hr>
<h2 id="13-pemikiran-penutup">13. Pemikiran Penutup</h2>
<p>AVI’s simplicity is both its strength and its Achilles’ heel. It gave early PC users a straightforward way to store synchronized audio‑video pairs, and that design philosophy—interleaved chunks, a clear header layout, and extensible FourCC identifiers—still influences modern containers. While the industry has moved on to more feature‑rich formats, the sheer volume of legacy footage means AVI will remain a “must‑know” for anyone working in video preservation, forensic analysis, or any field that must bridge the past with today’s workflows.</p>
<p>If you ever find yourself staring at a dusty <code>.avi</code> on a hard drive from the late‑90s, you now have the conceptual map, the command‑line recipes, and the troubleshooting checklist to bring that footage back to life—whether you choose to keep it in its original container or transcode it into a modern, HDR‑ready format.</p>
<p>Happy demuxing!</p>
<!-- raw HTML omitted -->
]]></content:encoded>
    </item>
    
  </channel>
</rss>
