Convert MPG to TS

Why Convert MPG to TS?

Converting MPG to TS transforms your video from MPEG Program Stream to MPEG Transport Stream — two related but fundamentally different multiplexing approaches within the same MPEG-2 standard. Program Stream (MPG) is designed for error-free sequential media like DVDs, where data integrity is guaranteed by the storage medium. Transport Stream (TS) is designed for broadcast and streaming environments where packet loss is expected, using fixed-length 188-byte packets with synchronization bytes and error correction to recover gracefully from transmission errors.

The primary reason to convert MPG to TS is to prepare content for broadcast, IPTV, or HLS streaming infrastructure. Television stations, cable operators, and IPTV providers require Transport Stream input for their encoding and distribution chains. If you have MPEG-2 content as Program Stream files (from DVD rips, legacy captures, or archival recordings), converting to TS makes it compatible with broadcast playout systems, satellite uplink equipment, and IPTV head-ends that only accept Transport Stream input.

HLS (HTTP Live Streaming) — the dominant adaptive bitrate streaming technology used by Apple, Netflix, and most streaming services — is built on MPEG Transport Stream. HLS segments are essentially short TS files (typically 6-10 seconds each) served over HTTP. Converting MPG to TS is the first step in an HLS packaging workflow: the TS file can then be segmented into HLS chunks with an M3U8 playlist for delivery to web browsers, mobile apps, and smart TVs with adaptive quality switching.

When the source MPG contains MPEG-2 video, the conversion to TS can often be a lossless remux — the video and audio elementary streams are repackaged from Program Stream packets into Transport Stream packets without any re-encoding. This preserves 100% of the original quality and completes very quickly. For modern broadcast requirements that demand H.264 or H.265 video inside the Transport Stream, full re-encoding is needed but delivers dramatically better compression efficiency than the original MPEG-2.

Key Benefits of Converting MPG to TS:

• Broadcast Ready: Transport Stream is the mandatory format for DVB, ATSC, and ISDB television
• Error Resilience: 188-byte packet structure with sync bytes enables recovery from transmission errors
• HLS Foundation: TS is the segment format for HTTP Live Streaming (adaptive bitrate)
• Lossless Remux: MPEG-2 streams can be repackaged without re-encoding (zero quality loss)
• Multi-Program: Multiplex multiple video/audio programs in a single transport stream
• IPTV Compatible: Standard input format for IPTV head-ends and streaming servers
• Blu-ray Ready: M2TS variant used for Blu-ray disc authoring

Practical Examples

Example 1: Preparing DVD Content for IPTV Distribution

Scenario: A hotel chain is building an IPTV system that streams promotional and entertainment content to guest room TVs. Their existing content library consists of DVD-sourced MPG files that need to be converted to Transport Stream for the IPTV encoder/multiplexer.

Source: welcome_video_resort.mpg (1.2 GB, 720x480, MPEG-2 6 Mbps, AC-3 stereo)
Conversion: MPG → TS (lossless remux for IPTV)
Result: welcome_video_resort.ts (1.25 GB, same MPEG-2 video, TS packets)

IPTV deployment workflow:
1. Remux MPG Program Stream to TS Transport Stream (lossless)
2. Assign PID values for video, audio, and PMT tables
3. Add PAT/PMT tables for IPTV multiplexer identification
4. Load into IPTV middleware for scheduled channel playout
5. Multiplexer combines with other programs into multi-program TS
✓ IPTV head-end accepts Transport Stream input natively
✓ Zero quality loss — MPEG-2 streams copied bit-for-bit
✓ PAT/PMT tables enable proper channel identification
✓ Content plays on all guest room set-top boxes

Example 2: Creating HLS Stream from Broadcast Archive

Scenario: A public broadcaster is launching a video-on-demand web platform for its archive of 50,000 hours of MPEG-2 Program Stream recordings. The platform uses HLS for adaptive streaming, requiring conversion from MPG to TS segments with H.264 re-encoding for web delivery.

Source: documentary_nature_ep042.mpg (5.6 GB, 1440x1080i, MPEG-2 15 Mbps)
Conversion: MPG → TS → HLS segments (H.264 re-encode)
Result: HLS stream with 3 quality tiers (1080p/720p/480p)

HLS packaging workflow:
1. Decode MPEG-2 source and deinterlace (1080i → 1080p)
2. Encode H.264 at three bitrates: 5 Mbps, 2.5 Mbps, 1 Mbps
3. Package each bitrate as 6-second TS segments
4. Generate master M3U8 playlist with variant streams
5. Deploy to CDN for web/mobile/smart TV delivery
✓ Viewers get adaptive quality based on connection speed
✓ File size reduced 70% vs original MPEG-2 (H.264 efficiency)
✓ Plays in all browsers via HLS.js or native HLS support
✓ Smart TVs and mobile apps stream natively

Example 3: Blu-ray Disc Authoring from DVD MPEG-2 Sources

Scenario: An independent filmmaker is creating a Blu-ray compilation disc from previously released DVD content. The DVD masters exist as MPEG-2 MPG files and need to be converted to M2TS (Blu-ray Transport Stream) format with proper H.264 re-encoding for Blu-ray compliance.

