Direct Play in Emby

Direct Play uses the original media representation for the selected playback session while the client performs its normal decoding and presentation work.

Direct Play uses the source media representation without server-side media conversion. The receiving playback path can handle the selected source under the session's relevant constraints.

That can still involve sending the resource from Emby Server. Some client environments can access a filesystem source directly, as Emby's Playback Methods describes. Direct Play is a media-processing category, not a promise that every app reads a network share itself.

The work is distributed

Server or source side Player side
Locate and access the resource Interpret the received container
Supply bytes through the chosen path Decode selected compressed streams
Maintain the playback session Buffer and synchronise presentation
Receive relevant progress reports Render pictures, audio and subtitles

The player does not draw compressed H.264 packets directly onto the display. It reconstructs pictures from them. Likewise, compressed audio must be decoded or delivered through a suitable bitstream output path.

Compressed delivery and decoded frames have different rates

Consider an original constant-rate example carrying 8 Mbit/s over the delivery path. That is 1,000,000 bytes per second in decimal units.

An ideal tightly packed 1920 × 1080, 8-bit 4:2:0 decoded picture occupies:

1920 × 1080 × 1.5 = 3,110,400 bytes

At 24 pictures per second, those ideal picture buffers represent 74,649,600 bytes per second. Actual memory layouts can add alignment and padding.

These figures are not measurements of an Emby device. They show why the network and decoded-frame processing rates describe different work. A client can have demanding decoding/display work even when the server does not encode replacement video.

The session still needs compatible conditions

The original container and selected stream presentation must work through the chosen player path. A bitrate constraint, unsupported audio choice or required subtitle rendering can change the media plan.

The relevant evidence is the actual session, rather than a poster's title or a general device capability list. Compatibility explains how those conditions fit together.

Original media and final presentation

Using the original representation does not bypass the client's presentation choices. The player can scale a picture to its display, apply an appropriate colour/output interpretation or render separately supplied subtitles.

Those client-side operations do not make the server's session a video transcode. The Direct Play label describes preservation of the delivered media representation; the player still has to produce a useful presentation from it.

See Also

References