ApsaraVideo Media Processing (MPS) provides the automated review feature that is implemented based on large amounts of tagged data and deep learning algorithms. This feature supports content moderation and content quality analysis. Content moderation detects prohibited content including pornography, terroristic content, politically sensitive content, and ads from multiple dimensions such as audio, text, and vision. Content quality analysis reviews the quality of videos. The automated review feature helps reduce the workload of manual reviews and improve the review efficiency and accuracy. This topic describes the automated review feature and how to create a content moderation job.
Overview
Scenarios
Accurate and efficient moderation for user-generated content (UGC): uses intelligent media review technologies to detect prohibited content and identify quality issues in large amounts of UGC. This reduces the workload of manual reviews.
Accurate and real-time content moderation for live streams: detects prohibited content in audio, text, and images of live streams in real time. This helps prevent business risks.
Efficient and accurate content moderation for on-demand videos: detects prohibited content such as terrorism-related and politically sensitive scenes in on-demand videos based on current affairs and politics.
Feature
For more information about the feature, see the "Automated review" section of the Functions and features topic.
For more information about how to experience this feature online, visit the Automated Review page of the Multimedia AI platform.
Limits
The automated review feature is available in the Asia Pacific SE 1 (Singapore) regions. Other regions are not supported.
Before you begin
Perform the following operations before you create a content moderation job:
Create an MPS queue for content moderation. If no MPS queue for content moderation is displayed in the MPS console, create and enable an MPS queue for content moderation.
Upload the video to be processed to OSS.
If you want to create a job, directly upload the video to OSS. For more information, see Upload videos.
If you want to create a workflow and automatically trigger the workflow, you must add media buckets and create a workflow before you upload the video. After you specify the input and output media buckets and upload a media file to the input media bucket, MPS receives a message about the upload and triggers the associated workflow. After the workflow is complete, the processed media file is uploaded to the output media bucket. For more information, see Add media buckets.
Optional. Enable the notification feature. If you want MPS to send notifications on jobs and workflows to MNS topics or queues, configure an MNS queue or topic as required. For more information, see Set up notifications.
Create a content moderation job in the MPS console
Create a content moderation job
Log on to the MPS console.
In the top navigation bar, select a region from the drop-down list.
In the left-side navigation pane, choose Job Management.
Click the Video Review tab, and then click Create Task.
On the Create Content Moderation Task page, configure the parameters that are described in the following table.
Parameter
Description
Input File URL
Click Select. From the Bucket drop-down list, select a bucket. The folders in the bucket are displayed under Path. Select a file from a folder as the input file.
NoteIf no bucket name is displayed in the Bucket drop-down list, add media buckets in the specified region. For more information, see Add media buckets.
If no files are displayed after you select an OSS bucket, go to the OSS console and upload files to the specified bucket.
If an error message appears to inform you that the current Resource Access Management (RAM) role is invalid or you do not have the required permissions, go to the RAM console to grant the RAM user the permissions to access OSS. You can attach the AliyunOSSFullAccess policy to the RAM user to grant the RAM user full permissions on OSS, or you can customize permissions based on your business requirements. For more information, see Create a RAM user and grant permissions to the RAM user.
Content Moderation Pipeline
From the Content Moderation Pipeline drop-down list, select a pipeline.
NoteIf no MPS queue name is displayed in the drop-down list, create and enable an MPS queue for content moderation. For more information, see Create an MPS queue.
Moderation Type
By default, Pornography and Terrorism are selected.
Storage Path
Click Select. From the Bucket drop-down list, select a bucket. The folders in the bucket are displayed under Path. Select a folder as the output path.
NoteIf the output path is the same as the input path, specify an output file name that is different from the input file name. This way, the input file is not overwritten. If the input file and output file share the same name, the relevant OSS settings determine whether the output file overwrites the input file. For information about how to disable file overwriting, see Prevent objects from being overwritten by objects that have the same names (OSS SDK for Java 1.0). If you disable file overwriting, the transcoded output file that shares the same name as the input file fails to be written to the OSS bucket. We recommend that you do not specify the same name for the input and output files.
For other common issues, see the description for Input File URL.
Click Submit to create and submit the content moderation job.
After the job is submitted, you can view the status and configurations of the job. You can also click the name of the job to view other information, such as the input and output paths.
Create a content moderation workflow
Log on to the MPS console.
In the top navigation bar, select a region from the drop-down list.
In the left-side navigation pane, choose Workflow > Workflow Orchestration.
Click Create Workflow.
-
Configure the basic information for the workflow.
Parameter
Description
Workflow Name
Enter a name for the workflow.
Preset
Select Custom from the drop-down list.
Configure the Input node.
Click the pencil icon on the right of the Input node to open the Input Settings page.
In the Input dialog box, configure the parameters that are described in the following table.
Parameter
Description
Input Path
Click Select. From the Bucket drop-down list, select a bucket. The folders in the bucket are displayed under Path. Select a folder as the input path.
NoteIf no bucket name is displayed in the Bucket drop-down list, add media buckets in the specified region. For more information, see Add media buckets.
MPS Queue for Transcoding
The MPS queue for content moderation.
NoteThe MPS queue specified for this parameter is used for transcoding and snapshot jobs. You can specify an MPS queue for content moderation when you configure subsequent nodes.
If no pipeline is available in the MPS Queue for Transcoding drop-down list, first create one. For more information, see Create a pipeline.
(Optional) Notifications
Optional. Specifies whether to send notifications about the workflow. If you turn on Notifications, configure the Message Type parameter and select a Simple Message Queue (SMQ) queue or topic from the Queue Name or Topic Name drop-down list.
NoteIf no SMQ queue name or topic name is displayed in the drop-down list, create an SMQ queue or topic and enable the notification feature based on the SMQ queue or topic. For more information, see Enable the notification feature for a media workflow.
Click OK to finish configuring the Input node.
Add a Content Moderation node.
Click the plus sign icon (+) to the right of the Input node and select review.
Click the pencil icon on the right of the Content Moderation node.
Set the Content Moderation parameters.
Parameter
Description
Moderation Pipeline
The MPS queue for content moderation.
NoteIf no pipeline is available in the Moderation Pipeline drop-down list, first create a dedicated pipeline for content moderation.
Output Path
Click Select and choose an OSS output location.
Workflow Termination
Configure this parameter based on your business requirements.
Click OK to finish configuring the review node.
Configure the Publish node.
Click the pencil icon on the right of the Publish node.
In the Publish dialog box, configure the parameter that is described in the following table.
Parameter
Description
Publish Type
Set Publish Type to Auto.
Manual: After the workflow runs successfully, the workflow sets the media status to unpublished. You can then publish the media manually. For information about how to manually publish media files, see Manage media assets.
Auto: After the workflow runs successfully, the workflow sets the media status to published.
NoteIf this parameter is set to Auto, the access permissions on all resources related to the output video, including playback files and captured video images, are the same as those on the OSS bucket in which the output video resides.
If this parameter is set to Manual, all these resources can be accessed only by the current user.
Click OK to finish configuring the Publish node.
Click Save to create the workflow.
If a file is uploaded to the path specified by the Input Path parameter after the workflow is created, the workflow is triggered.
Create a content moderation job by calling an API operation
Submit a content moderation job.
You can specify the URLs of videos, images, or audio files stored in an OSS bucket or the URLs of videos stored in a third-party service in the request when you call the SubmitMediaCensorJob operation to submit a content moderation job. For more information, see Submit a content moderation job.
Receive a callback notification.
If the notification feature is enabled for the content moderation job, you can receive a notification in the specified Simple Message Queue (formerly MNS) queue or topic after the content moderation job is complete. For more information, see Receive notifications.
Query the results of the content moderation job.
You can call the QueryMediaCensorJobDetail operation to query the status and results of the content moderation job by job ID. For more information, see QueryMediaCensorJobDetail.