M2TS to RM Converter

M2TS vs RM — Two Formats Twelve Years and a World Apart

An .m2ts is a Blu-ray or AVCHD stream: H.264 at high definition, packetised for a disc player, typically recorded by a camcorder or ripped from a disc. An .rm is RealMedia, built for streaming video over dial-up.

Converting one to the other is not a repackaging job, it is a substantial downgrade, and the interesting question is not how but what it costs you. This page lays the two formats side by side, then shows the settings that make the result as good as RealMedia allows.

Side-by-side Comparison

The resolution row is the one that decides everything else. RealVideo 1.0 and 2.0 are derived from H.263, and the encoder genuinely fails on large frames — we measured a hard failure at 1408 × 1152 with "Error while opening encoder". The pipeline caps output at 640 × 480 precisely so the job completes instead of erroring.

Getting the Aspect Ratio Right Is the Whole Game

The cap is applied to width and height independently, so it does not preserve your 16:9 shape. Measured outcomes from a 1920 × 1080 M2TS:

Dimensions round down to a multiple of 16 because RealVideo codes in 16-pixel macroblocks — that is why 360 becomes 352, and why a 1080-line frame would become 1072 if the cap were not already in the way.

When to Pick M2TS

• You are keeping AVCHD camcorder footage or a Blu-ray rip at its native quality and resolution.
• The destination is a disc player, a television or a hardware media player that expects BDAV framing.
• You want to preserve multichannel AC-3 or DTS audio, which RealMedia has no place for.
• You may want to edit later — H.264 at 1080p gives an editor something to work with, 640 × 480 RealVideo does not.

When to Pick RM

• A specific legacy application, kiosk, or archival system demands a .rm file and will not take anything else.
• You are reproducing an existing RealMedia workflow rather than starting one.
• Extreme file size matters more than any aspect of picture quality.

If none of those apply, M2TS to MP4 keeps your full resolution in a container that plays everywhere, and it is what almost everyone converting AVCHD footage actually wants.

How to Convert M2TS to RM

1. Upload Your M2TS File: Drag the .m2ts onto the drop zone or click "Add Files". AVCHD footage is large, so trimming first with the Trim group keeps the upload manageable.
2. Set Video Resolution to 480p: Under Video resolution choose Preset Resolutions → 480p. Leaving Keep original selected is what produces the squashed 640 × 480 result.
3. Set Audio Codec to AAC: The preselected audio value on RealMedia targets is genuinely ambiguous, and the RealAudio 1.0 entry is substituted with AC-3 before encoding — so choose AAC explicitly.
4. Convert and Download: Click Convert. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours. No sign-up, no watermark.

Frequently Asked Questions

Can I keep 1080p when converting M2TS to RM?

No. RealVideo 1.0 and 2.0 are the only RealVideo codecs anything can still encode, both descend from H.263, and both refuse frames much above standard definition. The 640 × 480 cap exists to keep the job from failing. 848 × 480 via the 480p preset is the largest correctly-shaped frame you can get.

Why is my picture squashed when I did not change anything?

Because Keep original hands the source dimensions to a cap that clamps each axis separately: 1920 becomes 640 and 1080 becomes 480, which turns 16:9 into 4:3. Choosing Preset Resolutions → 480p instead scales proportionally and gives 848 × 480.

Does the AVCHD audio survive?

Not as it was. AVCHD typically carries AC-3 or occasionally DTS, and the server always re-encodes rather than copying streams through. Multichannel audio is downmixed into whatever the RealMedia target holds. AAC is the best-sounding of the three options on this page.

Should I use RealAudio 1.0 to make it a "proper" RealMedia file?

It will not do what you expect. The pipeline substitutes AC-3 for that selection before the encode runs, so choosing it does not produce a RealAudio track. Since it also cannot make the file period-correct, there is no reason to prefer it over AAC.

Will my 1080i camcorder footage come out combed?

Yes, if there is motion in it. There is no deinterlacing anywhere in this pipeline — no yadif, no bwdif, nothing. Both fields of an interlaced frame are captured milliseconds apart and both survive into the output. Deinterlace in an editor before uploading if the artefact matters at 480 lines.

Why does the Max bitrate box under Constraint Quality have no effect?

Because RealVideo 1.0 and 2.0 accept only simple bitrate or quantiser control, so the pipeline strips the VBV rate-control parameters Constraint Quality would set. The control renders because the group is shared with every other video target. Use Constant Bitrate or Specific file size to set a real budget.

Is there a bitrate ceiling I should know about?

Yes, an indirect one. The RealMedia muxer allows at most 64 KB per packet, and the pipeline caps the video bitrate to stay inside that — scaled by frame rate, it works out around 5 Mbit/s at 30 frames per second. At 640 × 480 with RealVideo 1.0 you will never come close to it, so in practice it never bites.

What is the difference between .rm and .rmvb?

RealMedia streams are normally constant bitrate; RMVB is the variable-bitrate variant of the same container, which spends bits where the picture needs them. Everything on this page about the 640 × 480 cap and the codec choices applies equally to M2TS to RMVB — the difference is purely in how the bitrate is allocated.

Why does my .m2ts open here when some players reject it?

Because M2TS uses 192-byte BDAV packets with the sync byte at offset 4 rather than offset 0, and some tools only understand plain 188-byte transport packets. The decoder here handles both framings. That difference is also why renaming an .m2ts to .ts usually does not make a stubborn player accept it — the bytes are laid out differently, not just named differently.