Integration Methods

If you would like to user Microsoft Azure Blob storage as a source or destination, please follow these simple steps:

- Use a standard URL to access a source or destination locatlon: http(s)://[access_key]@[account].blob.core.windows.net/[container]/path
- Ensure to URL encode any special characters within the access_key 

Here is one example of a properly constructed URL:
http://P9DM47UTCF%2BQJZXl0uWy28J4jBdgnYv0SJPh%2FR%2AWCFOLPTBHuyeXtMfDOU75Wd0Yl2xm67vVTYGVAWSEDRdcw%3D%3D@[account].blob.core.windows.net/encoding/file.ext

Special notes for Azure Blob Storage:

- Your container name must consist of 3-63 characters, digits or sign "-". Please make sure to not have a "-" at the beginning or end of your container name.  
- If you do not include the access_key within your URL, they will be interpreted like casual urls. files in such urls should be public readable.

The Vid.ly PRO API can be used to obtain status information on jobs, by BatchID or MediaShortlink:

<?xml version="1.0"?>
<query>
  <action>GetStatus</action>
  <userid>[UserID</userid>
  <userkey>[User_Key]</userkey> 
<notify>[User_Email]</notify>
<BatchID>[BatchID_or_MediaShortlink]</BatchID>
</query>

Response:

<?xml version="1.0"?>
<Response>
<Message>[Success]</Message>
<MessageCode>[MessageCode]</MessageCode>
<Success>
<Task>
<UserID>[UserID]</UserID>
<MediaShortLink>[MediaShortLink]</MediaShortLink>
<SourceFile>[SourceFile]</SourceFile>
<BatchID>[BatchID]</BatchID>
<Status>[Status]</Status>
<Created>[LinkCreatedDate]</Created>
<Updated>[LinkUpdatedDate]</Updated>
<UserEmail>[UserEmail]</UserEmail>
</Task>
<Task>
</Task>
</Success>
<Errors> <!-- if file is not in Success section, it must be in this one -->
<Error>  <!-- Relates to the appropriate SourceFile in the request list -->
<SourceFile>[SourceFileK]</SourceFile>
<ErrorCode>[ErrorCodeID]</ErrorCode>
<Description>[ErrorDescriptionK]</Description>
<Suggestion>[ErrorSuggestionK]</Suggestion>
</Error>
</Response>

In order to best serve our loyal customers, we have implemented a feature request voting system here: http://vidly.uservoice.com/forums/125877-feature-requests.  These feature requests, as they gain votes, will help us on the Encoding.com team prioritize fixes and additions to the system. We hope here at Encoding.com, you'll take  this very hands on approach will help us maintain and grow the largest encoding service out there.

Sounds like you have lots of encoding to do there!

With Encoding.com's powerful API or snappy watch folders, you can request a maximum of 100 tasks per encode, or folder respectively. 

Yes! You can select the following choices in our watch folders to create files specifically targeted for playback via Roku. 

Click on any of the links below to expose the templates that we use for each preset:

roku_800
roku_1200
roku_1800
roku_2700
roku_hls

Preparing videos for use with the Wowza Media Server can be accomplished very simply using one of the Wowza Presets on Encoding.com.  Choose a Preset, set a destination location for output files and you're off and running.  You can send output files to any location but most likely you'll want to send them directly to your Wowza server.  

1. Wowza Preset for Single Bitrate output: quick setup to generate a single video output in .mov format

When using the web interface, select the "Wowza" preset from the Format drop-down menu to generate a static bitrate video output:

For API jobs, use this XML template:

<format>
<output>wowza</output>
<destination>ftp://your.server.com/output/wowza_test_video.mov</destination>
<size>320x240</size>
<bitrate>256k</bitrate>
<audio_bitrate>128k</audio_bitrate>
<audio_sample_rate>48000</audio_sample_rate>
<audio_channels_number>2</audio_channels_number>
<framerate>24</framerate>
<keep_aspect_ratio>yes</keep_aspect_ratio>
<video_codec>libx264</video_codec>
<profile>main</profile>
<audio_codec>libfaac</audio_codec>
<two_pass>no</two_pass>
<turbo>no</turbo>
<twin_turbo>no</twin_turbo>
<cbr>no</cbr>
<deinterlacing>no</deinterlacing>
<keyframe>300</keyframe>
<audio_volume>100</audio_volume>
<file_extension>mov</file_extension>
<hint>no</hint>
</format>

2. Wowza Multi-bitrate Preset for Adaptive Bitrate output: quick setup to generate the SMIL index file, output video files (.mov) and the streaming manifest files (.txt)

When using the web interface, select "Wowza Multi-bitrate" from the Format drop-down menu to generate the necessary files for adaptive streaming:

For multi-bitrate API jobs, use this XML template:

<format>
<output>wowza_multibitrate</output>
<destination>ftp://your.server.com/output/wowza_test_video.smil</destination>
<audio_bitrate>128k</audio_bitrate>
<audio_sample_rate>48000</audio_sample_rate>
<audio_channels_number>2</audio_channels_number>
<framerate>24</framerate>
<keep_aspect_ratio>yes</keep_aspect_ratio>
<video_codec>libx264</video_codec>
<profile>wowza_multibitrate</profile>
<VCodecParameters>no</VCodecParameters>
<audio_codec>libfaac</audio_codec>
<two_pass>no</two_pass>
<turbo>no</turbo>
<twin_turbo>no</twin_turbo>
<cbr>no</cbr>
<deinterlacing>no</deinterlacing>
<keyframe>48</keyframe>
<audio_volume>100</audio_volume>
<file_extension>mov</file_extension>
<hint>no</hint>
<bitrates>270k,570k,1000k,1200k,1400k</bitrates>
<sizes>320x180,420x270,720x406,1024x576,1080x608</sizes>
</format>

Sample output SMIL syntax

<smil>
<head>
</head>
<body>
<switch>
<video src="mp4:wowza_multibitrate_aligned_kf_400.mov" system-bitrate="400000"/>
<video src="mp4:wowza_multibitrate_aligned_kf_700.mov" system-bitrate="700000"/>
<video src="mp4:wowza_multibitrate_aligned_kf_1100.mov" system-bitrate="1100000"/>
<video src="mp4:wowza_multibitrate_aligned_kf_1300.mov" system-bitrate="1300000"/>
<video src="mp4:wowza_multibitrate_aligned_kf_1500.mov" system-bitrate="1500000"/>
</switch>
</body>
</smil>

Sample output Smooth Streaming manifest header

<?xml version="1.0" encoding="utf-8"?>
<SmoothStreamingMedia MajorVersion="2" MinorVersion="1" Timescale="10000000" Duration="1471670000">
<StreamIndex Type="audio" Index="0" Chunks="74" QualityLevels="1" Timescale="10000000" Url="QualityLevels({bitrate})/Fragments(audio={start time})/Chunks({chunk id})/WowzaSessions(2133794089).isma">
<QualityLevel Bitrate="127473" FourCC="AACL" SamplingRate="48000" Channels="2" BitsPerSample="16" PacketSize="4" AudioTag="255" CodecPrivateData="1190" />

Well, sounds like you're new to the platform, right?

Your objectives are to encode a video and deliver it someplace.

Here's where to start:

Beginner:

Most folks log into the UI @ http://www.encoding.com and select 'Start a new job' from the list of choices on the left in order to test drive the system. Run through this a couple times, as adding media one a time is a great way to get started with the platform. Try adding a few tasks to your source media for multiple outputs.  Make sure to take a peek at the Encoding Queue, as you'll have to manually select files you add via 'Start a new job' to process manually. Want to skip this step? Set up a watch folder and automagically content will be pulled from your source location and processed. 

Intermediate:

Setting up a watch folder on Amazon S3, Rackspace or your local FTP site is easy. Log into the UI, select 'Watch Folder' from the list on the left and select 'Add New.' Configure the URLs to hit your source location, deliver to your preferred destination, add a notify, then add a few tasks to the folder. If you have any questions on configuring FTP, S3 or Rackspace URLs, then make sure to check out the following article: http://www.encoding.com/how_can_i_specify_where_my_source_media_is_located

Advanced:

Wanna jump in with both feet and utilize Encoding.com's powerful API to submit your content to our platform?

Find all the resources you need here:

http://www.encoding.com/api/

http://www.encoding.com/api/category/category/complete_api_documentation

Encoding.com does not use FTP passive mode by default when retrieving or placing files. To use FTP with passive mode turned on, add ?passive=yes to the end of your FTP URL string (either source or destination): ftp://user:pass@ftphost.tld/path/to/your/file.ext?passive=yes

Once your encoding job is complete tell your Flowplayer where to find your encoded video on HDDN:
Click on the "Minimal Setup" from your saved setup
View the source code and copy & paste it to your site. Change the clip url to the one you set as the destination in your encoding settings.

It's something like this: ftp://usename:password@hddn-userId.com/examplefolder/sourcevideo.mov

You're almost done! Use Flowplayers direct link or embed code to view your player in a browser and click play to test the entire playback of the video prior to publishing. You can always go back to the encoding.com interface and reencode the video with different encoding parameters to meet your needs. Submit any questions through the "Contact Support" link in your encoding.com control panel.

We test video playback on a variety of devices, from Mac and Windows PCs, to all the various mobile phone platforms available today. One critical issue that comes up often is that the hosting server has not set the MIME types for the video type. A typical error message for this would be "unknown application/octet-stream". Here is a list of many common formats we encounter.

IMPORTANT: You will need to configure your ftp server to these MIME types for them to be properly recognized by their respective playback devices.

Using Amazon S3 is a snap. Follow these directions to get you started

1) Manually set the Amazon S3 object to have READ permission for the AWS user fastencoding: 1a85ad8fea02b4d948b962948f69972a72da6bed800a7e9ca7d0b43dc61d5869.

