Error Messages

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'

If you wish to stop the processing of any medaID via API, send the action 'StopMedia.' 

Example: 

<?xml version="1.0"?>
<query>
<action>StopMedia</action>
<userid>[UserID]</userid>
<userkey>2a595f16aefdfbd1e3d7bf9952229bfa</userkey> 
<mediaid>[MediaID]</mediaid>
</query>

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.

Thinking of using FTPS as your source locations? No problemo.

All you need to do is specify the port in which we access your file at. Connections via FTPS will use port 22 by default. If you'd like to specify a different port, add it to then end of your URL.

Example:

FTPS://www.xyz.com:[port]/files/input.mov

Thinking of using HTTPS as your source locations? No problemo.

All you need to do is specify the port in which we access your file at. Connections via HTTPS will use port 443 by default. If you'd like to specify a different port, add it to then end of your URL.

Example:

HTTPS://www.xyz.com:[port]/files/input.mov

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.

If you having issues with posting your XML to http://manage.encoding.com from your scripted workflow, please make sure that you have added the following:

Content-Type: application/x-www-form-urlencoded

This helps to avoid errors such as:

<?xml version="1.0"?>
<response>
<errors>
<error>Wrong XML!String could not be parsed as XML</error>
</errors>
</response>

Unforuntely at this time, the notify field only allows one URL or email address. This can be either an HTTP(S) URL for the script with which the result will be posted, or a mailto: link with email address for which the result info will be sent. Note that this field may be specified for AddMedia and AddMediaBenchmark actions.

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.

This error is returned when our system is not able to send the video to the FTP/SFTP destination you specified.  Please verify the username, password, permissions, and complete directory path in a FTP client prior to adding it to our system.

For VBScript output to work, you may need to percent-encode the destination path twice. Like this.

Regular FTP path:
ftp://username@yourcompany.com:password@server.com/file.m3u8?passive=yes

Single URL (%) encoded - used for some standard FTP configurations
ftp://username%40yourcompany.com:password@server.com/file.m3u8?passive=yes

Double URL (%) encoded - used for VBScript FTP
ftp%3A%2F%2Fusername%2540yourcompany%3Apassword%40server.com%2Ffile.m3u8%3Fpassive%3Dyes

<-- Hide

The error message ECOM00229 translates to "S3 upload error: We encountered an internal error. Please try again."

The error message ECOM00228 translates to "S3 upload error: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed."

The error message ECOM00230 translates to "Creating the dir/file failed: No such file or directory."

The error message ECOM00202 translates to "Error putting thumbnail"

This error is encountered when our platform is unable to deliver the thumbnail to the specified destination. Please verify the path, syntax and permissions and retry your request.

The error message ECOM00203 translates to "S3 Download error"

When you submit jobs to us via an Amazon S3 location, it's imperative that we can read it. Please refer to the Knowledge Base article on setting permissions if your source file is to be encoded properly. http://help.encoding.com/idx.php/9/025/Amazon-S3-Integration/article/How-can-I-use-a-Amazon-S3-file-as-a-source.html

The error message ECOM00227 translates to "The requested URL returned error: 400"
The web server returned an error processing your request: the request was not understood.

The error message ECOM00226 translates to "The requested URL returned error: 503"

The web server returned an error processing your request: "Service Unavailable." 

The error message ECOM00225 translates to "The requested URL returned error: 404"

The web server returned an error processing your request: there is no page with the specified URL.

The error message ECOM00201 translates to "Error while opening file"

Our encoding platform is experiencing issues decoding your source file. It may be the case that your source file format uses some features that our decoder doesn't currently support. Please scroll to the bottom of our home page and plug in your source and output formats to see if we support your request.

The error message ECOM00138 translates to "Audio downmixing failed"

The error message ECOM00137 translates to "Can not resample 4 channels @ 44100 Hz to 2 channels @ 44000 Hz"

The error message ECOM00223 translates to "Connection time-out"

Check to see if the location of your files either on the source side or destination is currently online. Try reaching the locations manually and check the syntax of the locations.

The error message ECOM00136 translates to "Bufsize is required"

The error message ECOM00135 translates to "syntax error near unexpected token"

Encoder error: OverallBitRate:163322\nsh: -c: line 0: syntax error near unexpected token `('\nsh: -c: line 0: `/usr/local/bin/mediainfo /mnt/vhosts/default/code/tmp/afa2b2b124ecb76ad4df56a4878d036f/Alic

The error message ECOM00134 translates to "width or height not divisible by 16 (480x360), compression will suffer"

Your source video appears to not want to play nicely with our encoding platform. Generally, it's best to see what the dimensions are of the video and see if they are divisible by 16.

The error message ECOM00133 translates to "Can't get segment duration"

Encoder error: OverallBitRate:588175\n\n\nDuration:380612\n\n\nCan't get segment duration\n

The error message ECOM00119 translates to "libfaac doesn't support this output format." 

The most often reason that you would run across this video is that the left audio parameter is blank. At this point, the encoder tried to take them from the source, but the target audio codec does not support such parameters set, e.g. 8000 Hz mono.

The error message ECOM00128 translates to "Encoder error: sh: /bin/tar: Argument list too long"

This is known bug. It will be fixed in nearest release.

The error message ECOM00124 translates to "Segmentation error"

