Video Moderation / Principles

Video Moderation Principles

Introduction

Sightengine's Video Moderation API works with any type of video or stream:

  • Static videos, meaning video files such as an MP4 file you might have available on a server
  • Streamed videos (also referred to as streams) meaning videos that are being consumed from a streaming resource. This could be a live video feed, a video-conferencing stream, or any video feed

Sequential or Continuous Moderation

There are two ways to moderate a Video, depending on the type of video. You can either do a so-called sequential moderation or a continuous moderation. While both yield the same results, they differ by their implementations. Here are the pros and cons of each:

  • Sequential moderation is easier and quicker to set up. The drawbacks being that it might be a bit slower and that it only works for short videos (less than 60 seconds and 50 megabytes). We first process the whole video, then send you the full results.
  • Continuous moderation requires more integration work, but it works with any video or stream and enables you to detect offending content a bit faster than with sequential moderation.
Sequential Moderation
  1. Your back-end submits a video and waits
  2. Sightengine reads the video, and analyzes it
  3. Once finished, the full results are sent back and the connection is closed
Continuous Moderation
  1. Your back-end submits a video and gets a stream ID from Sightengine
  2. Sightengine analyzes the video, and creates alerts each time offending content is found
  3. Your back-end receives callbacks (through webhooks) to inform you of any offending content. Or you can poll Sightengine to ask for status updates and moderation progress and results
  4. Once finished, the full results are sent to your server through a webhook

Did you find this page helpful?

We're always looking for advice to help improve our documentation!

Let us know what you think