Convert M2TS to FLV Online Free

M2TS packet alignment before an FLV conversion

An M2TS source is Blu-ray's BDAV adaptation of MPEG-2 Transport Stream. It multiplexes picture, audio, subtitles and programme information, which makes it useful for disc delivery but fundamentally different from an FLV file. Its source records are 192 bytes long: a four-byte BDAV extra header comes before each 188-byte transport packet. The 0x47 sync byte belongs to the transport packet after that prefix. Proper alignment is necessary before the converter can read packet identifiers and reassemble elementary streams.

Convert M2TS to FLV only for a system that genuinely accepts Flash Video. The operation demuxes a selected programme, chooses its video and audio streams, decodes or transcodes them to codecs suitable for the FLV target, and writes time-stamped FLV tags. Renaming a file does none of this. It cannot turn a Blu-ray PID map into FLV tags, nor can it make an M2TS H.264 or audio bitstream automatically obey a legacy FLV player's codec limitations.

Following PAT, PMT and timestamps to source media

The Program Association Table, or PAT, maps a programme number to the PID where its Program Map Table is carried. The PMT enumerates the elementary stream PIDs belonging to that programme and identifies the programme-clock PID. A source can therefore include several video angles or audio languages. Demuxing must follow the selected PMT entries; it cannot infer intent merely from a stream's position in the file.

Select one video and the intended audio PID for a straightforward FLV output. If a disc contains commentary, descriptive audio or a dubbed language, those are independent source choices. FLV does not retain the original PID numbers or the complete programme map, so create separate files where those choices need to remain available. Subtitle streams and Blu-ray navigation are outside the ordinary FLV audio/video tag model and should be retained in the M2TS master instead.

PCR synchronizes a transport programme, while PTS marks presentation timing for access units. Captures and joined segments can have discontinuities. An FLV tag timestamp must be derived from a coherent output timeline; it should not convert a reset into an accidental long blank interval. When output sync fails at a source splice, investigate source timing and packet integrity. Adding arbitrary audio silence or repeating video frames masks the diagnostic evidence rather than restoring original media.

FLV headers, tag types and timestamp representation

An FLV file starts with the three bytes FLV, followed by a version, type flags indicating whether audio and video tags are present, and a data-offset field that is normally nine for version 1. A previous-tag-size field follows the header and each tag. Tags are self-contained time-stamped units: their headers carry a tag type, data size, timestamp and stream identifier. The common tag types are audio (8), video (9) and script data (18).

For AVC/H.264 carried in FLV, an AVC video packet supplies a payload related to AVC video data and needs configuration information appropriate to the stream. For AAC, the audio-tag header identifies AAC and the stream needs its decoder configuration as well as raw AAC payload units. “H.264 plus AAC” is therefore not just a label: both the FLV packet conventions and the actual target player's support must agree. A source H.264 or AAC stream may still need remux-specific configuration or a transcode to meet a legacy client.

An FLV script-data tag can carry Action Message Format data. The usual metadata object is named onMetadata, and it can describe properties such as duration, dimensions, frame rate, data rates, codecs, keyframes and file positions. This metadata assists playback and seeking but is not a substitute for valid audio/video tags or decodable media. Rebuild it from the output, not from an unverified M2TS file-size estimate.

The FLV tag header has a 24-bit data-size field and a timestamp whose lower portion is stored with an extension byte, allowing time to be carried separately from the source transport packets. The stream identifier field is normally zero in conventional FLV files. Each tag is followed by a previous-tag-size value, which helps a reader navigate the tag sequence. This contrasts with TS continuity counters and PID routing: a converter must write FLV's own grammar and timestamps, not transplant M2TS packet headers into a new filename.

M2TS transport packets compared with FLV media tags

Codec and compatibility decisions for a legacy FLV target

FLV has strong historical associations with Flash playback, so compatibility depends on the actual consumer—not on whether an FLV file can be produced. Some targets expect AVC video and AAC audio; older ones may expect different Flash-era codecs. Establish the target player's accepted video profile, audio rate, channel count and resolution before encoding. A modern general-purpose player may open FLV while the required legacy system rejects a high-profile AVC stream or an unsupported audio configuration.

Transcoding changes the media representation. Scaling alters pixels, changing frame rate alters cadence, downmixing alters the source mix and lossy video/audio encodes add a generation step. If compatible streams can be rewrapped, quality can be preserved, but stream compatibility and correct FLV configuration still must be proven. If transcode is needed, use settings chosen for the receiver and keep the original M2TS for preservation and future conversions.

Keyframe placement affects seeking. The metadata's keyframe positions are useful only when they point to actual decodable video access points. Test a seek near several scenes, not just start-to-finish playback. Incorrect metadata may make a player appear to have a broken duration or land on a blank image even though tags exist in the file.

Audio has its own target constraints. FLV audio-tag fields express sound format, rate, sample size and channel type, but AAC's real configuration must still be conveyed in the AAC-specific payload form and supported by the player. A number displayed in a tag header should not be mistaken for a universal declaration that the source's exact sample rate, multichannel layout or codec features are usable. Test an actual complex scene as well as spoken dialogue, because decoder limitations can appear only with particular source content.

Validating FLV playback after a Blu-ray-source conversion

Verify the exact source selection first: picture, language, audio role, duration and intended aspect ratio. Then test start, a mid-file seek, a scene transition and end in the actual FLV consumer. A wrong language or commentary means the source PID was chosen incorrectly. Audio leading or lagging after a join suggests timeline construction or source PTS discontinuity. A blank image after seek can arise from keyframe/index metadata or codec-profile incompatibility.

Distinguish source evidence from target effects. If a defect exists at the same moment in native M2TS playback, it may be in the capture. If it appears only after conversion, review selected codecs, AVC/AAC configuration, tag timestamps and transcode settings. Retain conversion notes and the M2TS file until the target application passes its complete workflow; FLV does not contain the unselected Blu-ray programme material needed for a later correction.

M2TS to FLV questions for target-specific exports

Can an FLV preserve all tracks in a Blu-ray M2TS?
Not as the original multiplex. Select the required video and audio; retain M2TS for alternate languages, subtitles and disc programme context.

What does onMetadata do in an FLV?
It is usually AMF script data describing output properties such as duration, dimensions, codecs, keyframes and file positions. It helps readers but cannot repair invalid media tags.

Does M2TS-to-FLV keep source quality unchanged?
Only a compatible rewrap avoids codec re-encoding. Many legacy FLV targets require specific codecs or configurations, which can require a lossy transcode.

Why does FLV video seek to a blank frame?
The metadata keyframe data may be wrong, the player may not support the video configuration, or the target point may not provide a decodable access unit. Test both metadata and codec compatibility.

Why is audio out of sync only after conversion?
Check source PTS discontinuities, FLV tag timestamp generation and the selected codec configuration. The original PCR/PTS timeline does not automatically transfer to FLV tags.

Can I use FLV as my preservation copy?
It is generally a target-specific legacy delivery container, not a replacement for a Blu-ray M2TS master. It discards programme-map context and often requires codec changes; retain the source for future extraction or remastering.