This error can be traced to specifying the incorrect set of parameters: segment duration, framerates and keyframes. Please refer to http://help.encoding.com/idx.php/0/142/article/why-do-i-get-segmentation-error.html for more details

The error message ECOM00123 translates to "Neither video nor audio stream was found."

Verify that the clip that you sent does contain video and audio. Also please verify that the clip that you sent transferred in its entirety. If you're sure your media contains the right components, please contact technical support.

The error message ECOM00122 translates to "Unknown format."

This error could denote a few different issues:

1) Your source file may be corrupted. Please verify that your source has uploaded in its entirety.

2) Double check that your file is supported by encoding.com. It may be that it is not supported format. Check it against our source listing: http://www.encoding.com/wdocs/SourceFileFormats

3) The path to your source may not be valid. Be sure the source URL you specified is correct in path and syntax and that there are external references that could not be interpreted by our download engine.

The error message ECOM00121 translates to "Unsupported codec for input video stream."

Your source media contains a video stream that our system cannot decode. A good way of isolating this issue is to resubmit a different version of your source clip. Please contact technical support for more details.

The error message ECOM00120 translates to "Unsupported codec for input audio stream." 

Your source media contains an audio stream that our platform could not decode. A good way of isolating this issue is to resubmit a different version of your source clip. Please contact technical support for more details.

The error message ECOM00118 translates to "Video codec is not supported." 

Our encoding engine is unable to decode the source video that you submitted. Please refer to our supported format list and submit a different version of your clip.

To provide a foundation for a strong error messaging system, we have segmented error codes into four main categories.  This makes the error messages easier to classify as well as allow our API customers to take specific actions programatically in their software based on a specific error message that was returned.  Here is the breakdown of categories:

The error message ECOM00117 translates to "Unknown encoder ." 

No resulting file. Our encoder was not able to produce any resulting file from the submitted clip. This is internal error, please inform us if it persists.

The error message ECOM00114 translates to "Requested video bitrate is too low." 

The error message ECOM00112 translates to "Encoding was not completed: .*: could not find codec parameters."

Your source file did not contain a video stream. Please check your source file for a video stream if the request that you made was for an output requiring audio and video.

The error message ECOM00001 translates to "The AWS Access Key Id you provided does not exist." 

Please verify you specified the correct AWS key and it is properly encoded in the URL. If you still experience this problem, please contact customer support.

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 most common error is specifying incorrect SFTP URLs for files located in your home directory. You must specify full directory path in your URL: sftp://user:password@your-host.com/home/user/video/file.ext Another common issue is missing files! Check the file is there, and the path for encoding.com is correct. If you continue to experience issues, don't hesitate to email helpdesk@encoding.com.

If a user is experiencing an issue using the iphone_streaming task/preset (see snippet of the full error read out below), this error is easily resolved by setting the audio_sample_rate. Apple recommends the audio_sample_rate is set to 22050, however, it could potentially be set to: 8000, 11025, 16000, 22050, 32000, 44100, 48000.


Encoder error: FFmpeg version SVN-r21449, Copyright (c) 2000-2010 Fabrice Bellard, et al.   built on Feb  3 2010 06:48:05 with gcc 4.4.0 20090514 (Red Hat 4.4.0-6)   configuration: --prefix=/usr/local/ffmpeg/21449 --enable-shared --enable-gpl --enable-version3 --enable-nonfree --disable-ffserver --enable-postproc --enable-pthreads --enable-memalign-hack --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfaac --enable-libfaad --enable-libgsm --enable-libmp3lame --enable-libvorbis --enable-libx264 --enable-libxvid   libavutil     50. 7. 0 / 50. 7. 0   libavcodec    52.48. 0 / 52.48. 0   libavformat   52.47. 0 / 52.47. 0   libavdevice   52. 2. 0 / 52. 2. 0   libswscale     0. 9. 0 /  0. 9. 0   libpostproc   51. 2. 0 / 51. 2. 0 [mpeg @ 0x806b3e0]MAX_READ_SIZE:5000000 reached  Seems stream 0 codec frame rate differs from container frame rate: 50.00 (50/1) -> 25.00 (25/1) Input #0, mpeg, from '/mnt/vhosts/default/code/tmp/source_1506155':   Duration: 00:03:33.19, start: 0.164600, bitrate: 15775 kb/s     Stream #0.0[0x1e0]: Video: mpeg2video, yuv420p, 720x480 [PAR 32:27 DAR 16:9], 15000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc     Stream #0.1[0x1c0]: Audio: mp2, 48000 Hz, 2 channels, s16, 384 kb/s [mp3 @ 0x8074560]sample rate not set Output #0, mp3, to '/mnt/vhosts/default/code/tmp/converted_6272009.mp3':     Stream #0.0: Audio: libmp3lame, 2 channels, s16, 64 kb/s Stream mapping:   Stream #0.1 -> #0.0 Could not write header for output file #0 (incorrect codec parameters ?) Encoder error: FFmpeg version SVN-.... ... <-- Hide

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.

If you've received this error, then the wrong UserID is matched with the wrong UserKey. Please log into your user account to verify that you are using the correct key.

If you've received the 'Wrong Media ID' error, then the media with such ID was not found. Suggested API Actions: UpdateMedia, GetStatus

If you've received the 'Source file is not indicated' error message then the SourceFile parameter is empty. Suggestion API Actions: AddMedia, UpdateMedia