免费转换 AVCHD 文件

Why did camcorders use complex BDMV folder structure instead of simple video files?

AVCHD specification designed folder structure mimicking Blu-ray disc organization (BDMV/STREAM/, BDMV/CLIPINF/, BDMV/PLAYLIST/) to enable direct burning to Blu-ray without conversion. Marketing vision: record on camcorder, insert SD card into Blu-ray recorder, burn disc for TV playback. Folder structure carries metadata (thumbnails, clip information, playlists) enabling Blu-ray menu systems. In practice, nobody used this workflow - people uploaded to computers instead. Complex structure that made sense for Blu-ray compatibility became confusing obstacle for users wanting simple video files.

结构还启用了高级功能：播放列表文件（.mpls）定义了在多个文件中录制时的播放顺序，剪辑信息文件（.clpi）存储了用于编辑系统的帧精确时间，缩略图缓存用于快速预览。专业摄像机利用这些元数据；消费者用户对此感到困惑。在复制 AVCHD 内容时，必须保留整个 BDMV 结构，否则软件无法正确解释文件。单个 .mts 文件没有支持文件会丢失元数据和章节点。这种复杂性对专业人士来说是功能，对消费者来说是缺陷。

如何将整个 AVCHD BDMV 文件夹导入视频编辑器？

专业编辑人员理解 AVCHD 结构：

Premiere Pro / Final Cut

专业编辑人员原生导入 AVCHD。文件 → 导入，选择 BDMV 文件夹，软件解析结构，显示所有带有元数据的剪辑。Premiere 识别来自摄像机、读卡器或复制的 SD 卡的文件夹结构。剪辑以原始时间码、缩略图和元数据出现。可以直接编辑而无需转换 - 编辑后导出为交付格式。这保留了最大质量，避免了双重转码（AVCHD→MP4→编辑后的 MP4）。专业工作流程：编辑原生格式，一次导出。

消费者编辑器

iMovie, Windows Movie Maker, consumer tools struggle with AVCHD structure. Might import only first clip, lose metadata, or reject folder entirely. Workaround: convert AVCHD to MP4 first using HandBrake or FFmpeg, then import MP4 to consumer editor. Or use camcorder software (Canon, Sony, Panasonic provide utilities) that converts footage during import. Pre-conversion simplifies editing experience at cost of generation loss and processing time.

直接导入 MTS

