Skip to main content
Uploaded Content and the Media Manager

Best Practices For Video Content On The Korbyt Platform

Video options can be complex and varied. This article shares best practices and considerations for a successful video dpleoyment in the Korbty Signage platform

Written By Ed Kinne

Korbyt can support several common video formats Supported Media Specification, but the complexity of digital video and player hardware options can lead to less-than-optimal playback at times.

Korbyt operates across a broad ecosystem of players and platforms. Primarily, the Korbyt platform uses the Chromium web engine to render videos within a multi-zone layout, which is powered by HTML5. There are exceptions, particularly on native players with full-screen videos in playlists, where native APIs are utilized for video playback.

The following best practices are based on our experience testing and deploying new content on the Korbyt platform:


Video playback issues on Korbyt Players are often related to video bitrate and encoding settings. Videos encoded at higher bitrates than the player configuration allows may fail to play, stutter, or behave inconsistently.

Video Encoding Considerations and Bitrate

Korbyt does not automatically transcode videos.
Unlike platforms like YouTube, which handle transcoding and resolution adjustments, Korbyt allows you to upload raw video files. While this offers flexibility, it can also introduce challenges, particularly if high-resolution videos (e.g., 4K) are being delivered to devices with lower resolution capabilities (e.g., 1080p displays). Encoding videos appropriately before uploading is crucial to avoid performance issues.

Korbyt has a standard bitrate limit of 5 Mbps (average bitrate of video)
This is to ensure a consistent experience across player types with varying levels of processing power.

Your tenant may have a higher bitrate limit set. If you need to increase your tenants' bitrate limit, please contact Support@Korbyt.com, but be aware of the impact it may have on your hardware when sending a file that is too complex for it to play well.

Videos have to be below your tenant’s maximum limit to be able to be added to a playlist. Videos over your limit will appear with a red warning symbol.


BrightSign Specific Considerations

BrightSign has its own article that outlines limits and considerations for each player series.
Please Review - BrightSign Video Formats & Codecs

Video encoding requirements for BrightSign (H.264)

On some BrightSign players, some H.264 videos stop about 2 seconds early, at around the 8-second mark, and then show a white or blank screen until the next item starts. The same files play correctly in BrightSign’s native player.

Cause

Korbyt plays video on BrightSign through the player’s HTML video engine, which streams the file over a local HTTP connection. On BrightSign 4 Series OS 8.5 and 9.1, H.264 files encoded without B-frames can end early on that path. Files encoded with B-frames play their full length.

Required encoding settings

Setting

Value

Container

MP4 (index at the start of the file, sometimes called “fast start”)

Codec

H.264 (AVC)

Profile

High (Main also works if B-frames are enabled)

Level

5.1 for 4K at up to 30 fps; 5.2 for 4K at 60 fps; 4.1 or 4.2 for 1080p

B-frames

Required (2 recommended)

Keyframe interval (GOP)

1 second, for example 30 frames at 30 fps

Frame rate

Constant (CFR)

Pixel format

8-bit 4:2:0 (yuv420p)

Color

Rec. 709 (SDR)

Audio

Optional. AAC if included

Exporting from After Effects

Render through Adobe Media Encoder with the H.264 format, using High profile and the level from the table above. Because B-frames aren’t always visible as a setting in Adobe’s H.264 exporter, check every finished file using the steps below before uploading it to Korbyt.

Checking a file for B-frames

  • MediaInfo: open the file and find Format settings, GOP in the Video section. M=1 means no B-frames, so the file will fail. M=2 or higher (for example M=3, N=30) means B-frames are present, so it’s OK.

  • ffprobe: run
    ffprobe -v error -select_streams v:0 -show_entries stream=has_b_frames -of default=nw=1 input.mp4
    has_b_frames=0 will fail. has_b_frames=1 or higher is OK.

Fixing an existing file

Re-encode the file with B-frames using ffmpeg:

