Features

Flix Cloud supports today's most popular formats and includes all the necessary encoding & decoding licenses*.

Note: Flix Cloud only supports encoding and decoding audio streams within video container files. We don't support standalone audio containers such as .MP3 .M4A and .WMA.

Flix Cloud can output:

One- and two-pass encoding for Flash video (On2 VP6, H.264 and Spark/h.263)

Baseline, Main and High H.264 profiles

MP3 and AAC+ audio

Baseline H.263 video profile & AMR audio for 3GPP

Windows Media video & audio

Flix Cloud also provides many preprocessing filters including:

Video

Datarate increase/decrease

Scaling/resizing (with or without aspect ratio preservation)

Video overlay watermarking (with or without transparency)

Framerate controls

Automated PNG thumbnail creation (first frame, regular interval, random interval and more)

Keyframe type/interval

Deinterlacing (adaptive, 1:2:1 blur, drop field)

Noise reduction

In/out cutting

Cropping

Hue, saturation, brightness, contrast

Sharpen/blur

Mirror/rotate

Audio

Resampling

Datarate increase/decrease

The Flix Cloud Dashboard lets you view jobs that are waiting, in progress, and completed. The Dashboard lets you see reports and statistics (like average processing time) and see a running tally of your Flix Cloud fees.

Screenshots (click to expand)

Flix Cloud is built to scale as far as you need it to, by distributing transcoding jobs across multiple Amazon EC2 servers. This means very high throughput, enabling you to transcode more videos in less time than with a single transcoding server.

By "less time" we mean slashing your transcoding queues from weeks to hours. (Seriously, no kidding.)

All of our On2 Flix Engine transcoding servers run on Amazon EC2 High-CPU Medium instances, and we can create more as needed, immediately, to ensure short queues and the highest quality of service.

The Flix Cloud application and database servers are hosted in a secure facility at On2 headquarters, with redundant failover in our secure remote co-location center.

Reliability is one of the biggest challenges of a video transcoding system. Flix Cloud is extremely reliable, such that it is almost impossible for jobs to be lost.

We run a minimum of three On2 Flix Engine instances within Amazon EC2 at all times, so there is always a server available to transcode your jobs. If there are a lot of job requests, we simply start as many more Flix Engines as we need.

Also, Flix Cloud is a self-healing application; if a transcoding job is interrupted for some reason, another Flix Engine instance will automatically finish the job.

Your application can integrate with Flix Cloud through a simple, well-documented API using XML and REST web services with minimal coding.

Flix Cloud supports a bunch of transcoding settings and filters, so to make things easier we've designed a "Recipe" scheme to manage your transcoding settings. We also include a custom API element that you can use for whatever purpose you like (for example, server origin or authentication). You can start from our optimized Flix Cloud Recipes and tweak them in your Dashboard to make them your own.

When Flix Cloud finishes transcoding a file, it transfers the output to your preferred data store (Amazon S3, or a file server over ftp or sftp). Flix Cloud will then send your application an XML message containing the location of the output file and other information.

Note that Amazon S3 storage fees will apply for files written to your S3 bucket.

Supported File Transfer Protocols

Amazon S3 (s3://)

Requires that you give Flix Cloud access to your S3 bucket. (We recommend S3 for fastest file transfer in & out of Flix Cloud.)

ftp/sftp

Supports basic ftp authentication.

http/https

Only supported for input files or watermark image location, not output files. Supports basic http authentication.