Random Errors

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.

There's a little bit of similarity in a few of the Restart actions in the API. Here's the breakdown:

+ RestartMedia:  This will completely restart the entire job, including all tasks.

+ RestartMediaErrors:  This action will retry specific tasks within the request that produced an error. For example, if you received a 404 error on a file and remedied the issue, this action will successfully rerun only that task. 

+ RestartMediaTask:  This action requires an additional parameter. You can specify to rerun a specific task within a MediaID. For more information on the difference between MediaIDs and TaskIDs, please go here.

You've read all the help articles, you've done your homework, and S3 is still giving you grief.  

Check this one simple thing, and it should help you with your final issues.

Does your source or destination URL look like this:

http://[your_accesskey_code]:[your_secretkey_code]@CLIVETHEGOAT.s3.amazonaws.com/path

Amazon AWS does not recognize capital letters of bucketnames (the part after the @). Change that puppy to this:

http://[your_accesskey_code]:[your_secretkey_code]@clivethegoat.s3.amazonaws.com/path

If all is still not well, drop us a line at helpdesk@encoding.com and we'll help you solve your issue with this.

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.

With TAR output is set to OFF, and should see .m3u8 pointers and .ts segment files populate your output directory. The trick is correctly formatting the output filepath. You have to make sure your output filepath has a filename WITHOUT a 3-character file extension. I had this same problem because I either defined only the output directory, or had an output filename with .m3u on it. In both cases that will force a TAR output even if you have set it to off. SAMPLES: To get your segments, a correct output filepath should look something like this: http://yourbucket.s3.amazonaws.com/iphonetest/outputfilename ftp://username:password@ftp.yourserver.net/iphonetest/outputfilename

The Desktop Application requires you to plug in a few details before you can start encoding video. If you are receiving this error, stop for a moment and verify a few items. You can pull all the required information from your login page @ encoding.com. Login and go to the 'My Account' section of the user interface.

1) In the File menu, select Preferences.
2) Ensure that the UserID is a numerical value as opposed to your username.
3) Cross reference the API key with the value from the 'My Account' section of your login page. Make sure this is correct.
4) Hit SAVE! You're done. Restart any and all jobs and see if the issue corrects itself.