tencent cloud


Publishing from Camera

Last updated: 2024-01-13 15:49:41


    Publishing from camera refers to the process of collecting video and audio data from the mobile phone’s camera and mic, encoding the data, and publishing it to cloud-based live streaming platforms. Tencent Cloud’s LiteAVSDK provides the camera publishing capability via V2TXLivePusher.The following is the relevant GUI that demonstrating camera push stream in the SDK API-Example project:


    Testing on real devices: The SDK uses a lot of audio and video APIs of the Android system, most of which cannot be used on emulators. Therefore, we recommend that you test your project on a real device.

    Sample Code

    GitHub Address
    Key Class


    1. Download the SDK

    Download the SDK and follow the instructions in SDK Integration to integrate the SDK into your application.

    2. Configure License Authorization for SDK

    1. Obtain license authorization:
    If you have obtained the relevant license authorization, need to Get License URL and License Key in Cloud Live Console
    If you have not yet obtained the license authorization, please reference Adding and Renewing Licenses to make an application.
    2. Before your App calls SDK-related functions (it is recommended in the Application class), set the following settings:
    public class MApplication extends Application {
    public void onCreate() {
    String licenceURL = ""; // your licence url
    String licenceKey = ""; // your licence key
    V2TXLivePremier.setEnvironment("GDPR"); // set your environment
    V2TXLivePremier.setLicence(this, licenceURL, licenceKey);
    V2TXLivePremier.setObserver(new V2TXLivePremierObserver() {
    public void onLicenceLoaded(int result, String reason) {
    Log.i(TAG, "onLicenceLoaded: result:" + result + ", reason:" + reason);

    3. Initialize the V2TXLivePusher component

    Create a V2TXLivePusher object, which will be responsible for publishing operations.
    // Specify the corresponding live broadcast protocol as RTMP, which does not support mic connection
    V2TXLivePusher mLivePusher = new V2TXLivePusherImpl(this, V2TXLiveDef.V2TXLiveMode.TXLiveMode_RTMP);

    4. Enable camera preview

    Before enabling camera preview, you must first provide the SDK with a TXCloudVideoView object to display video images. Given that TXCloudVideoView is inherited from FrameLayout in Android, you can:
    1. Add a video rendering control in the XML file:
    android:layout_height="match_parent" />
    2. Call startCamera in V2TXLivePusher to enable camera preview for your mobile phone.
    // Enable preview for the local camera
    TXCloudVideoView mPusherView = (TXCloudVideoView) findViewById(R.id.pusher_tx_cloud_view);

    5. Start and stop publishing

    1. After calling startCamera to enable camera preview, you can call the startPush API in V2TXLivePusher to start publishing.
    if you choose RTMP protocol to push in Step3,the generate of the push URL, please refer to RTMP URL.
    //This URL does not support co-anchoring. The stream is published to a live streaming CDN.
    String url = "rtmp://test.com/live/streamid?txSecret=xxxxx&txTime=xxxxxxxx";
    int ret = mLivePusher.startPush(url);
    Log.i(TAG, "startRTMPPush: license verification failed");
    Reason for returning V2TXLIVE_ERROR_INVALID_LICENSE?
    If the startPush interface returns V2TXLIVE_ERROR_INVALID_LICENSE, it means that your license verification failed, please check the url and key set in Step 2: Configure the SDK for license authorization.
    2. Call stopPush in V2TXLivePusher to stop publishing streams
    //Stop publishing

    6. Publish audio-only streams

    If your live streaming scenarios involve audio only, you can skip Step 4 or call stopCamera before startPush.
    // The push stream can be started by passing in the corresponding URL according to the push stream protocol. The RTMP protocol starts with rtmp://, and this protocol does not support the connection of microphones.
    String url = "rtmp://test.com/live/streamid?txSecret=xxxxx&txTime=xxxxxxxx";
    int ret = mLivePusher.startPush(url);
    If you publish audio-only streams but no streams can be pulled from an RTMP, FLV, or HLS playback URL, there is a problem with your line configuration, please submit a ticket for help.

    7. Set video quality

    Call setVideoQuality in V2TXLivePusher to set the quality of videos watched by audience. The encoding parameters set determine the quality of videos presented to audience. The local video watched by the host is the original HD version that has not been encoded or compressed, and is therefore not affected by the settings. For details, please see Setting Video Quality.

    8. Set the beauty filter style and skin brightening and rosy skin effects

    Call getBeautyManager in V2TXLivePusher to get a TXBeautyManager instance to set beauty filters.

    Beauty filter style

    The SDK has three built-in beauty filter algorithms, each corresponding to a beauty filter style. Choose one that best fits your product positioning. For the definitions, see TXLiveConstants.java.
    Beauty Filter Style
    The smooth style, which features more obvious skin smoothing effects and is suitable for live showrooms
    The natural style, which retains more facial details and is more natural
    The Pitu style, which uses the beauty filter algorithm developed by YouTu Lab. Its effect is between the smooth style and the natural style, that is, it retains more skin details than the smooth style and delivers more obvious skin smoothing effects than the natural style.
    You can call the setBeautyStyle API of TXBeautyManager to set the beauty filter style.
    Beauty filter strength
    Via the setBeautyLevel API in `TXBeautyManager`
    Value range: 0-9. `0` means the filter is disabled. The greater the value, the more obvious the effect.
    Skin brightening filter strength
    Via the setWhitenessLevel API in `TXBeautyManager`
    Value range: 0-9. `0` means the filter is disabled. The greater the value, the more obvious the effect.
    Rosy skin filter strength
    Via the setRuddyLevel API in `TXBeautyManager`
    Value range: 0-9. `0` means the filter is disabled. The greater the value, the more obvious the effect.

    9. Set color filters

    Call getBeautyManager in V2TXLivePusher to get a TXBeautyManager instance to set color filters.
    Call the setFilter API in TXBeautyManager to set color filters. Color filters are a technology that adjusts the color tone of sections of an image. For example, it may lighten the yellow sections of an image to achieve the effect of skin brightening, or add warm tones to a video to give it a refreshing and soft boost.
    Call the setFilterStrength API in TXBeautyManager to set the strength of a color filter. The higher the strength, the more obvious the effect.
    Based on our experience of operating Mobile QQ and Now Live, it’s not enough to use only the setBeautyStyle API in TXBeautyManager to set the beauty filter style. The setBeautyStyle API must be used together with setFilter to produce richer effects. Given this, our designers have developed 17 built-in color filters for you to choose from.
    // Select the desired color filter file. The filter file can be obtained from the resource file of the Mini Live App (a .png file starting with tuibeauty_filter_).
    Bitmap filterBmp = decodeResource(getResources(), R.drawable.tuibeauty_filter_biaozhun);

    10. Manage devices

    V2TXLivePusher provides a series of APIs for the control of devices. You can call getDeviceManager to get a TXDeviceManager instance for device management. For detailed instructions, please see TXDeviceManager API.

    11. Set the video mirroring effect for audience

    Call setEncoderMirror in V2TXLivePusher to set the camera mirror mode, which affects the way video images are presented to audience. By default, the local video watched by the host is flipped when the front camera is used, which creates the same effect as a mirror does. The video watched by audience is the same as that watched by the host, as shown below.

    12. Publish streams in landscape mode

    In most cases, hosts stream while holding their phones vertically, and audience watch videos in portrait resolutions (e.g., 540 × 960). However, there are also cases where hosts hold phones horizontally, and ideally, audience should watch videos in landscape resolutions (960 × 540).
    By default, V2TXLivePusher outputs videos in portrait resolutions. You can publish landscape-mode videos to audience by modifying a parameter of the setVideoQuality API.
    V2TXLiveDef.V2TXLiveVideoEncoderParam param = new V2TXLiveDef.V2TXLiveVideoEncoderParam(V2TXLiveDef.V2TXLiveVideoResolution.V2TXLiveVideoResolution960x540);
    param.videoResolutionMode = isLandscape ? V2TXLiveVideoResolutionModeLandscape : V2TXLiveVideoResolutionModePortrait;

    13. Set audio effects

    Call getAudioEffectManager in V2TXLivePusher to get a TXAudioEffectManager instance, which can be used to mix background music and set in-ear monitoring, reverb, and other audio effects. Background music mixing means mixing into the published stream the music played by the host’s phone so that audience can also hear the music.
    Call the enableVoiceEarMonitor API in TXAudioEffectManager to enable in-ear monitoring, which allows hosts to hear their vocals in earphones when they sing.
    Call the setVoiceReverbType API in TXAudioEffectManager to add reverb effects such as karaoke, hall, husky, and metal. The effects are applied to the videos watched by audience.
    Call the setVoiceChangerType API in TXAudioEffectManager to add voice changing effects such as little girl and middle-aged man to enrich host-audience interaction. The effects are applied to the videos watched by audience.
    For detailed instructions, please see TXAudioEffectManager API.

    14. Set watermarks

    Call setWatermark in V2TXLivePusher to add a watermark to videos output by the SDK. The position of the watermark is determined by the (x, y, scale) parameter passed in.
    The watermark image must be in PNG rather than JPG format. The former carries opacity information, which allows the SDK to better address the image aliasing issue (changing the extension of a JPG image to PNG won’t work).
    The (x, y, scale) parameter specifies the normalized coordinates of the watermark relative to the resolution of the published video. For example, if the resolution of the published video is 540 x 960, and (x, y, scale) is set to (0.1, 0.1, 0.1), the actual pixel coordinates of the watermark will be (540 x 0.1, 960 x 0.1). The width of the watermark image will be the video width x 0.1, and the height will be scaled automatically.
    // Set a video watermark
    mLivePusher.setWatermark(BitmapFactory.decodeResource(getResources(),R.drawable.watermark), 0.03f, 0.015f, 1f);

    15. Inform hosts of poor network conditions

    Hosts should be informed when their network conditions are bad and be prompted to check their network.
    You can capture the V2TXLIVE_WARNING_NETWORK_BUSY event using onWarning in V2TXLivePusherObserver. The event indicates poor network conditions for hosts, which result in stuttering for audience. When this event occurs, you can send a UI message about poor network conditions to hosts.
    public void onWarning(int code, String msg, Bundle extraInfo) {
    if (code == V2TXLiveCode.V2TXLIVE_WARNING_NETWORK_BUSY) {
    showNetBusyTips(); // Show network tips

    16. Send SEI messages

    Call the sendSeiMessage API in V2TXLivePusher to send SEI messages. SEI refers to the supplementary enhancement information of encoded video. It is not used most of the time, but you can insert custom information into SEI messages. The information will be forwarded to audience by live streaming CDNs. The applications for SEI messages include:
    Live quiz: The publisher can use SEI messages to send questions to the audience. SEI can ensure synchronization among audio, video, and the questions.
    Live showroom: The publisher can use SEI messages to display lyrics to the audience in real time. The effects are not affected by reduction in video encoding quality.
    Online education: The publisher can use SEI messages to display pointers and sketches on slides to the audience in real time.
    Custom data is inserted directly into video data and therefore cannot be too large in size (preferably several bytes). It’s common to insert information such as custom timestamps.
    //Sample code for Android
    int payloadType = 5;
    String msg = "test";
    mTXLivePusher.sendSeiMessage(payloadType, msg.getBytes("UTF-8"));
    Common open-source players or web players are incapable of parsing SEI messages. You must use V2TXLivePlayer, the built-in player of LiteAVSDK.
    1. Configuration:
    int payloadType = 5;
    mTXLivePlayer.enableReceiveSeiMessage(true, payloadType)
    2. If the video streams played by V2TXLivePlayer contain SEI messages, you will receive the messages via the onReceiveSeiMessage callback in V2TXLivePlayerObserver.

    Event Handling

    Listening for events

    The SDK listens for publishing events and errors via the V2TXLivePusherObserver delegate. See V2TXLiveCode for a detailed list of events and error codes.


    An error indicates that the SDK encountered a serious problem that made it impossible for stream publishing to continue.
    Event ID
    A common error not yet classified
    An invalid parameter was passed in during API calling.
    The API call was rejected.
    The API cannot be called.
    Failed to call the API due to invalid license.
    The server request timed out.
    The server could not handle your request.


    A warning indicates that the SDK encountered a problem whose severity level is warning. Warning events trigger tentative protection or recovery logic and can often be resolved.
    Event ID
    Bad network connection: data upload blocked due to limited upstream bandwidth.
    Stuttering during video playback.
    Failed to turn the camera on.
    The camera is occupied. Try a different camera.
    No access to the camera. This usually occurs on mobile devices and may be because the user denied the access.
    Failed to turn the mic on.
    The mic is occupied. This occurs when, for example, the user is having a call on the mobile device.
    No access to the mic. This usually occurs on mobile devices and may be because the user denied the access.
    The system does not support screen sharing.
    Failed to start screen recording. If this occurs on a mobile device, it may be because the user denied the access.
    Screen recording was stopped by the system.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support