Extract Audio from DVR to AIFC — Free Online Tool
Extract audio from DVR surveillance or broadcast recordings and save it as an AIFC file with lossless PCM encoding. This tool strips the video stream entirely and converts the AAC audio track from your DVR file into 16-bit big-endian PCM (pcm_s16be), producing a professional-grade AIFC file compatible with pro audio workflows on macOS and Apple platforms.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your DVR file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
DVR files typically store video using H.264 (libx264) and audio using AAC, a lossy compressed codec. During this conversion, the video stream is completely discarded using the -vn flag. The AAC audio is then decoded from its compressed form and re-encoded into pcm_s16be — a 16-bit big-endian uncompressed PCM format — and wrapped in the AIFC container. AIFC is Apple's compressed/extended AIFF format, but in this case we're writing uncompressed PCM into it, which means the output audio is lossless from this point forward, though the original AAC compression means some fidelity was already lost before the DVR was ever created. The result is a clean, flat audio file with no video overhead, suitable for editing, archiving, or analysis in professional audio tools.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine that this tool runs in your browser via WebAssembly (FFmpeg.wasm). The same command can be run on your desktop if you have FFmpeg installed locally. |
-i input.dvr
|
Specifies the input DVR file. FFmpeg will demux this proprietary digital video recorder container to access its internal video (typically H.264) and audio (typically AAC) streams for processing. |
-vn
|
Disables video output entirely, instructing FFmpeg to ignore the H.264 video stream from the DVR file. Since the goal is audio extraction, this flag ensures no video data is written to the AIFC output, which is a purely audio container. |
-c:a pcm_s16be
|
Sets the output audio codec to 16-bit signed big-endian PCM — the standard uncompressed audio format for AIFC files on Apple platforms. This decodes the AAC audio from the DVR source and re-encodes it as raw, uncompressed samples, making the output lossless from this point forward. |
-b:a 128k
|
Specifies a target audio bitrate of 128 kilobits per second. For pcm_s16be this parameter has no functional effect since uncompressed PCM has a fixed bitrate determined by its sample rate and channel count, but it is passed as part of the tool's standard parameter set without causing errors. |
output.aifc
|
Specifies the output filename and tells FFmpeg to write an AIFC container. The .aifc extension signals FFmpeg to use the AIFF-C muxer, which wraps the pcm_s16be audio stream in Apple's extended AIFF format, compatible with Logic Pro, Pro Tools, and other professional audio applications. |
Common Use Cases
- Extracting audio from a DVR security camera recording to use as evidence, where a clean uncompressed AIFC file is required by forensic or legal workflows on macOS
- Pulling broadcast audio captured by a DVR to import into Logic Pro or Pro Tools for professional post-production editing, which natively supports AIFC/AIFF formats
- Archiving the audio track from a DVR-recorded television broadcast in a lossless PCM container so it can be re-encoded later to any format without generation loss
- Isolating spoken audio from a surveillance DVR clip for transcription or voice analysis, removing the video stream to reduce file size and simplify processing
- Extracting audio commentary or on-air talent audio from a DVR broadcast capture for use in podcast or radio production workflows that require AIFF-family files
- Separating audio from a DVR recording to analyze sound levels or sync audio with a separately recorded video source in a non-linear editing system like Final Cut Pro
Frequently Asked Questions
The AIFC output uses uncompressed pcm_s16be encoding, which is lossless from the point of conversion — no further quality is lost during this process. However, the original DVR file stored audio as AAC, which is a lossy codec, so any quality reduction that occurred when the DVR originally recorded the audio is permanent. Think of it like scanning a JPEG at maximum quality: the scan itself is lossless, but the original compression artifacts remain. If your DVR used a high AAC bitrate (e.g., 192k or 320k), the perceptible quality loss is typically minimal.
DVR files store audio as AAC, a compressed codec that can reduce audio data size by 10x or more compared to uncompressed PCM. When converting to AIFC with pcm_s16be, the audio is decompressed into raw PCM samples, which takes significantly more space. For example, one minute of 128k AAC audio takes roughly 1MB, while one minute of 16-bit stereo PCM at 44.1kHz takes about 10MB. The video stream is removed, but the audio stream grows substantially in size.
AIFC is an Apple-originated format and has its strongest native support on macOS and iOS applications like Logic Pro, GarageBand, and QuickTime Player. On Windows, AIFC support is not built into the OS by default, but professional audio applications like Adobe Audition, iZotope RX, and Audacity (with the FFmpeg library installed) can open AIFC files. If Windows compatibility is a priority, consider converting to WAV instead, which uses the same PCM audio data in a universally supported container.
You can replace pcm_s16be with other codecs supported by AIFC to change the bit depth or format. For example, use -c:a pcm_s24be for 24-bit audio (better dynamic range for professional work), -c:a pcm_s32be for 32-bit integer, or -c:a pcm_f32be for 32-bit float. The command would look like: ffmpeg -i input.dvr -vn -c:a pcm_s24be output.aifc. Note that the -b:a bitrate flag has no effect on uncompressed PCM codecs — the bitrate is determined entirely by the sample rate, bit depth, and channel count.
The single-file command shown here can be adapted for batch processing using a shell loop. On Linux or macOS, you can run: for f in *.dvr; do ffmpeg -i "$f" -vn -c:a pcm_s16be "${f%.dvr}.aifc"; done. On Windows Command Prompt, use: for %f in (*.dvr) do ffmpeg -i "%f" -vn -c:a pcm_s16be "%~nf.aifc". This is especially useful for processing large DVR archives where the browser-based tool's 1GB file limit may be a constraint.
DVR files are a proprietary format and typically carry minimal standardized metadata — often just recording timestamps embedded in the container or filename rather than structured tags. AIFC supports basic metadata chunks (such as NAME, ANNO, and AUTH markers), but FFmpeg's DVR demuxer may not reliably map DVR-specific metadata into AIFC's chunk format. You should not rely on this conversion to preserve recording timestamps or camera identifiers; if that information is critical, document it separately before converting.
Technical Notes
DVR is a proprietary container format used by digital video recorders from various manufacturers, meaning its internal structure can vary between vendors and firmware versions. FFmpeg's DVR support covers the most common variants, but unusual or manufacturer-locked DVR files may require vendor software to first remux into a standard container before this tool can process them. The default audio codec in DVR recordings is AAC, and FFmpeg fully decodes AAC before writing it out as pcm_s16be in AIFC — there is no direct stream copy, which means the process involves a full decode-encode cycle even though the output is PCM. AIFC with pcm_s16be uses big-endian byte ordering, which is standard for Apple platforms and pro audio gear but is the opposite of the little-endian PCM used in WAV files; this distinction matters if you're feeding the output into custom audio processing pipelines that are byte-order sensitive. The -b:a 128k flag in the command is technically a no-op for PCM codecs (since uncompressed audio has a fixed bitrate determined by sample rate and bit depth), but it doesn't cause errors and is included for consistency with the tool's parameter structure.