This is a requirement for encoding.com to read the file(s).  To do this, log into your AWS console, right click on the bucket and select 'Properties' Add the string and wait for a moment, as it resolves to 'fastencoding'. Give this user upload/delete permissions.

2) Use the following format for the source url: http://[bucket].s3.amazonaws.com/[filename] Amazon provides some excellent documentation about ACL permissions, visit this link for details:

http://docs.amazonwebservices.com/AmazonS3/latest/dev/

Important notes: 

**Do not use capitalization in your bucket names. You will receive a 403 error. Please only use lowercase letters.

There are a few steps that need to occur before videos can be uploaded directly to your blog from Encoding.com.

First, ensure that you have downloaded and added the latest plugin to your blog's directory:

http://wordpress.org/extend/plugins/encodingcom-wordpress-plugin/

Second, follow the directions on installation here:

http://wordpress.org/extend/plugins/encodingcom-wordpress-plugin/installation/

- - -

In the Wordpress article creation: There is a Encoding.com "E" icon next to the row of Upload/Insert Icons which will give you access to the WP Encoding.com plugin.

1. Click "Add New" Post

2. Click the Encoding.com "E" icon in the row of Upload/Insert Icons

3. Click "Select a Video" button to select a source video from your hard drive to upload.

4. After upload and transcoding is complete you will see a list of all converted videos in a list

5. Click the "Show" link next to the video you want to insert into your post. Click "Insert into Post" to automatically insert the video code into your blog.