Convert MTS to AAC Online for Free

Convert MTS to AAC by Choosing the Correct Camera Audio Programme

Convert MTS to AAC when the required delivery is audio-only and the intended soundtrack has been identified. MTS is commonly an AVCHD-associated MPEG transport-stream clip carrying video and audio. It can contain more than one audio component, and the first audio PID is not automatically the required language, mix, commentary, or camera recording. AAC output discards the picture, so make the programme choice before extraction.

AAC is an audio coding family, not a single universal file representation. A destination may expect ADTS-framed AAC, another raw or ADIF-style AAC form, and another AAC stored in an M4A/MP4 container. The National Archives description of ADTS notes a sequence of frames with header data followed by compressed audio. Confirm the real receiver’s required framing and suffix rather than calling every .aac file interchangeable.

Retain the MTS and, for camera material, preserve the full original AVCHD card hierarchy when it matters. AAC is a new delivery and does not retain video, playlist relationships, source timing tables, visual evidence, or all source metadata.

MTS PAT PMT and Audio PID Inspection Comes Before AAC Encoding

Transport streams use fixed 188-byte packets. The packet header has a 13-bit PID. The Program Association Table identifies programme-map locations and the Program Map Table identifies which PIDs make up each programme, including its audio. Do not choose audio by filename or decode order alone: inspect PMT component entries and the resulting stream properties.

Record selected PID, codec, language where present, sample rate, channel layout, duration, offset, and bitrate mode. AVCHD recordings commonly use AC-3 or LPCM audio, but MTS itself is transport-stream packaging, not a guarantee of a particular camera codec. Some software has explicit AC-3 support constraints, which is one reason an audio-only AAC derivative may be requested. The source still needs a usable decoder before conversion.

Compare a known source event near beginning, middle, and end while listening to the selected stream. This verifies that you extracted the intended programme and catches source discontinuities or silence before AAC settings are blamed. Preserve source details when picture-linked time or edit context matters.

PES PTS and AAC Boundaries Need an Audio-Only Timeline Check

Audio access units reach a transport stream through PES packets. PES can carry PTS and DTS information, while the programme clock and packet timing establish presentation context. When video is removed, compare audio against identifiable source-video events: a clap, spoken word at a cut, door close, or music entrance. This shows whether the selected MTS audio starts at the intended point and remains aligned with the source programme concept.

An output duration report cannot prove correct boundaries. Decoder priming, encoder delay, trimming, discontinuities, and an unintended silence rule can affect the start and tail. Listen to the first sound, a mid-clip transition, and the final intended sound. If trimming, normalisation, fade work, loudness adjustment, or a downmix is requested, state it as an additional transform rather than implying an untouched audio extraction.

If the MTS is part of a multi-file or spanned camera recording, preserve the original card/package and validate the intended continuous programme before extracting audio. A single clip boundary may not be the logical recording boundary.

AAC Profile Framing and Decoder Configuration Must Match the Receiver

AAC profile, sample rate, channels, bitrate, and framing affect compatibility. ADTS puts synchronization and stream details in repeated frame headers; a container-based receiver may instead need AAC configuration stored at its container level. These forms are not interchangeable merely because the encoded essence is called AAC. Name the target app, device, ingest system, or archive requirement before choosing output representation.

FFmpeg documentation describes AAC as its native default AAC encoder and treats bitrate, channel layout, and sample format as per-stream choices. Its examples make the output sample rate and layout explicit. Use that discipline even when no command line is involved: do not let an unexamined layout guess turn a 5.1 source into a mislabeled or unintended stereo result.

If MTS audio is already AAC in the exact framing and target constraints required, a verified stream copy may be possible. Otherwise decode and encode. Re-encoding is usually lossy: a higher bitrate can manage fresh artefacts but cannot reconstruct information already removed from the source codec.

Channel Layout Sample Rate and Downmix Decisions Need Listening Evidence

Channel count is not channel layout. Stereo, 5.1, and a custom arrangement have different speaker roles and ordering. Record the source layout, decide whether it will be preserved or downmixed, and test dialogue, music balance, ambience, and phase-sensitive material in the intended listening environment. A valid AAC stream can still carry the wrong practical mix.

Resampling may be needed for a specific target, but it is not a quality upgrade. Check supported output combinations and listen to speech consonants, high-frequency material, sustained tones, and transient attacks after conversion. Changing sample rate or bitrate should be justified by target support or delivery constraints, not by a generic preference.

Keep the original MTS accessible. If another receiver wants a different AAC framing, stereo mix, sample rate, or bitrate, create it from the source rather than encoding a previous AAC variant and compounding loss.

MTS Audio Selection and AAC Release Evidence Compared

Questions Before Releasing AAC From an MTS Clip

Does AAC retain the MTS video?
No. AAC is audio-only; retain the source clip and any needed visual or camera-card context.

How do I identify the right audio?
Inspect PAT/PMT programme components and listen to each candidate PID, language, mix, and offset.

Should the AAC file use ADTS?
Only when the target accepts or requires it. Other receivers need another framing or an AAC container.

Why did dialogue or surround balance change?
Review source layout, channel mapping, and any explicit or implicit downmix.

Can higher bitrate restore camera audio quality?
No. It limits new AAC loss but cannot restore detail removed by source coding.

What is the acceptance test?
Probe output, listen at three source landmarks and the end, and play it in the named receiver.

Approve MTS-to-AAC output only after the selected PID, requested AAC representation, sample rate, channel layout, audible quality, boundaries, and receiver have been checked. Record the accepted file, target version, source probe, settings, and listening result so an alternate delivery can be made from the original MTS.

If a target rejects the result, change one recorded factor—framing, profile, rate, layout, bitrate, or selected source programme—and repeat the same listening landmarks. Do not re-encode the rejected AAC repeatedly, because that hides the cause and adds another lossy generation.

For AVCHD-originated recordings, distinguish a standalone MTS delivery from the camera-card acquisition package. The clip may be useful for an audio extraction, yet the full original hierarchy can hold playlist and clip-information context that explains spans, recorded duration, or import behaviour. Preserve that package before any conversion. The AAC file should be treated as an access or delivery derivative, not as an archival replacement for the camera original.

A detailed acceptance note names the original clip, selected programme and audio PID, source codec and layout, output profile/framing, sample rate, bitrate, layout or downmix policy, target application or device/version, and results at start, middle, end, and a late listening point. Include the accepted filename or checksum. Those facts let another operator identify whether a later failure came from AC-3/LPCM decoding, the wrong source component, AAC framing, receiver support, or a changed delivery setting.

Transfer can be part of the test. If the AAC is to be copied to removable media, uploaded to an ingest service, or opened by a mobile application, verify that delivered copy rather than only the local working file. A service may change metadata, reject a framing representation, or make a secondary derivative. When there is a new target requirement, return to the retained MTS and create an individually tested AAC delivery with that requirement recorded.

Keep the source clip and the verified acceptance note together for future variants and recheck each requested receiver independently. For ADTS delivery, a header precedes each compressed AAC frame; verify that the target actually accepts this repeated frame-level representation reliably in practical playback.