Should you’re thinking about streaming media, you probably fall into considered one of camps: Either you already know something about transcoding, or you’re wondering why you keep hearing about it. When you aren’t positive you need it, bear with me for a number of paragraphs. I’ll clarify what transcoding is (and isn’t), and why it might be critical on your streaming success — especially if you want to deliver adaptive streams to any device.

So, What Is Transcoding?
First, the word transcoding is commonly used as an umbrella time period that covers a number of digital media tasks:

Transcoding, at a high level, is taking already-compressed (or encoded) content; decompressing (decoding) it; and then in some way altering and recompressing it. As an example, you may change the audio and/or video format (codec) from one to another, akin to converting from an MPEG2 source (commonly used in broadcast television) to H.264 video and AAC audio (the most well-liked codecs for streaming). Other fundamental tasks may include adding watermarks, logos, or different graphics to your video.
Transrating refers specifically to altering bitrates, similar to taking a fourK video input stream at 13 Mbps and changing it into one or more lower-bitrate streams (additionally known as renditions): HD at 6Mbps, or different renditions at 3 Mbps, 1.8 Mbps, 1 Mbps, 600 kbps, etc.
Transsizing refers specifically to resizing the video frame; say, from a resolution of 3840×2160 (fourK UHD) down to 1920×1080 (1080p) or 1280×720 (720p).

So, when you say "transcoding," you is likely to be referring to any mixture of the above tasks — and typically are. Video conversion is computationally intensive, so transcoding usually requires more powerful hardware resources, together with faster CPUs or graphics acceleration capabilities.

What Transcoding Is Not
Transcoding shouldn't be confused with transmuxing, which can also be referred to as repackaging, packetizing or rewrapping. Transmuxing is whenever you take compressed audio and video and — without changing the precise audio or video content — (re)package it into different delivery formats.

For instance, you might have H.264/AAC content, and by changing the container it’s packaged in, you'll be able to deliver it as HTTP Live Streaming (HLS), Smooth Streaming, HTTP Dynamic Streaming (HDS) or Dynamic Adaptive Streaming over HTTP (DASH). The computational overhead for transmuxing is far smaller than for transcoding.

When Is Transcoding Critical?
Simply put: Transcoding is critical when you want your content to achieve more finish users.

For example, let’s say you need to do a live broadsolid utilizing a camera and encoder. You may be compressing your content material with a RTMP encoder, and select the H.264 video codec at 1080p.

This must be delivered to online viewers. But when you try to stream it directly, you will have a number of problems. First, viewers without ample bandwidth aren’t going to be able to view the stream. Their players will be buffering continuously as they wait for packets of that 1080p video to arrive. Secondly, the RTMP protocol is not widely supported for playback. Apple’s HLS is far more widely used. Without transcoding and transmuxing the video, you will exclude nearly anyone with slower data speeds, tablets, mobile phones, and related TV devices.

Using a transcoding software or service, you can simultaneously create a set of time-aligned video streams, each with a different bitrate and frame size, while converting the codecs and protocols to achieve additional viewers. This set of internet-friendly streams can then be packaged into several adaptive streaming codecs (e.g., HLS), permitting playback on almost any screen on the planet.

Another common example is broadcasting live streams utilizing an IP camera, as can be the case with surveillance cameras and site visitors cams. Again, to reach the largest number of viewers with the absolute best quality allowed by their bandwidth and devices, you’d wish to support adaptive streaming. You’d deliver one HD H.264/AAC stream to your transcoder (typically positioned on a server image in the cloud), which in turn would create multiple H.264/AAC renditions at totally different bitrates and resolutions. Then you definately’d have your media server (which may be the same server as your transcoder) package these renditions into one or more adaptive streaming formats earlier than delivering them to end users.

If you cherished this posting and you would like to receive additional information relating to Security Center VMS Sharing kindly check out our own web site.