Starter Deal! First 3 month from only  $9.9 /month!
Starter Deal! First 3 month from only  $9.9 /month!
Grab It Now 
RTC Engine
Overview
  • Web
    • Run Sample Demo
    • SDK Quickstart
    • Basic Features
      • Screen Sharing
      • Live Streaming
      • Media Device
      • Audio Volume
      • Set Encoding Profile
      • Detect Network Quality
      • Detect Capabilities
    • Advance Features
      • Enable AI Denoiser
      • Enable Audio Mixer
      • Enable Watermark
      • Enable Beauty and Effects
      • Data Messages
      • Custom Capturing and Rendering
    • API List
    • Released Notes
    • Supported Platforms
    • Web FAQs
      • Optimize Multi-Person Video Calls
      • Handle Autoplay Restriction
      • Handle Firewall Restriction
      • Others
  • Android
    • Integration
      • 1.API Examples
      • 2.Importing the SDK
      • 3.Entering a Room
      • 4.Subscribing to Audio/Video Streams
      • 5.Publish Audio/Video Streams
      • 6.Exiting a Room
      • 7.Sensing Network Quality
      • 8.Enabling Screen Sharing
      • 9.Setting Video Quality
      • 10.Rotating Videos
    • Testing Newwork Quality
    • Custom Capturing and Rendering
    • Custom Audio Capturing and Playback
    • Client APIs
      • Overview
      • TRTCCloud
      • TRTCStatistics
      • TRTCCloudListener
      • TXAudioEffectManager
      • TXBeautyManager
      • TXDeviceManager
      • Type Definition
      • Deprecated Interface
      • Error Codes
    • Solution
      • Real-Time Chorus (TUIKaraoke)
        • Quick Integration
        • Implementation Steps
        • Song Synchronization
        • Lyric Synchronization
        • Vocal Synchronization
        • Mixing Stream Solution
        • TRTCKaraoke APIs
        • FAQs
    • Release Notes
  • iOS
    • Integration
      • 1.API Examples
      • 2.Importing the SDK
      • 3.Entering a Room
      • 4.Subscribing to Audio/Video Streams
      • 5.Publish Audio/Video Streams
      • 6.Exiting a Room
      • 7.Sensing Network Quality
      • 8.Enabling Screen Sharing
      • 9.Setting Video Quality
      • 10.Rotating Videos
    • Testing Network Quality
    • Custom Capturing and Rendering
    • Custom Audio Capturing and Playback
    • Client APIs
      • Overview
      • TRTCCloud
      • TRTCCloudDelegate
      • TRTCStatistics
      • TXAudioEffectManager
      • TXBeautyManager
      • TXDeviceManager
      • Type Definition
      • Deprecated Interface
      • ErrorCode
    • Solution
      • Quick Integration
      • Implementation Steps
      • Song Synchronization
      • Lyric Synchronization
      • Vocal Synchronization
      • Mixing Stream Solution
      • TRTCKaraoke APIs
      • FAQs
    • Release Notes
  • macOS
    • Integration
      • 1.API Examples
      • 2.Importing the SDK
      • 3.Entering a Room
      • 4.Subscribing to Audio/Video Streams
      • 5.Publish Audio/Video Streams
      • 6.Exiting a Room
      • 7.Sensing Network Quality
      • 8.Enabling Screen Sharing
      • 9.Sharing Computer Audio
      • 10.Setting Video Quality
      • 11.Rotating Videos
    • Testing Hardware Devices
    • Testing Network Quality
    • Custom Capturing and Rendering
    • Custom Audio Capturing and Playback
    • Client APIs
      • Overview
      • TRTCCloud
      • TRTCCloudDelegate
      • TRTCStatistics
      • TXAudioEffectManager
      • TXBeautyManager
      • TXDeviceManager
      • Type Definition
      • Deprecated Interface
      • ErrorCode
      • Release Notes
    • Release Notes
  • Windows
    • Integration
      • 1.API Examples
      • 2.Importing the SDK
      • 3.Entering a Room
      • 4.Subscribing to Audio/Video Streams
      • 5.Publish Audio/Video Streams
      • 6.Exiting a Room
      • 7.Sensing Network Quality
      • 8.Enabling Screen Sharing
      • 9.Setting Video Quality
      • 10.Rotating Videos
    • Testing Hardware Devices
    • Testing Network Quality
    • Custom Capturing and Rendering
    • Custom Audio Capturing and Playback
    • Client APIs
      • Overview
      • ITRTCCloud
      • ITRTCStatistics
      • TRTCCloudCallback
      • ITXAudioEffectManager
      • ITXDeviceManager
      • Type Definition
      • Deprecated Interface
      • Error Codes
    • Release Notes
  • Electron
    • Integration
      • 1.API Examples
      • 2.Importing the SDK
      • 3.Entering a Room
      • 4.Subscribing to Audio/Video Streams
      • 5.Publish Audio/Video Streams
      • 6.Exiting a Room
      • 7.Sensing Network Quality
      • 8.Enabling Screen Sharing
      • 9.Sharing Computer Audio
      • 10.Setting Video Quality
      • 11.Rotating Videos
    • Client APIs
      • Overview
      • Error Codes
  • Flutter
    • Integration
      • 1.API Examples
      • 2.Importing the SDK
      • 3.Entering a Room
      • 4.Subscribing to Audio/Video Streams
      • 5.Publish Audio/Video Streams
      • 6.Exiting a Room
      • 7.Sensing Network Quality
      • 8.Enabling Screen Sharing
      • 9.Sharing Computer Audio
      • 10.Setting Video Quality
      • 11.Rotating Videos
    • Client APIs
      • Overview
      • Error Codes
  • Unity
    • Integration
      • 1.API Examples
      • 2Importing the SDK
    • Client APIs
      • Overview
      • Error Codes
  • Qt
    • Integration
      • 1.Importing the SDK
  • Overview
    • Overview
  • Concepts
  • Features
  • Performance Statistics
  • Pricing
    • RTC-Engine Packages
    • Billing of On-Cloud Recording
    • Billing of MixTranscoding and Relay to CDN
    • Billing Explanation for Subscription Package Duration
    • Billing of Monitoring Dashboard
    • Free Minutes
    • Pay-As-You-Go
  • Tencent RTC Quickplay: Experience Ultimate Real-Time Audio and Video Interaction!
  • FAQs
    • FAQs for Beginners
    • Migration Guide
      • Twilio Video to Tencent RTC
      • Billing
      • Features
      • UserSig
      • Firewall Restrictions
      • How to Downsize Installation Package
      • TRTCCalling for Web
      • Audio and Video Quality
      • Others