可以通过直接从 STREAM 文件夹导入 .mts 文件来绕过 BDMV 结构。将 BDMV/STREAM/*.MTS 文件拖入编辑器。这可以工作，但会丢失剪辑元数据、缩略图和播放列表组织。编辑器将文件视为单独的剪辑，而不是组织良好的项目。对于元数据不重要的简单项目来说，这很好。保留结构需要 AVCHD 识别的导入。

Archive.org 工作流程

首先将整个 SD 卡或摄像机内存复制到计算机，保留 BDMV 结构。不要直接从摄像机导入到编辑器 - 摄像机在编辑过程中可能会格式化卡片，导致数据丢失。创建完整的文件夹备份，然后从备份中导入。这保留了卡上的原始素材，直到确认导入成功。数字囤积摄像机原件是对导入失败的廉价保险。

AVCHD 识别软件优雅地处理结构。非识别工具需要变通方法（预转换或直接导入 MTS）。在规划工作流程之前，了解您编辑器的能力。

为什么 AVCHD 视频看起来是交错的，我该怎么处理？

{faq_3_intro}

{faq_3_web_title}

{faq_3_web_desc}

{faq_3_photos_title}

{faq_3_photos_desc}

{faq_3_graphics_title}

{faq_3_graphics_desc}

{faq_3_print_title}

{faq_3_print_desc}

{faq_3_social_title}

{faq_3_social_desc}

{faq_3_professional_title}

{faq_3_professional_desc}

{faq_3_mobile_title}

{faq_3_mobile_desc}

{faq_3_outro}

我可以从 SD 卡恢复已删除的 AVCHD 素材吗？

{faq_4_answer_p1}

{faq_4_answer_p2}

{faq_4_answer_p3}

是什么导致 AVCHD 摄像机在市场上完全消失？

Smartphones killed dedicated camcorder market. iPhone and Android phones reached good-enough video quality (720p then 1080p then 4K) eliminating need for separate device. Convenience of always-available camera in pocket trumped camcorder's superior zoom, battery life, ergonomics. Camcorder sales collapsed 2010-2015 as smartphone video improved. Remaining market (enthusiasts, events, professionals) too small to sustain consumer camcorder development. AVCHD format died with hardware ecosystem that created it.

分享摩擦加速了衰退。摄像机录制到 AVCHD 需要计算机传输，并且通常在分享之前需要转换。智能手机直接捕获可分享至社交媒体、消息传递、云存储的 MP4，无需中间步骤。对于大多数用户来说，这种工作流程的简单性比视频质量更重要。人们更重视即时分享，而不是专用摄像机带来的稍微更好的质量。为磁带/光盘时代优化的格式和工作流程无法与云原生智能手机的方法竞争。

行业反应太迟缓。到制造商为摄像机增加 WiFi、触摸屏、应用集成时，智能手机已经主导了人们的思维。佳能、索尼、松下缩减了消费类摄像机系列，专注于专业市场（广播摄像机、电影摄像机），在这些领域智能手机无法竞争。消费类摄像机成为特定需求（体育、活动、野生动物）的利基产品，而不是大众市场设备。AVCHD 的遗产仍然存在于广播设备中，但消费类实施已经消亡。智能手机的颠覆是彻底和永久的。

我应该以原始格式归档 AVCHD 素材，还是转换为 MP4？

为了长期保存，转换为 MP4。随着摄像机的消失和软件放弃对旧格式的支持，AVCHD 的支持正在下降。在 10-20 年内，找到能够正确处理 AVCHD 结构的工具可能会很困难。MP4 是具有长期支持保证的通用标准。在工具运行良好时立即转换，同时保留 AVCHD 原件和 MP4 衍生文件（如果存储允许）。不要拖延，假设未来的工具会处理转换 - 格式迁移窗口最终会关闭。

质量保存：在转换为 H.264 MP4 进行归档时，使用高 CRF 值（18-20）。这保持接近原始质量，只有轻微的代际损失。或者使用 H.265 MP4，CRF 值为 22-24，以更小的文件大小实现类似的质量。不要使用默认的 CRF 23（为一般用途平衡） - 归档需要更高的质量设置。磁盘空间便宜；不可替代的记忆是无价的。倾向于更大的文件和更好的质量。可以随时从高质量母版创建更小的衍生文件。

Metadata preservation: extract recording date, GPS coordinates, camera settings from AVCHD before converting. FFmpeg's `-map_metadata 0` preserves most metadata but verify. Use exiftool to check metadata in output file matching original. If metadata lost, manually tag files with dates, locations, subjects. Metadata ensures collection remains searchable and meaningful decades later when memory fades. Organize converted files hierarchically by year/event with descriptive names. Future you will thank present you for good archival practices.

为什么来自不同相机的 AVCHD 质量差异如此之大？

AVCHD 是容器规范，而不是质量保证。该规范允许宽比特率范围（5-28 Mbps），在 H.264 中使用不同的编解码器（配置文件/级别），音频质量各异。制造商以不同的方式实现 AVCHD：高端索尼/佳能摄像机以 24 Mbps 录制，编码效果极佳，预算型号使用 12-15 Mbps 的廉价编码器。相同的 AVCHD 格式，输出质量却截然不同。此外，传感器大小、镜头质量、图像处理管道在不同相机层次之间差异巨大，影响编码前的源质量。

录制模式很重要：相机提供多种 AVCHD 模式（HQ、SP、LP，代表不同的比特率）。HQ 模式可能是 24 Mbps，LP 模式是 5 Mbps。用户选择 LP 模式以获得更长的录制时间，牺牲了质量。检查相机设置 - 许多用户无意中录制了最低质量模式，想知道为什么素材看起来很糟糕。专业相机默认最高质量；消费类型号通常默认平衡模式，优先考虑录制时间而非质量。始终检查并明确设置录制模式。

光照条件放大了质量差异。消费类摄像机在低光照条件下表现不佳 - 噪声、伪影、颜色差。具有更大传感器的专业摄像机能够优雅地处理具有挑战性的光照。AVCHD 编码加剧了这些差异 - 嘈杂的源压缩效果差，干净的源压缩效果好。在良好的光照条件下，相同的比特率产生优秀的结果，而在昏暗条件下则产生糟糕的结果。这解释了为什么某些 AVCHD 素材看起来像广播质量，而其他素材看起来像业余作品，尽管格式相同。源质量和编码实现比格式规范更重要。

我如何将连续录制的多个 AVCHD 剪辑合并为单个文件？

摄像机由于文件系统限制而分割录制：

文件系统限制

FAT32（用于大多数 SD 卡）有 4GB 的文件大小限制。长时间录制会自动分割成多个文件（00000.MTS、00001.MTS、00002.MTS）。相机在文件之间无缝继续录制。在摄像机播放时，显示为单个连续录制。当复制到计算机时，文件会显示为单独的文件，需要手动连接以生成单个输出文件。

FFmpeg Concatenation

FFmpeg's concat demuxer joins split files losslessly. Create text file listing parts in order: `file 'BDMV/STREAM/00000.MTS'` `file 'BDMV/STREAM/00001.MTS'` `file 'BDMV/STREAM/00002.MTS'`. Then concatenate: `ffmpeg -f concat -safe 0 -i filelist.txt -c copy joined.mts`. This copies streams without re-encoding (fast, lossless). Finally convert joined file to MP4: `ffmpeg -i joined.mts -c:v libx264 -crf 20 -c:a aac output.mp4`.

基于播放列表

AVCHD 播放列表文件（.mpls 在 BDMV/PLAYLIST/ 中）定义了分割文件之间的关系。AVCHD 识别软件（Premiere、Final Cut）自动读取播放列表，将分割录制呈现为单个剪辑。将 BDMV 文件夹导入编辑器，软件内部处理连接。导出组合结果。这保留了所有元数据和时间信息，而手动连接可能会丢失。

验证连续性

在合并文件后，观看过渡点以确认无缝播放。摄像机在录制中间分割的情况应该是透明的。如果您在边界处看到帧故障或音频同步问题，文件可能来自不同的录制，而不是连续捕获。检查时间戳 - 连续录制具有顺序时间码，单独录制之间有间隙。只连接真正连续的分割，而不是恰好有顺序编号的单独剪辑。

{faq_8_web_title}

{faq_8_web_desc}

连接恢复了摄像机的连续录制，消除了 FAT32 的人为文件边界。适当的工具使这一过程无缝，保留原始质量和时间。

AVCHD 和 AVCHD Lite（或 AVCHD Progressive）之间有什么区别？

AVCHD Lite 是完整 AVCHD 规范的简化子集，用于预算摄像机和一些智能手机（大约 2010 年）。限制：最大 720p 分辨率（没有 1080p），比特率受限，录制选项较少。允许制造商以较低的实施成本声称“AVCHD 兼容”。文件使用相同的容器结构（.mts 在 BDMV 文件夹中）并以相同的方式转换。区别在于录制质量限制，而不是兼容性问题。AVCHD Lite 是对简化实施的营销术语。

AVCHD Progressive（后来的扩展）在原始规范中增加了真正的逐行录制模式（1080p50/60），原始规范主要支持交错。这回应了对 AVCHD 的 1080i 看起来劣于新兴的 1080p 摄像机的批评。AVCHD Progressive 提供了升级路径，同时保持与现有 AVCHD 播放器/编辑器的向后兼容性。标记为 AVCHD Progressive 的文件是最高质量的变体 - 真正的 1080p，没有交错妥协。这些文件转换为优秀的 MP4 输出，无需去交错。

For conversion purposes, variants don't matter - all use H.264 in MPEG-2 TS container. Convert AVCHD, AVCHD Lite, AVCHD Progressive identically using HandBrake or FFmpeg. Output quality depends on source resolution and bitrate, not which variant label applied. Don't worry about specification details when converting - focus on settings appropriate for source quality. Terms are historical trivia rather than practical conversion considerations.

为什么 AVCHD 使用 MPEG-2 传输流而不是 MP4 容器？

{faq_10_intro}

{faq_10_web_title}

{faq_10_web_desc}

{faq_10_professional_title}

{faq_10_professional_desc}

{faq_10_mobile_title}

{faq_10_mobile_desc}

{faq_10_raw_title}

{faq_10_raw_desc}

{faq_10_unix_title}

{faq_10_unix_desc}

{faq_10_portable_title}

{faq_10_portable_desc}

{faq_10_legacy_title}

{faq_10_legacy_desc}

{faq_10_specialized_title}

{faq_10_specialized_desc}

{faq_10_fax_title}

{faq_10_fax_desc}

{faq_10_retro_title}

{faq_10_retro_desc}

Can I edit AVCHD footage on tablet or phone?

Technically possible but impractical. Mobile editing apps (LumaFusion, KineMaster, iMovie iOS) might import AVCHD files but performance struggles with high-bitrate footage and complex container structure. Mobile devices lack processing power for smooth AVCHD playback during editing. Better workflow: convert AVCHD to mobile-friendly MP4 on computer, then edit on tablet/phone. Or use cloud-based editing (WeVideo, Clipchamp) where servers handle heavy processing, mobile device just controls interface.

Storage and transfer challenges: AVCHD's BDMV folder structure doesn't transfer nicely to mobile. iOS file system hides folder complexity; Android makes it visible but confusing. Apps expect single video files, not folder hierarchies. Must convert AVCHD to standalone MP4 before mobile editing makes sense. Use computer as intermediate step: import AVCHD, convert to MP4, sync to mobile for editing. Attempting AVCHD on mobile creates frustration without benefit.

Future perspective: mobile editors will likely never support AVCHD well because format is obsolete. Development effort goes toward current formats (MP4, HEVC, ProRes). AVCHD is legacy format from deceased hardware ecosystem. Converting to modern format is migration to sustainability, not workaround. Accept that mobile editing requires mobile-appropriate formats. AVCHD belongs to desktop workflow era, not mobile-first era. Adapt content to workflow rather than forcing outdated formats into modern tools.

What audio formats does AVCHD support and how do they convert?

AVCHD supports three audio formats: Dolby Digital AC-3 (most common), linear PCM (uncompressed, high-end models), and MPEG-2 AAC (rare). Consumer camcorders typically use AC-3 stereo or 5.1 surround. AC-3 compresses audio to 192-384 kbps for stereo, 384-640 kbps for 5.1. High-end professional cameras might offer PCM (uncompressed, large files). Check camera specs or use MediaInfo to identify audio codec in specific file.

Converting AC-3 to MP4: can stream copy (keep AC-3) but compatibility varies - some devices don't play AC-3 in MP4. Better to convert to AAC for universal compatibility: `ffmpeg -i input.mts -c:v libx264 -c:a aac -b:a 192k output.mp4`. AAC at 192 kbps for stereo is transparent quality for camcorder audio. For 5.1 surround, use 384-512 kbps AAC or keep AC-3 if target devices support it: `-c:a copy` preserves original audio. Test playback on target devices before batch conversion.

PCM audio converts without loss of quality but requires transcoding (MP4 doesn't support PCM directly). Convert to FLAC (lossless in MKV) or high-bitrate AAC (near-lossless in MP4): `ffmpeg -i input.mts -c:v libx264 -c:a flac output.mkv` for lossless archival, or `-c:a aac -b:a 320k output.mp4` for high-quality lossy. For most users, AAC 192 kbps is sufficient - camcorder microphones aren't audiophile-grade so extreme audio bitrates waste space without audible benefit. Match audio quality to source capabilities.

How do I handle AVCHD files with corrupted BDMV structure?

{faq_13_answer_p1}

{faq_13_answer_p2}

{faq_13_answer_p3}

Why do some AVCHD files show wrong duration or refuse to seek?

Index corruption or missing clip information files cause seeking problems. AVCHD uses separate .clpi (clip information) files storing frame-accurate timing data. If .clpi file is missing or corrupted, software can't seek accurately - shows wrong duration, jumps unpredictably during scrubbing, or won't seek at all. .clpi files are in BDMV/CLIPINF/ folder parallel to video files in STREAM/. Missing clip info is recoverable - rebuild index from video file.

Rebuilding index with FFmpeg: `ffmpeg -i input.mts -c copy -map 0 reindexed.mts` forces re-indexing while copying streams without transcode. Resulting file has rebuilt index allowing proper seeking. Or use Avidemux: open file, save with copy streams (Audio and Video → Copy), which rebuilds index. HandBrake rebuilds index automatically during conversion. VLC can play without proper index but playback might be imperfect.

Prevention: always copy complete BDMV structure, not just .mts files. Clip info, playlists, metadata ensure proper functionality. If selective copying necessary (space constraints), at minimum copy STREAM/ and CLIPINF/ folders together. PLAYLIST/ folder optional for basic playback but needed for advanced features. Complete structure preservation is simplest approach avoiding index and seeking problems.

What lessons does AVCHD teach about designing consumer video formats?

Feature-driven design can hurt usability - AVCHD's Blu-ray compatibility, playlist system, metadata structure were sophisticated features nobody actually used. Complexity added no value for typical users who wanted simple video files they could drag and drop. Design decisions optimized for theoretical use cases (burning Blu-rays) rather than actual behavior (uploading to computer). Lesson: observe real usage patterns, design for what users actually do, not what engineers imagine ideal workflow. Simplicity often beats capability.

Hardware ecosystem dependencies create fragility - AVCHD succeeded during camcorder era but had no path beyond that hardware. Format tied to specific device category rather than use case (recording video). When smartphones disrupted camcorders, AVCHD became obsolete despite being technically fine. Formats should be platform-agnostic and use-case-focused rather than device-specific. MP4's survival across phones, cameras, computers, web demonstrates importance of vendor neutrality and platform flexibility.

Reliability engineering matters for consumer devices - AVCHD's Transport Stream container choice prioritized error resilience for consumer recording devices. This was correct decision valuing data preservation over efficiency. Modern MP4-based cameras rely on improved reliability (better memory cards, robust file systems) but AVCHD's defensive approach was prudent for mid-2000s technology. When designing for consumer recording, engineer for failure scenarios - interrupted recordings, card errors, battery deaths. AVCHD got this right even though format ultimately became obsolete for other reasons. Reliability focus remains relevant lesson for any device capturing irreplaceable content.