Tips and Tricks

Securing your iPhone streams is easy with Encoding.com's stream encrytion option. We encrypt your TS segements using AES-128 with no need for an additional processing step. The encryption passes on delivery, as opposed to requiring additional processing time. You'll need a few things to get started, so let's lay out all the details:

1)  Create 32 character hexadecimal string. (Noted as 128 bit key below.)

     Sample encryption key: 243F6A8885A308D313198A2E03707344. Don't confuse this with API keys, as the encryption key can only contain characters A - F & 0- 9.

     Sample of encryption key that will fail immediately: COq8MA6wT3aHxEIvGy4U3VNBa3BMch29

OR

     Create a file that contains the hex string. If you choose a file, this will overrride the hex key specified in the request.

3) Request an HLS encode with the following additions:

<format>
    <!-- Format fields -->
        <output>[iphone_stream|ipad_stream]</output>
        ...
        <encryption>[yes|no]</encryption>
        <encryption_key>[128bit-key]</encryption_key>
        <encryption_key_file>[SourceURL]</encryption_key_file> <----Use a key_file or a string value. Don't use both, as the file will override the key. 
        ...
    </format>

###

Full XML:

<?xml version="1.0"?>
<query>
  <action>AddMedia</action>
  <userid>[userid]</userid>
  <userkey>[userkey]</userkey> 
  <source>[source]</source>
  <notify/>
   <format>
   <output>iphone_stream</output>
  <size>480x320</size>
   <bitrate>512k</bitrate>
<destination>[URL]</destination>
   <audio_bitrate>40k</audio_bitrate>
   <audio_sample_rate>44100</audio_sample_rate>
   <audio_channels_number>2</audio_channels_number>
   <keep_aspect_ratio>yes</keep_aspect_ratio>
   <video_codec>libx264</video_codec>
   <profile>iphone_stream</profile>
   <audio_codec>libfaac</audio_codec>
   <two_pass>no</two_pass>
   <turbo>no</turbo>
   <cbr>no</cbr>
   <deinterlacing>yes</deinterlacing>
   <keyframe>300</keyframe>
   <audio_volume>100</audio_volume>
   <rotate>0</rotate>
   <file_extension>tar</file_extension>
   <hint>no</hint>
   <bitrates>600k,400k,200k,110k</bitrates>
   <framerates>29.97,29.97,15,10</framerates>
   <keyframes>90,90,45,30</keyframes>
   <pack_files>no</pack_files>
   <segment_duration>10</segment_duration>
   <add_audio_only>no</add_audio_only>
   <still_image>no</still_image>
   <still_image_time>5</still_image_time>
   <still_image_size>480x320</still_image_size>
   <encryption>yes</encryption>
   <encryption_key>[128bit-key]</encryption_key>
   <encryption_key_file>[URL]</encryption_key_file>
   </format>
</query>

For additional information on encryption of iPhone streams: https://developer.apple.com/library/ios/#qa/qa1661/_index.html

Chapter markers got you down? Try this easy fix for removing chapter marker metadata from your source videos. This action, by default, is set to no; if you know your clip contains this metadata, switch </strip_chapters> to yes. 

Via API:

<format>
    <!-- Format fields -->
    <strip_chapters>[yes|no]</strip_chapters>
        ...
    </format>

Via UI:

You will find this feature at the bottom of the task list, underneath 'Denoiser'

Take control of where your processing occurs!  By housing Encoding.com's platfrom on Amazon's EC2, we have access to data centers on a global level. No matter where you decide to host your videos, there's a data center nearby to handle your encoding tasks and return your content back to you in the most efficient manner. Check out the complete list of datacenters that we support here:

US (Nothern Virginia): 'us-east-1'
US (Nothern California): 'us-west-1'
US (Oregon): 'us-west-2'  
EU (Ireland): 'eu-west-1'
Asia Pacific (Singapore): 'ap-southeast-1'
Asia Pacific (Tokyo): 'ap-northeast-1'
South America (Sao Paulo): 'sa-east-1'

Via API: 

    <format>
    <!-- Format fields -->
     <region>[us-east-1|us-west-1|us-west-2|eu-west-1|ap-southeast-1|ap-northeast-1|sa-east-1]</region>
      ...</format>

Have a ton of videos that just require lossless rotation? Did someone have too much fun with the iPhone and shoot everything portrait instead of landscape?

Try this on for size. Lossless rotation for use with .mov --> .mov files only.

<format>
  <output>mov</output>
  <destination>[Destination]</destination>
  <rotate>0</rotate>
  <set_rotate>90</set_rotate>
  <video_codec>copy</video_codec>
  <audio_codec>copy</audio_codec>
</format>

Want control over file names after they finish encoding from your watch folders? It's easy. Follow these simple steps:

- Add in what you would like to have displayed after your file name finished encoding.

Example:If your file name is video.ext, and you specify '_big' in the Name Postfix field, your resulting file name will be video_big.ext.

