Media asset upload FAQ

File stuck in uploading state

This can be caused by one of the following reasons:

• Cause 1: URL-based upload is an asynchronous process and does not guarantee timely completion.

  The URL-based upload method is asynchronous and does not guarantee timely completion. Uploads may take several hours or even days to complete. This method is available only in the China (Shanghai), China (Beijing), China (Shenzhen), Singapore, and US (Silicon Valley) regions. We recommend that you integrate the ApsaraVideo VOD server-side upload SDK for uploads.

• Cause 2: You only generated an upload credential without uploading the file.

  Calling the CreateUploadVideo API only obtains an upload credential and creates basic media asset information. It does not upload the actual file. You still need to call OSS operations to complete the file upload. For the complete procedure, see Upload media files by calling the ApsaraVideo VOD API.

• Cause 3: The upload is slow because the file is large.

  Check if the upload duration is reasonable for the file size. By default, methods such as using the console, upload SDKs, and client tools use multipart upload, which supports single files up to 48.8 TB. The upload SDK also provides a simple upload feature, which supports single files up to 5 GB.

• Cause 4: Network issues.

  Verify that your network bandwidth meets the requirements.

iOS SDK upload fails with NSCocoaErrorDomain error

URL-based upload: "not open in current region" error

The error message The service is not open in current region indicates that URL-based upload is not supported in the current region. This feature is available in limited regions, including China (Shanghai) and Singapore.

If you are in an unsupported region, download the files locally and then upload them by using an upload SDK. For more information, see Upload SDK overview.

Cannot view uploaded images in the console

Images uploaded with the type set to cover are treated as video covers and are not displayed in the ApsaraVideo VOD console. They can only be retrieved by calling an API. For more information, see CreateUploadImage.

JavaScript SDK upload compatibility issue in WeChat

This issue is caused by a compatibility problem with the HTML5 implementation in the WeChat browser. To resolve this, remove the multiple="" parameter from the <input type="file" name="file" id="files" multiple=""> tag.

Stretched preview with the stream ingest SDK

When you select 480p as the stream resolution in the stream ingest SDK, the preview page may appear stretched, but the actual stream output is normal. This happens because 480p corresponds to a resolution of 480×640 pixels. Because this aspect ratio is not supported by most mobile phone screens, the preview appears stretched.

public void initView() {
    mPreviewView = (SurfaceView) findViewById(R.id.preview_view);
    mPreviewView.getHolder().addCallback(mCallback);
}

<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="match_parent">
    <SurfaceView
            android:id="@+id/preview_view"
            android:layout_width="match_parent"
            android:layout_height="match_parent"/>

    <!--FrameLayout-->
        <!--android:id="@+id/publisher_fragment"-->
        <!--android:layout_width="match_parent"-->
        <!--android:layout_height="match_parent"-->
        <!--android:visibility="gone"/>-->

    <android.support.v4.view.ViewPager
            android:id="@+id/tv_pager"
            android:layout_width="match_parent"
            android:layout_height="match_parent"
            >
    </android.support.v4.view.ViewPager>
</RelativeLayout>

View and import AAR packages in Android Studio

To view the data in an AAR package, change the file extension from .aar to .zip and then decompress the file. You can then view its contents, such as .class files, .xml files, .jar files, images, and text files.

Related links