DVR to RM Converter

DVR to RM: Read This Before You Run It

RealMedia is RealNetworks' streaming container from the era when a 56k modem was the constraint that shaped everything, and the RealVideo codecs that can still be written today are the two oldest ones in the family. That has consequences for your recording that are much larger than "the file gets smaller", and the defaults will not warn you about them.

This page is a troubleshooting guide first and a how-to second, because almost everybody who runs this conversion at the default settings gets a result they did not expect.

The Headline: Your Frame Will Be At Most 640 × 480

RealVideo 1.0 and 2.0 are derived from H.263, and the encoders refuse frames much beyond standard definition. We bisected the limit: an rv10 encode at 1280 × 720 succeeds, and at 1408 × 1152 and above it fails outright with "Error while opening encoder — maybe incorrect parameters such as bit_rate, rate, width or height."

To keep the conversion from failing, the pipeline caps RealVideo output at 640 × 480. The cap is applied to width and height independently, which is what catches people out — it does not preserve your aspect ratio. Here is what a 1920 × 1080 source produced under each resolution setting, measured:

Do not leave this on Keep original if your source is widescreen. Choosing 480p from Preset Resolutions is a one-click fix that gives a properly proportioned 848 × 480 picture, which is both larger and correctly shaped compared with the default.

The dimensions are also rounded down to a multiple of 16, because RealVideo works in 16-pixel macroblocks. That is why 360 becomes 352 and 1080 would become 1072 — expect the odd row or two to be trimmed.

How to Convert DVR to RM

1. Upload Your DVR File: Drag the .dvr onto the drop zone or click "Add Files". A .dvr is identified by its contents rather than its extension, so recordings from most set-top boxes and PVRs open normally.
2. Set Video Resolution to 480p: Under Video resolution pick Preset Resolutions → 480p rather than leaving Keep original selected. This is the single most important setting on the page.
3. Set the Audio Codec Explicitly to AAC: Do not leave the audio to the default — the reasons are in the next section, and they are not obvious.
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.

The Audio Codec Dropdown Has Two Traps

The Audio Codec group on this page offers AAC, AC3 and RealAudio 1.0. Both traps concern that third entry.

First, the preselected value is genuinely ambiguous. Two different configuration rules both claim the audio setting on RealMedia targets, and which one wins depends on the order things resolve in — one of them selects RealAudio 1.0, the other selects AAC. Because we cannot honestly tell you which one your session will land on, set it yourself.

Second, and more surprising: choosing RealAudio 1.0 does not give you RealAudio. The pipeline substitutes AC-3 for it before the encode runs. So the one option on the dropdown that would make the file a genuine period-correct RealMedia stream is the one that quietly does something else.

Taken together, that leads to a simple recommendation: pick AAC. It is the best-sounding of the three, it is unambiguous, and it is what you get anyway if the other default happens to win.

Common Errors and How to Fix Them

• "Everyone looks short and wide / tall and thin" — Keep original clamped 1920 × 1080 to 640 × 480 independently on each axis. Re-run with Preset Resolutions set to 480p.
• "I asked for 1080p and got something small" — every preset at or above 480p collapses to the same 480-pixel height, because the codec's ceiling is enforced after your choice. There is no way to get an HD RealMedia file out of RealVideo 1.0 or 2.0.
• "The Max bitrate box under Constraint Quality does nothing" — it genuinely does nothing here. RealVideo 1.0 and 2.0 only accept simple bitrate or quantiser control, so the pipeline strips the rate-control parameters that Constraint Quality would set. Use Constant Bitrate or Specific file size instead.
• "My bitrate got reduced without asking" — the RealMedia muxer has a 64 KB per-packet limit, and the pipeline caps the video bitrate to stay under it, scaled by frame rate. At 30 frames per second that ceiling works out around 5 Mbit/s, which is far more than RealVideo 1.0 will use anyway.
• "The audio is terrible" — you probably ended up on the RealAudio path. Set Audio Codec to AAC explicitly.
• "Moving edges are combed" — broadcast recordings are frequently interlaced and there is no deinterlacing anywhere in this pipeline. Deinterlace before uploading if it matters.

When This Doesn't Work

RealMedia support has been dwindling for two decades, and part of the reason is that most of the family can be read but not written. The available codecs break down like this:

Modern players built on ffmpeg — VLC, mpv and their relatives — will open what this produces, because they can decode RealVideo 1.0 and 2.0. Actual RealPlayer is a different question: the audio track in your file will be AAC or AC-3 rather than a RealAudio codec, and that combination is not what the format ever standardised.

The honest position is that a .rm from any modern converter is a compatibility artefact, not a faithful period file. If your requirement is "something a specific old device or piece of software will accept", test one short clip before converting a library. If the requirement is anything else, DVR to MP4 keeps your full resolution, sounds better and plays everywhere. If you specifically need RealMedia with variable bitrate, DVR to RMVB is the sibling format.

Frequently Asked Questions

Why can I only choose RealVideo 1.0 and 2.0 and not 3.0 or 4.0?

Because only those two have encoders. The toolchain can decode RealVideo 1.0, 2.0, 3.0, 4.0 and 6.0, but it can only encode the first two. RV10 is based on H.263 and RV20 on H.263+; the later RealVideo codecs are H.264 precursors and no open-source encoder implements them.

Is 640 × 480 really the maximum, or can I push past it?

It is the maximum this page will produce. The limit exists because the encoder genuinely fails above standard definition — we measured a hard failure at 1408 × 1152 — and clamping is what stops the job erroring out. Choosing 480p from Preset Resolutions gives you the largest correctly-shaped frame available, 848 × 480.

What should I set the audio codec to?

AAC. The preselected value is ambiguous between two configuration rules, and the RealAudio 1.0 entry is substituted with AC-3 before encoding rather than producing a RealAudio track. Setting AAC explicitly removes both problems and gives the best-sounding result of the three.

Why does Constraint Quality have a Max bitrate box that is ignored?

The box renders because the control group is shared across every video target on the site. RealVideo 1.0 and 2.0 cannot use the VBV rate-control parameters that Constraint Quality relies on, so the pipeline removes them before the encode. It is a genuine dead end on this page — use Constant Bitrate or Specific file size for a real budget.

Will the RM file play in VLC?

Yes. VLC and anything else built on ffmpeg will decode RealVideo 1.0 and 2.0 and will handle the AAC or AC-3 audio track without complaint. It is legacy RealPlayer, and hardware that expected genuine RealAudio, where the mismatch shows up.

How does Constant Quality behave on this page?

It runs on a 1–31 quantiser scale where lower is better — the opposite direction to H.264's CRF, despite being labelled the same way. It does emit a real setting and does change the output, so it is a usable control; just remember that 1 is the best quality and 31 the worst.

Can I trim the recording instead of converting the whole thing?

Yes. The Trim group takes a start time and a duration, in seconds or as HH:MM:SS.sss. On long PVR recordings trimming first is much faster than converting everything, and it avoids uploading footage you do not need.

Does the .dvr extension affect what gets read?

No. Detection is done by reading the file, not its name. We wrote an MPEG-2 transport stream, named it .dvr and it was correctly identified as mpegts with its H.264 and AC-3 streams intact. If a .dvr will not open, the payload is something the decoder cannot handle rather than a naming problem.

Is any of this lossless?

No. The server always re-encodes — there is no path that copies your original video or audio through untouched. Combined with the 640 × 480 ceiling and RealVideo 1.0's age, this conversion should be treated as a deliberate downgrade for compatibility, never as a way to repackage a recording.