RTC Engine

Billing of MixTranscoding and Relay to CDN

Billable Item

MixTranscoding is a paid feature service launched by Tencent Real-Time Communication (TRTC) and can be used to process multiple upstream audio and video streams through image mixing, audio and video transcoding, and repackaging. You can perform configurations on the console or call APIs as needed.

Billing Overview

Billing mode: Post-paid on a daily basis.
Billing cycle: Settled daily. The cloud recording fees for each day will be deducted when the billing statement is generated the next day. For detailed billing and billing time, see Billing Statement.
Since June 1, 2022, the usage measurement for MixTranscoding has been changed from output-duration-based measurement to input-duration-based measurement.
This document only describes the transcoding fees generated by MixTranscoding using the MCU cluster provided by TRTC. If you push the audio and video streams of TRTC to Cloud Streaming Services (CSS) and then use the Stream Mix feature provided by CSS, CSS will charge you for the live transcoding fee.
The usage generated by pushing or pulling and relaying streams back to the TRTC room is also billed based on the transcoding fees.
If you relay the transcoded audio and video stream output into the Cloud Streaming Services system for the audience to view CDN live streaming, Cloud Streaming Services will charge you for the traffic/bandwidth fee.
If you relay the transcoded audio and video stream output to CSS or a third-party CDN, you will be charged for the relay robot subscription duration fee and the bypass relay fee.
If you use the Input Online Media Stream function to share external media stream to the room, On-Cloud MixTranscoding billing will also be applied, and the audio duration fee generated by the robot in the Room will be charged.
Note:
When a transcoding task is initiated in a room, the system assigns corresponding robot to enter the room as a virtual viewer (for multiple transcoding tasks, multiple robots will enter the room). The robot subscribes to the audio and video streams that need to be transcoded, leading to a fee based on the audio and video duration.
In other scenarios (including but not limited to transcoding and relay to other rooms or platforms), the robot subscription duration will be normally charged.

Fee Calculation

MixTranscoding fee = Audio transcoding fee + Video transcoding fee = Audio input duration × Audio transcoding unit price + Video input duration after collection × Unit price corresponding to the input stream collected video resolution and output coding method.

Product Pricing

The following table list the published prices for MixTranscoding of TRTC:
Codec
Billable Item
Unit Price (USD/1,000 Min)
Audio transcoding
Transcoding - Voice
1.99
H.264
Transcoding-H264-High Definition HD
5.99
H.264
Transcoding - H264 - Ultra High Definition FHD
13.99
H.264
Transcoding-H264-2K
25.99
H.264
Transcoding-H264-4K
69.99
H.265
Transcoding-H265-High definition HD
17.99
H.265
Transcoding-H265-Ultra high definition FHD
37.99
H.265
Transcoding-H265-2K
69.99
H.265
Transcoding-H265-4K
189.99
Note:
MixTranscoding of TRTC supports only post-paid billing mode on a daily basis, with the fees generated from the previous day being deducted at 10:00 AM each day.

Usage Statistics

The TRTC transcoding service usage is calculated based on the video and audio stream duration input for MCU MixTranscoding under the same Tencent Cloud account across all applications. Depending on the input streams in the room, the transcoding duration falls into two categories: video input duration and audio input duration.

Video Input Duration

