Using Microsoft’s Smooth Streaming (MSS) with Encoding.com

Microsoft's Smooth Streaming (MSS) To stream media over HTTP using Microsoft's Smooth Streaming protocol chose the “Smooth Streaming” preset from the encoding.com client interface, watch folder, or API. NOTE: Because the Smooth Streaming output creates multiple files from a single source file you have the option to tar the output tar = yes, in which Read more

By

Do you have an audio normalization feature?

Varying content and varying edit styles can cause unexpected results during compression. Correct any and all issues with audio normalization. This will correct variances in dialogue, natural sound and background music. There is no default value for this tag. Please specify a non-negative integer between 0 and 100 for this value.

By

What frame rate controls are available?

Looking to gain some control over your encodes, especially if your content varies in frame rates. Check out our threshold settings. If your source frame rate is lower then the framerate_upper_threshold, your source frame rate will be used. For example, if your source frame rate is 23.98 fps, and the threshold is set to 30, Read more

By

Using Adobe’s HTTP Dynamic Streaming (HDS) with Encoding.com

To stream on-demand media over HTTP using Adobe's HTTP Dynamic Streaming (HDS) protocol chose the preset “Dynamic Streaming” from the encoding.com client interface/watch folder, or the parameter “HDS” from the Encoding.com API. NOTE: To use Adobe's HDS, the source media must be in MP4, FV4, or FLV compatible formats.  Please transcode your video into one Read more

By

Can I receive a notification only on errors?

To receive a notification only where a job errors, designate a URL or email address for <notify_encoding_errors>, you will receive information when a job contains errors. This is in additon to the regular <notify> field for completion of all job processes. 

By

Turbo and Twin Turbo works on files 500 MB and larger

Now processing cores are utilized automatically as follows: All jobs under 100mb are processed with 4 cores. All jobs between 100mb and 500mb are processed with 8 cores. All jobs over 500mb are processed with 16 cores. This is automatic and happens by default.

By

Smooth Streaming Template

<?xml version=”1.0″?> <query>     <userid>[]</userid>     <userkey>[]</userkey>     <action>AddMedia</action>    <notify/>    <notify_encoding_errors/>    <source/>     <format>         <output>smooth_streaming</output>         <rotate>def</rotate>         <audio_codec>libfaac</audio_codec>         </destination>         <pack_files>yes</pack_files>     </format> </query>  

By

How can I use GetStatus extended mode?

Reduce your request rates per second with this handy workflow. Need to find out the status of many mediaIDs at once? .. plus their task ID? … plus their STATUS? Request: Response:

By