Set the Video Profile

User experience in real-time engagement scenarios involving video is closely related to the quality of the video, such as its sharpness and smoothness.

Video profiles are preset configurations of resolution, frame rate, and bitrate. Developers can implement video profiles to control how video streams will appear to users under ideal network conditions. This article shows how to call the API provided by Agora to set video profiles.

Agora provides an open-source sample project on GitHub that implements setting the video profile. You can download the sample project to try it out or view the source code.

Before proceeding, ensure that you have implemented real-time audio and video functions in your project.

The Agora SDK provides the setVideoEncoderConfiguration method to set the video profile. After you initialize the RtcEngine object, you can call setVideoEncoderConfiguration either before or after joining a channel.

If you do not intend to update the video profile after joining a channel, Agora recommends calling setVideoEncoderConfiguration before enableVideo, which reduces the time to render the first local video frame.

You can set the video resolution, frame rate, and bitrate with the following parameters:

• dimensions: The video encoding resolution (px). The default value is 640 × 360. Generally speaking, the higher the resolution, the sharper the video. The value of this parameter does not indicate the orientation mode of the output video. For how to set the orientation mode of the output video, see Orientation mode.
• frameRate: The video encoding frame rate (fps), that is, the number of frames that the SDK encodes per second. The default value is 15. Generally speaking, the higher the frame rate, the smoother the video. For scenarios with high requirements on video smoothness, You can set this parameter as 20 or 25. Agora recommends not setting frameRate as any value beyond 30.
• bitrate: The video encoding bitrate (Kbps). The default value is STANDARD_BITRATE, that is, the standard bitrate mode. Under the standard bitrate mode, the SDK assigns a bitrate value according to the channel profile, video dimensions, and frame rate that you set.

• To achieve high video quality, you need to strike a balance between video dimensions, bitrate, and frame rate. Higher video dimensions require higher bitrate. With a fixed bitrate, excessive frame rate reduces video dimensions.
• The parameters specified are the maximum values under ideal network conditions. If the SDK cannot render the video using the specified parameters due to poor network conditions, lower quality settings are used.

The Agora SDK provides selections of video dimensions, frame rate, and bitrate for you to choose from. You can also customize the values according to the table below.

Video profile table

Whether 720p+ can be supported depends on the device. If the device cannot support 720p, the frame rate will be lower than the one listed in the table.

Resolution (width × height)	Frame rate (fps)	Base bitrate (Kbps, for Communication)	Live bitrate (Kbps, for LiveBroadcasting)
160 × 120	15	65	130
120 × 120	15	50	100
320 × 180	15	140	280
180 × 180	15	100	200
240 × 180	15	120	240
320 × 240	15	200	400
240 × 240	15	140	280
424 × 240	15	220	440
640 × 360	15	400	800
360 × 360	15	260	520
640 × 360	30	600	1200
360 × 360	30	400	800
480 × 360	15	320	640
480 × 360	30	490	980
640 × 480	15	500	1000
480 × 480	15	400	800
640 × 480	30	750	1500
480 × 480	30	600	1200
848 × 480	15	610	1220
848 × 480	30	930	1860
640 × 480	10	400	800
1280 × 720	15	1130	2260
1280 × 720	30	1710	3420
960 × 720	15	910	1820
960 × 720	30	1380	2760

Recommended video profiles

The recommended video profiles vary by scenario. For example, in a one-to-one online class, the video windows of the teacher and student are both large, which calls for higher resolutions, frame rates, and bitrates. In a one-to-four online class, however, the video windows of the teacher and students are smaller, so lower resolutions, frame rates, and bitrates are used to accommodate bandwidth limitations.

The following profiles for different scenarios are recommended:

• One-to-one video call:
  • Resolution: 320 × 240; frame rate: 15 fps; bitrate: 200 Kbps.
  • Resolution: 640 × 360; frame rate: 15 fps; bitrate: 400 Kbps.
• One-to-many video call:
  • Resolution: 160 × 120; frame rate: 15 fps; bitrate: 65 Kbps.
  • Resolution: 320 × 180; frame rate: 15 fps; bitrate: 140 Kbps.
  • Resolution: 320 × 240; frame rate: 15 fps; bitrate: 200 Kbps.

Orientation mode​

Video rotation involves the video capturer and the video player, where:

• The video capturer captures the video and outputs the relevant video information, namely, the relative position of the video and the status bar.
• The video player renders the received video and rotates the video according to the rotation information.

To avoid issues such as video scaling and cropping caused by video rotation, the Agora SDK provides the orientationMode parameter in the setVideoEncoderConfiguration method. You can use this parameter to set the video orientation mode according to your scenario to get the video you want.

The orientationMode parameter provides three modes to suit different user needs: ORIENTATION_MODE_ADAPTIVE, ORIENTATION_MODE_FIXED_LANDSCAPE, and ORIENTATION_MODE_FIXED_PORTRAIT.

Regardless of the mode, the relative position of the video and the status bar on both the video capturer and the player remain the same.