The video input duration refers to the length of the videos in all input streams after collection before transcoding. TRTC will divide the videos into different levels based on the resolution of the input video after collection and will charge for the duration of the videos at different levels. The relationship between video level and resolution is as follows:
Video Level
Input Resolution
High Definition HD
Not exceeding 1280 × 720 (inclusive)
Ultra High Definition FHD
1280 × 720 - 1920 × 1080 (inclusive)
2K
1920 × 1080 - 2560 ×1440 (inclusive)
4K
2560 × 1440 - 4096 × 2176 (inclusive)
If the same input stream before transcoding contains both video and audio at the same time, only the video duration is measured, and the audio duration is not measured again.
Before transcoding, if there are pure audio streams in multiple input streams, the audio duration of this stream also needs to be measured.
Before transcoding, the resolution of the same input stream may change. TRTC will measure the usage in segments, which is usually updated every 60 seconds. When the resolution changes, it will be reported and updated immediately.
For the same mixed stream task at a certain moment, when the ratio of the area of the output resolution to the sum of all input resolution areas is greater than 2:1, the system will add an input image according to the output resolution to guarantee the quality of the output resolution, generating an extra audio and video input usage.
When the host uses H.265 as the stream codec and the audience in TRTC room does not support H.265 decoding, the stream codec of the host will automatically downgrade to H.264 to ensure the playback experience of the audience in the room. At the same time, to keep the stability of the codec of CDN playback and not to affect the CDN audience, the TRTC background will automatically initiate transcoding to output H.265 during bypass relay, generating H.265 transcoding fees.

Audio Input Duration

Audio input duration refers to the length of pure audio in all input streams before transcoding. For scenarios of pure audio input, billing for multiple audio inputs is based on the collected audio. That is, multiple audio inputs are billed as a single audio input for transcoding.
Note:
The duration is measured by second, and the billing is conducted by SDKAppID and based on the time through a conversion from seconds to minutes every day. Durations less than one minute are billed as one minute.
If there is no image in the audio and video output of MixTranscoding, the system will add a black screen image according to the output resolution to ensure that there is the audio and video output. Therefore, an extra video input usage will be generated.
For one stream input of MixTranscoding, if there is pure audio input in a period and video input in another period, the period of pure audio will be charged based on audio, and the period of video will be charged based on video.

Billing Examples

MixTranscoding

Audio live streaming

An anchor streamed audio-only content for 30 minutes and then co-anchored with someone for 30 minutes, during which the two anchors’ streams were mixed and then published to Tencent Cloud’s live streaming system.
In the first 30 minutes, because there was only one anchor, no MixTranscoding fees would be charged. In the 30 minutes afterward, there were two anchors who communicated over audio, so audio MixTranscoding fees would be charged.
MixTranscoding fee = 1.99 x 30/1,000 = 0.0597 USD.

Video live streaming

Anchor A streamed video content at a resolution of 1920 x 1080 for 30 minutes and then co-anchored with anchor B over video for 10 minutes. Anchor B’s video resolution was 1280 x 720. The two anchors’ streams were mixed and then published to Tencent Cloud’s live streaming system.
For anchor A, his or her own video was displayed as the big image, and anchor B’s video appeared in a small window in the top right corner. The resolution of the video viewed by anchor A was 1920 x 1080. For anchor B, his or her own video was displayed in the large video window, and anchor A’s video appeared in a small window in the top right corner. The resolution of the video viewed by anchor B was 1280 x 720.
In the first 30 minutes, because there was only one anchor, no MixTranscoding fees would be charged. In the 10 minutes afterward, two anchors communicated over video, and two MixTranscoding tasks were started, which would be charged separately. The aggregate resolution of both tasks was 1920 x 1080 + 1280 x 720 = 2,995,200, and the H.264 codec was used, so the H.264 2K category would apply. Note that the applicable video category is not determined by the resolution of the output video.
MixTranscoding fee = 25.99 x 10/1,000 + 25.99 x 10/1,000 = 0.5198 USD.

Relaying fees

If you publish to a third-party platform or CDN, relaying fees will be charged based on the bandwidth used.
Cost formula:
Relaying fees = Monthly peak bandwidth x Unit price of relaying

Pricing

The bandwidth used for relaying is priced as follows:
Category
Price (USD/Mbps/Month)
Monthly peak bandwidth
18.99
Note:
TRTC calculates usage based on the Peak Bandwidth (unit: Mbps) generated by the Relay service used in all applications under the same Tencent Cloud account within the billing period. The current default is to calculate usage based on Monthly Peak Bandwidth.
Relay to Tencent Cloud CSS, for all applications under the same Tencent Cloud account, if the monthly peak bandwidth has not reached 50Mbps, no bandwidth fee will be charged for relaying to Tencent Cloud CSS.

Billing examples

Suppose the bitrate of a stream you published to third-party platforms was 500 Kbps (the sum of the audio bitrate and video bitrate), and there were 10 relaying tasks at the peak on that day. Daily peak bandwidth = 500 (Kbps) x 10 = 5,000 (Kbps) = 5 Mbps.
Suppose you used the relaying feature in June 2022, and the bandwidth used for relaying reached 5 Mbps at the peak. Your relaying fee for June 2022 = 18.99 (USD/Mbps/month) x 5 (Mbps) = 94.95 USD.