Source: short_film_collection_part3.mpg (4.2 GB, 720x480, MPEG-2 DVD)
Conversion: MPG → M2TS (H.264 re-encode for Blu-ray)
Result: short_film_collection_part3.m2ts (3.8 GB, 1920x1080, H.264 Level 4.1)

Blu-ray authoring workflow:
1. Upscale DVD-quality 480p to Blu-ray 1080p resolution
2. Encode H.264 High Profile, Level 4.1 (Blu-ray mandatory)
3. Audio: convert MP2 stereo to AC-3 5.1 (Blu-ray standard)
4. Package as M2TS Transport Stream with Blu-ray structure
5. Author Blu-ray disc image with menus and chapter points
✓ Compliant with Blu-ray Disc Association specifications
✓ H.264 encoding provides better quality than DVD MPEG-2
✓ Transport Stream structure with proper M2TS timestamps
✓ Chapter markers and menu navigation preserved

Frequently Asked Questions (FAQ)

Q: What is the difference between MPG (Program Stream) and TS (Transport Stream)?

A: Both are defined in the MPEG-2 Systems standard (ISO/IEC 13818-1) but serve different purposes. Program Stream (MPG) uses variable-length packets and assumes error-free delivery — designed for DVD playback where the disc provides reliable data access. Transport Stream (TS) uses fixed 188-byte packets with synchronization bytes, allowing receivers to recover from dropped packets — designed for broadcast, cable, satellite, and internet streaming where transmission errors are expected. TS also supports multiplexing multiple programs (channels) in a single stream.

Q: Can I convert MPG to TS without re-encoding?

A: Yes, if your MPG file contains MPEG-2 video and compatible audio (MP2, AC-3, or AAC). The conversion is a lossless remux — the elementary streams are extracted from Program Stream packets and repackaged into Transport Stream packets without decoding or re-encoding. Use ffmpeg -i input.mpg -c copy -f mpegts output.ts. The output has identical video/audio quality, with a slightly larger file size due to TS packet overhead (approximately 2-5% increase).

Q: Why is the TS file slightly larger than the MPG file?

A: Transport Stream has inherent overhead from its 188-byte fixed-packet structure. Each packet includes a 4-byte header with sync byte, PID (Packet Identifier), and continuity counter. Additionally, TS includes PSI tables (PAT, PMT) that describe the stream structure, and adaptation fields for timing synchronization. This overhead typically adds 2-5% to the file size compared to Program Stream. For very large files, the percentage is at the lower end; for short clips, it can be higher due to the fixed overhead of PSI tables.

Q: Is TS the same as M2TS used for Blu-ray?

A: M2TS is a variant of MPEG Transport Stream with a 4-byte timestamp prefix prepended to each 188-byte TS packet, creating 192-byte packets. This timestamp (called the "arrival time stamp") is used for precise timing control during Blu-ray playback. Standard TS files can be converted to M2TS by adding these timestamps. Both use the same underlying Transport Stream structure, but Blu-ray authoring tools specifically require the M2TS format with proper timestamp information and H.264 Level 4.1 compliance.

Q: Can I use the TS output for HLS streaming?

A: Yes, TS is the native segment format for HLS (HTTP Live Streaming). After converting MPG to TS, you can segment the file into HLS chunks: ffmpeg -i output.ts -c copy -hls_time 6 -hls_list_size 0 playlist.m3u8. This creates 6-second TS segments with an M3U8 playlist that web browsers (via HLS.js), iOS Safari (native), and most smart TVs can play with adaptive bitrate switching. For multiple quality tiers, re-encode the source at different bitrates and create a master playlist.

Q: Should I re-encode to H.264 when converting MPG to TS, or keep MPEG-2?

A: It depends on your target use case. For legacy broadcast systems, IPTV head-ends, and DVD-era playout equipment that expect MPEG-2, keep the original codec (lossless remux). For modern HLS streaming, web delivery, or Blu-ray authoring, re-encode to H.264 — you will get 50-70% smaller files at equivalent quality. For next-generation ATSC 3.0 broadcast or cutting-edge streaming, H.265/HEVC is the preferred codec inside TS. The lossless remux approach is always faster and preserves quality perfectly.

Q: Can Transport Stream contain multiple video programs?

A: Yes, this is one of TS's key advantages over Program Stream. A single Transport Stream can multiplex multiple independent programs (channels), each with its own video and audio streams identified by unique PIDs (Packet Identifiers). This is how a cable TV signal carries dozens of channels in one stream, or how a satellite transponder delivers multiple services simultaneously. Program Stream (MPG) is limited to a single program. For most file-based conversions, you will create single-program TS files, but broadcast multiplexers routinely combine multiple sources.

Q: How do I handle interlaced MPEG-2 content when converting to TS?

A: If you are performing a lossless remux (keeping MPEG-2 codec), the interlacing is preserved exactly as in the source — no processing needed. If you are re-encoding to H.264 for modern streaming, you should deinterlace the content since most web and mobile viewers expect progressive video. Use FFmpeg's yadif filter: ffmpeg -i input.mpg -vf yadif -c:v libx264 -c:a aac -f mpegts output.ts. For broadcast TS output where interlaced H.264 is acceptable, omit the deinterlacer and the encoder will flag the output as interlaced.