ORIENTATION_MODE_ADAPTIVE

In the ORIENTATION_MODE_ADAPTIVE mode, the output video always follows the orientation of the captured video, and the receiver takes the rotation information passed on from the video encoder. This mode applies to scenarios where video orientation can be adjusted on the receiver and is usually used between Agora SDKs.

The following figures show the video orientations at the video capturer and player when a rear camera is used as the video capturer. Note that the video orientation differs depending on whether or not the UI is locked.

UI locked (or UI unlocked with the app disabling the screen auto-rotation)

The relative position of the status bar remains the same as the screen and not according to the phone tilt (for example, in WeChat). Therefore, the relative positions of the video and the screen remain the same for the video capturer and the player.

• For a landscape capturer:

  

• For a portrait capturer:

  

UI unlocked with the app enabling the screen auto-rotation

The status bar of the app remains horizontal, regardless of the orientation of the screen (for example, in Facetime). Therefore, the relative positions of the video and the phone tilt remain the same for the video capturer and the player.

• For a landscape capturer:

  

• For a portrait capturer:

  

ORIENTATION_MODE_FIXED_LANDSCAPE

In the ORIENTATION_MODE_FIXED_LANDSCAPE mode, the video capturer sends the video in the landscape orientation relative to the status bar. If the captured video is in portrait mode, the video encoder crops it to fit the output. This mode applies to situations where the receiving end cannot process the rotation information.

The following figures show the video orientations at the video capturer and the player when a rear camera is used as the video capturer.

• The captured video in the landscape mode (video cropping is not needed):

  

• The captured video in the portrait mode (video cropping is needed):

  

ORIENTATION_MODE_FIXED_PORTRAIT

In the ORIENTATION_MODE_FIXED_PORTRAIT mode, the video capturer sends out the video in the portrait orientation relative to the status bar. If the captured video is in landscape mode, the video encoder crops it to fit the output. This mode applies to situations where the receiving end cannot process the rotation information.

The following figures show the video orientations at the video capturer and the player when a rear camera is used as the video capturer.

• The captured video in the portrait mode (video cropping is not needed):

  

• The captured video in the landscape mode (video cropping is needed):

  

To optimize user experience in poor network conditions, Agora provides the degradationPrefer parameter to set how you wish to degrade the video under limited network bandwidth.

By default, the SDK does not mirror the video during encoding. You can use the mirrorMode parameter to decide whether to mirror the video that remote users see.

If your scenario has special requirements for video sharpness or smoothness, you can use the following parameters to alter the minimum frame rate or bitrate:

• minFrameRate: The minimum video frame rate (fps). You can use minFrameRate and MAINTAIN_QUALITY to balance the video sharpness and video smoothness under unreliable connections. When minFrameRate is relatively low, the frame rate degrades significantly, so the poor network conditions have limited impact on video sharpness. When minFrameRate is relatively high, the frame rate degrades within a limited range, so the poor network conditions can have high impact on video sharpness.
• minBitrate: The minimum video bitrate (Kbps). The Agora SDK automatically adjusts the encoding bitrate to adapt to the network conditions. Setting this parameter to a value greater than the default value forces the video encoder to output high-quality video images but may cause more packet loss and sacrifice video smoothness.

The default values of minFrameRate and minBitrate can meet the requirements of most real-time scenarios. Unless you have special requirements, Agora recommends not changing these default values.

You can refer to the following code sample when setting the parameters of setVideoEncoderConfiguration:

_18

// Set the video encoding resolution, frame rate, bitrate and orientation mode according to the settings of the user

_18

VideoEncoderConfiguration.VideoDimensions value = VD_640x360;

_18

try {

_18

Field tmp = VideoEncoderConfiguration.class.getDeclaredField(dimension.getSelectedItem(toString());

_18

tmp.setAccessible(true);

_18

value = (VideoEncoderConfiguration.VideoDimensions) tmp.get(null);

_18

} catch (NoSuchFieldException e) {

_18

Log.e("Field", "Can not find field " + dimension.getSelectedItem().toString());

_18

} catch (IllegalAccessException e) {

_18

Log.e("Field", "Could not access field " + dimension.getSelectedItem().toString());

_18

_18

_18

engine.setVideoEncoderConfiguration(new VideoEncoderConfiguration(

_18

value,

_18

VideoEncoderConfiguration.FRAME_RATE.valueOf(framerate.getSelectedItem().toString()),

_18

Integer.valueOf(et_bitrate.getText().toString()),

_18

VideoEncoderConfiguration.ORIENTATION_MODE.valueOf(orientation.getSelectedItem().toStri())

_18

));

• The parameters specified in setVideoEncoderConfiguration are the maximum values under ideal network conditions. The SDK adapts (most often downwards) these parameters according to the network conditions in real-time.
• Setting parameters in setVideoEncoderConfiguration affects your bill. If network adaptation occurs, the unit price is calculated based on the actual video dimensions. For more information, see Billing for Real-time Communication.