- If you wish to retain the task ID number, and also add more information, use the # sign to allow the task id to pas to your file name.

Example: If your file name is video.ext, and you specify '_big_#' in the Name Postfix field, your resulting file name will be video_big_1234.ext

The default setting for the watch folders will be to leave the watch folder settings as is, and continue augmenting the suffix of the file name with the task ID. 

Do you have a bunch of files that require encoding, but want to know more about the source media properties?

Use this workflow to achieve this:

Step 1: Send source media to the API via the AddMediaBenchmark action. Manage.encoding.com will accept this request and assign a Media ID for the video.

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

Step 2: Send a GetMediaInfo call to the API, with assigned MediaID, so source video characteristics will be shown, such as framesize, duration, and bitrate.

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

Step 3: Configure your CMS to select a setting based on returned media properites.

Step 4: Send  back a ProcessMedia call, and use GetStatus to monitor progress.

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

NOTE: If you need separate progress reports for each task, add <extended>yes</extended> to GetStatus

Step 5: When job completes, have your CMS parse the result notification.

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

- - - 

To reuse source files, which expire after 15 days, use <action>UpdateMedia</action> with an existing Media ID to replace all of the existing format fields. 

With Encoding.com, you can easily add a dissovle at the start and end of your encodes via our fade commands.

Click on this link for more information.

Within the format tag, you can now specify the duration and length of the fade that you would like to apply to your encodes. 

via XML:

<format>
   <fade_in>[FadeInStart]:[FadeInDuration]</fade_in>
   <fade_out>[FadeOutStart]:[FadeOutDuration]</fade_out>
</format>

Definitions:

FadeInStart: Start of fade_in effect in seconds

FadeInDuration: Duration of fade_in effect in seconds

FadeOutStart: Start of fade_out effect in seconds. If you specify this parameter equal to 0, fade out effect will be applied to the end of video/audio.

FadeOutDuration: Duration of fade_out effect in seconds.

Note: FadeIn/FadeOut effect applies both for audio and video streams.

You can easily correct audio sync issues by setting the audio_sync tag in your XML, as follows: 

<audio_sync>1</audio_sync>

This works by adjusting the output audio stream to match the source timestamps, in # of samples per second. Consider this a great for fixing sync when source is variable framerate, or has timescale problems.

The most common instance of this is webcam video recorded with Nellymoser audio codec from the free flash plugin.

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 'Add Media' 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 'Add Media' 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

Watch folders are a nifty way to manage all incoming content. In case you want to change the applied settings, here's a guide on how to do just that. You can easily change the destination URL, the notify location and even the watch folder source location.

In the watch folder main view, which lists all of your watched locations, click on the watch folder name you wish to edit. This will take you to the 'Watch Options' page.

Under 'Watch Options' you can reconfigure the location that Encoding.com is polling, change the frequency of the time that Encoding.com polls your directory for new content, and a host of other options. 

To change task settings, select 'Encoding Options.' Here you'll see a list of the applied tasks.

To delete a task, select it from the list below 'With Selected' and hit Delete.

To edit a task, select it from the list below 'With Selected' and reconfigure it on the right side of the screen, under 'Format.' Make sure to hit save after this point, or your changes will be lost. 

To add a new task, simply hit 'Add New' to add tasks to an existing watch folder.

Once you've completed any of these steps, make sure to hit 'Save.' Select 'Close' from the upper right hand corner of the grey box.

If you wish to reprocess the entire watch folder contents, select 'Reset' from the main watch folder view.

If you have current jobs in your encoding queue and wish to change the settings, follow the instructions below. In either case, you can change the destination URL, the notify location and even the source location. This is handy in case you uploaded the wrong source, but want to keep the correct applied tasks.

In progress jobs: This works well on larger jobs, as with smaller jobs, you'll have to work quickly to catch them and change their applied tasks.

Finished jobs: This workflow works well for large files that are already uploaded to the platform. You can just change the applied tasks (over and over again) if you want different versions of the source file.

In the queue, select the check box next to the MediaID you want to edit. From the top row of choices, select 'Edit'. 

In the task manager view you can now add or delete tasks. To edit a current task, select it from the list 'With Selected' below the large orange button that says 'Add Task.' 

Once you've completed this step, make sure to hit 'Save.' Select 'Close' from the upper right hand corner of the grey box.

Now head to the Encoding Queue and select 'Process' to start the job with the new applied tasks.

A great place to start when trying to improve your video quality is to change the field 'Two pass' from no to yes. This applies to folks that are using the Desktop Application or web UI, for watchfolders or single add media requests. If you're an API user, toggle the <two_pass> field from no to yes. This should beef up the quality. Encodes will take a bit longer, but you'll be impressed with the quality improvement.

Having wierd errors in your submissions to the platform of your video or image files? Check to see if you have a file extension on your source media. If not, give it the proper extension so that the platform can easily parse your source files and start the encoding process.