Local-only · metadata comparison · bounded

Compare OBS audio tracks before and after remux

Select an original MKV or MOV and a remuxed MP4 or MOV. Analysis happens in a disposable browser worker; media files are not uploaded or stored.

Choose the local media pair

Provisional limits: 8 MiB per read, 64 MiB total across both files, 1,000 reads, and a 15-second hard deadline. A limit failure is reported as an error, never as zero audio.

No original media selected locally.

The container is recognized from parsed metadata, not its filename extension.

No remuxed media selected locally.

The parsed output container must be MPEG-4, which covers MP4 and MOV.

Choose both media files to begin.

Evidence, privacy and limitations

MediaInfo streamOrder is shown only with MediaInfo provenance. It is never presented as a ffprobe absolute index. Unknown codec profile, layout, or default values stay unknown.

Bundled extractor: mediainfo.js 0.3.8, self-hosted under BSD-2-Clause terms. Frozen references: OBS Multiple Audio Track Recording Guide (https://obsproject.com/kb/multiple-audio-track-recording-guide) and ffprobe documentation (https://ffmpeg.org/ffprobe.html). No live source is fetched by this page.

What this comparison can tell you

Why do I hear only one track?

A player may select one audio track at a time. One audible track alone does not establish that the other tracks are absent. Inspect the counts and your player or editor track selection separately.

Does matching metadata prove the audio survived?

No. Similar metadata can belong to different audio. This tool does not decode, listen to or compare audio samples, and identical track metadata can make matching ambiguous.

Can it identify microphone and game audio?

No. Track position is not an audio-role label. Roles and editor compatibility remain unverified.

Does fewer output tracks prove an OBS bug?

No. A count difference is an observation about the selected files, not a diagnosis of its cause.

Privacy

Selected files and extracted metadata remain in this browser. There is no analytics, upload, account or result storage. The page downloads its own scripts and parser; hosting infrastructure can receive ordinary page-request information. Reset clears the displayed comparison.