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.
VOD supports the following upload methods:
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 |
---|---|
Beijing | ap-beijing |
Shanghai | ap-shanghai |
Chongqing | ap-chongqing |
Tianjin | ap-beijing-1 |
Hong Kong, China | ap-hongkong |
Singapore | ap-singapore |
Mumbai (India) | ap-mumbai |
Seoul | ap-seoul |
Bangkok | ap-bangkok |
Tokyo | ap-tokyo |
Silicon Valley (Western US) | na-siliconvalley |
Virginia (Eastern US) | na-ashburn |
Toronto | na-toronto |
Frankfurt | eu-frankfurt |
Moscow | eu-moscow |
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 the Singapore storage region. You can activate other storage regions based on your actual business needs. For detailed directions, please see Upload Storage Settings. Once activated, a storage region cannot be deactivated.
In all of your activated storage regions, only one will be used as the default region. If you have only one activated region (Singapore), 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.
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.
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 |
Live recording | The VOD backend will select the storage region nearest to the region of the live push |
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 |
Live recording | Not supported |
VOD supports uploading media files in the following formats:
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 |
---|---|
|
NewFileUpload |
|
PullComplete |
VOD media upload provides multiple additional features for media asset management, video processing and event notification, and upload control.
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 | Live 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 |
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 | Live 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 | |
Passthrough 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 |
Passthrough field in upload event notification | Not supported | Not supported | sourceContext parameter in the signature for upload from client |
Not supported | Not supported |
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 | Live 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 |
|
N/A | N/A |
Upload Method | Maximum Media File Size |
---|---|
|
60 GB |
|
48.82 TB (50,000 GB) |
|
10 GB |
Live recording |
|
Was this page helpful?