ffmpeg -i input.mp4 -c:v libx264 -profile:v high -level 5.1 -bf 2 -g 30 -pix_fmt yuv420p -an -movflags +faststart output.mp4
  • For 1080p content, use -level 4.1.

  • To keep the audio track, replace -an with -c:a aac -b:a 192k.

  • To control quality or file size, add -crf 18 for higher quality or a fixed bitrate such as -b:v 20M.


Video Encoding Best Practices:

Bitrate Management

  • Bitrate is critical for both file size and consistent playback performance

  • We recommend using constant bitrate (CBR) encoding, as it ensures stable playback without large fluctuations in quality.

    • Variable bitrate (VBR) encoding can have bitrate spikes that lead to playback issues

  • For 1080p resolution, we suggest a CBR between 2-7 Mbps. For higher resolutions (e.g., 2K to 4K), the bitrate should be adjusted accordingly, based on the video content itself.

  • It’s important to avoid excessive bitrate spikes, such as transitioning from 2 Mbps to 30 Mbps, as these may cause decoding problems on some players. Tools like FFBitrateViewer can help you monitor the bitrate fluctuations of VBR videos.

Video Transcoding Software

There are many video encoding/transcoding software options available. Korbyt does not require any specific software.
Below are some suggestions for you if your organization does not already have a preferred video production software.

CurtConvert

  • CurtConvert is a Korbyt-created tool.

  • It is free and simple to use.

    • It automatically compresses the video to target a 5 Mbps Bitrate,

    • It does not offer any custom settings.

  • For more information on CurtConvert, see How To Transcode Videos With CurtConvert

Handbrake

  • Handbrake is a popular, powerful, and free video transcoding software.

  • It offers many encoding options and settings.

    • Not all will be compatible with Korbyt.

  • While powerful, it can be complex to learn.

  • It can be found at https://handbrake.fr/

FFmpeg for Encoding and Debugging

  • FFmpeg is an excellent free tool for both encoding and troubleshooting.

  • It offers diagnostic tools to check for encoding errors

    • By using the -v info or -v error flag, you can identify potential issues with frames or decoding problems, ensuring that the video is error-free before deployment.

  • It can be found at https://www.ffmpeg.org/


Source Resolution

  • Always aim to maintain the source resolution of the video, or downscale it if necessary.

  • Upscaling videos is generally discouraged, as it can introduce quality degradation and increase file size unnecessarily.

Resolution Matching

  • Always match the output video resolution to the intended display environment. This ensures that the video is appropriately scaled for the target device or platform, optimizing both performance and quality.


Codec Selection

  • For optimal compatibility and performance, use the H.264 codec, which is widely supported across most devices and browsers.

  • Alternatively, VP9 is an excellent choice, particularly when using the Chromium renderer, as it is used by platforms like YouTube and is supported by modern browsers.

  • Though codecs like AV1 offer advanced compression, they are not as widely supported so you will need to ensure that they are compatible with your target players and environment before widespread deployment.


Video Deployment Considerations

Pre-Deployment Testing

It is crucial to test video content on one or more players before full production deployment for critical deployments. While the preview pane in the Korbyt Builder and the playlist preview provide useful initial insights, testing on your actual player hardware is essential. This helps ensure that content plays correctly across your different devices and environments.
Moreover, it’s advisable to conduct longevity tests to assess the content’s performance over extended periods, ensuring it operates effectively after days of continuous playback.

File Size Considerations

Video file size plays a significant role in playback quality, especially during streaming. Korbyt supports both streaming and caching modes for video playback. In streaming mode, larger files may cause suboptimal playback, particularly on less-than-ideal network connections. However, once the file is cached locally, Korbyt always uses the cached version, ensuring smooth playback.

Audio Considerations

  • Depending on the use case, audio may not be necessary. Consider using a tool like FFmpeg to strip out audio from videos where it is not required, reducing file size and simplifying playback.

  • If audio is required, consider the needed number of channels (Multiple, Stereo, Mono) and the Sample Rate required. Any extra audio signal that is not needed will add to the overall demand when played back