Overview

Last updated: 2020-10-22 11:26:14

    Media upload refers to upload of media files such as videos, audios, and cover images to VOD's storage capacity, so that the files can be further processed or distributed.

    Upload Methods

    VOD supports the following upload methods:

    • Local upload through console
      You can upload local media files to VOD on the upload page of the VOD Console. This method allows you to upload files with speed and ease and has no requirement for technical experience, making it suitable for direct management of a small number of media files.
    • Pull through console
      This method is implemented on the upload page of the VOD Console. You can specify the URL of the media file to be uploaded, and the VOD backend will pull the file offline.
    • Upload from server
      You can upload media files stored on your backend server to VOD. This method is suitable for automated and systematic production environments. VOD provides the following upload from server SDKs for different programming languages:
    • Upload from client
      This method allows end users to upload local videos on the client to VOD, which is suitable for scenarios such as UGC and PGC. VOD provides upload from client SDKs for the following platforms:
    • Pull through API
      When using the PullUpload API, you can specify the URL of the media file to be uploaded, and the VOD backend will pull the file offline. This method is suitable for migration of a large number of files or automated file migration.
    • LVB recording
      You can use the recording feature of VOD to save video content of LVB streams to VOD for archiving, clipping, and replay.

    Storage Regions

    List of supported regions

    VOD has storage nodes in multiple regions around the globe. During media upload, files will be stored in the specified region. Currently, VOD supports the following storage regions:

    Storage Region Region Abbreviation
    Hong Kong (China) ap-hongkong
    Singapore ap-singapore
    Mumbai ap-mumbai
    Seoul ap-seoul
    Bangkok ap-bangkok
    Silicon Valley na-siliconvalley
    Eastern US na-ashburn
    Toronto na-toronto
    Frankfurt eu-frankfurt

    Activating storage regions

    An important purpose of configuring multiple storage regions is to improve media upload quality (success rate and speed), which is subject to the distance between the uploader and storage node. Generally, the shorter the distance, the better the upload quality.

    After you activate the VOD service, VOD will automatically assign Toronto, Frankfurt, Hongkong, Mumbai, Tokyo, Seoul, Moscow, Singapore, Bangkok, and Ashburn as storage regions. You can enable other storage regions (such as Chinese mainland) based on your actual business needs. For detailed directions, please see Upload Storage Settings. Once activated, a storage region cannot be deactivated.

    Default storage region

    In all of your activated storage regions, only one will be used as the default region. If you have only one activated region, it will be the default storage region; if you have activated multiple storage regions, you can select another region as the default storage region in the console. For detailed directions, please see Storage Region Settings.

    Purpose of the default storage region: in some scenarios, this region will be first selected as the target region for media upload. For more information, please see the following section.

    Selecting a storage region

    A specified storage region is needed for media upload, which can be automatically selected by the VOD backend by default or be specified in the upload request.

    • When the VOD backend automatically selects the storage region:
      • If you have only one storage region, all uploaded media files will be stored in this region.
      • If you have activated multiple storage regions, the region selection policies for different upload methods are as follows:
        Upload Method Region Selection Policy
        Local upload through console The VOD backend will select the storage region nearest to the uploader
        Pull through console The default storage region will always be selected
        Upload from server The VOD backend will select the storage region nearest to the uploader
        Upload from client The VOD backend will select the storage region nearest to the uploader
        Pull through API The default storage region will always be selected
        LVB recording The VOD backend will select the storage region nearest to the region of the LVB push
    • You can specify the storage region for different upload methods in the following ways:
      Upload Method Region Designation Method
      Local upload through console Not supported
      Pull through console Not supported
      Upload from server
      Upload from client Signature for upload from client
      Pull through API `StorageRegion` parameter in the `PullUpload` API
      LVB recording Not supported

    Features and Limits

    Media types

    VOD supports uploading media files in the following formats:

    • Video: MP4, TS, FLV, WMV, ASF, RM, RMVB, MPG, MPEG, 3GP, MOV, WEBM, MKV, and AVI
    • Audio: MP3, M4A, FLAC, OGG, and WAV
    • Cover image: JPG, JPEG, PNG, GIF, BMP, TIFF, AI, CDR, and EPS

    Event notifications

    After a media file is uploaded, the VOD backend can notify you of this event. For more information on how event notifications work and how to configure them, please see Event Notification and Configuring Event Notification, respectively.
    The event notification types of different upload methods are as below:

    Upload Method Event Notification Type
    • Local upload through console
    • Upload from server
    • Upload from client
    • LVB recording
    NewFileUpload
    • Pull through console
    • Pull through API
    PullComplete

    Additional features

    VOD media upload provides multiple additional features for media asset management, video processing and event notification, and upload control.

    Media asset management features

    • Adding a cover: you can upload an image together with a video, and this image will be automatically set as video cover in the VOD media asset system.
    • Specifying the expiration time: you can specify the expiration time of a media file when uploading it. After the specified time elapses, the VOD backend will automatically delete the media file and its associated files (e.g., output files and screenshots).
    • Specifying the category: you can specify the category for the media file after it is uploaded.

    Support conditions and usage of different upload methods are as shown below:

    Feature Local upload through console Pull through console Upload from server Upload from client Pull through API LVB recording
    Adding a cover Not supported Not supported CoverUrl parameter in the PullUpload API Not supported
    Specifying the expiration time Not supported Not supported Not supported ExpireTime parameter in the PullUpload API Recording configuration
    Specifying the category Specifying category Not supported ClassId parameter in the signature for upload from client [ClassId parameter in the PullUpload API] Not supported

    Video processing and event notification

    • Automatic video processing: you can specify a task flow for media upload. After upload is completed, VOD will automatically execute this task flow. Common scenarios of this feature are screencapturing the first video frame as cover, transcoding, and content audit.
    • Passing through field in video processing event notification: if automatic video processing is enabled, after video is processed, the VOD backend will initiate an event notification to pass through this field to you.
    • Passing through field in upload event notification: after upload is completed, the VOD backend will initiate an event notification to pass through this field to you.

    Support conditions and usage of different upload methods are as shown below:

    Feature Local upload through console Pull through console Upload from server Upload from client Pull through API LVB recording
    Automatic video processing Automatic video processing after upload Not supported procedure parameter in the signature for upload from client Procedure parameter in the PullUpload API Not supported
    Passing through field in video processing event notification Not supported Not supported Not supported sessionContext parameter in the signature for upload from client SessionContext parameter in the PullUpload API Not supported
    Passing through field in upload event notification Not supported Not supported sourceContext parameter in the signature for upload from client Not supported Not supported

    Upload control

    • Checkpoint restart: if the upload is terminated unexpectedly due to causes such as network disconnection and closing of the browser, you can upload the file again from where it left off without the need to upload the entire file again.
    • Pausing/resuming upload: during the upload, you can proactively pause or resume the upload.
    • Canceling upload: during the upload, you can proactively cancel the upload.
    • Getting upload progress: you can get the upload progress, i.e., the size ratio of the part already uploaded to VOD to the full file size.
    • Multipart upload: during the upload, a media file will be divided into multiple parts for separated upload. If you are on a weak network, this feature can reduce the affect of disconnection caused by network exceptions. If your bandwidth is high, this feature can concurrently upload multiple parts to make full use of the network bandwidth.

    Support conditions and usage of different upload methods are as shown below:

    Feature Local upload through console Pull through console Upload from server Upload from client Pull through API LVB recording
    Checkpoint restart Not supported N/A Not supported N/A N/A
    Pausing/resuming upload Not supported N/A Not supported N/A N/A
    Canceling upload Refresh or close the page in browser N/A N/A N/A StopLiveRecord
    Getting upload progress The progress is displayed on the page by default Not supported Not supported Not supported N/A
    Multipart upload Enabled N/A
    • It is enabled for the SDK for Web by default
    • It is enabled for the SDK for Android by default
    • It is enabled for the SDK for iOS by default
    • The SDK for WeChat Mini Program is not supported
    N/A N/A

    Limits

    • The limits on media file size are as below:
      Upload Method Maximum Media File Size
      • Local upload through console
      • Upload from client - SDK for Web
      60 GB
      • Upload from server
      • Pull through console
      • Pull through API
      48.82 TB (50,000 GB)
      • Upload from client - SDK for Android
      • Upload from client - SDK for iOS
      10 GB
      LVB recording
      • For MP4/FLV formats, the upper limit is 48.82 TB (50,000 GB)
      • There is no upper limit for files in HLS format
      • Other restrictions are subject to LVB recording
    • Number of files: unlimited.

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help