Encoding Errors

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

<-- Hide

If you have your Watch Folder frequency set to a short time interval (e.g 5 minutes) and you are uploading a video file to your watch folder that takes more than 5 minutes to upload it is possible for our system to start encoding the video file before it is uploaded and produce partial/duplicate encoding results. To resolve this simply set your time interval for a longer frequency (e.g 1 hour) while you are uploading your source video content. <-- Hide

If you're having issues with S3 storage forcing a download when viewing the URL, you can correct this issue very easily by specifying a custom content type. Simply append &content_type= to your S3 destination. For example: http://dbucketname.destination.s3.amazonaws.com/no_ext_file_with_cont_type?acl=public-read&content_type=video/mp4D <-- Hide

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

This error is returned when you have attempted to encode a video using our VP6 preset and both the height and width are not divisible by 16.  For more information see our article on recommended Flash output dimensions. <-- Hide

This error message is generated when we could not generate a thumbnail from your video. Make sure that the timestamp you have chosen for us take the thumbnail exists in the video file, for example a thumbnail request with a timestamp of 35s in a 30s video will return this error.

<-- Hide

Although we support over 95% of the most common video codec and container variations, sometimes a file will return this error. We are always working to improve our support of video codecs, and if you have file that returns this error please submit a ticket to: helpdesk@encoding.com with the MediaID and we will let you know if there is anything we can do.

Known reasons for this error:

* Variable Frame Rate files. Please change the source file to have standard frame rates. *

* Windows Media Screen Codec (MSS2). *

* Apple ProRes LT Files *

 

<-- Hide

The frame size you specified is too large. Please choose a smaller frame size and resubmit. <-- Hide

This maybe attributed to incorrect parameters such as bit_rate, rate, width or height . The specified parameters such as bitrate, audio sampling rate or audio channels number are not allowed for the specified codec. Also, often this error appears when specified bitrate is too low. <-- Hide

Some audio codecs (e.g. AAC or MPEG-Layer-3) have their own limitation for options values. When you leave these options blank in your API request, encoding.com will get them from the source file, and not always their set will be correct for particular codec. So, it's better to always set audio codec parameters explicitly.

<-- Hide

It means that unknown or unsupported video/audio codec is specified. See API docs.

<-- Hide

Left (Right, Top, Bottom) crop size must be a multiple of 2 <-- Hide

Incorrect frame size - Error specifying size, e.g. 0x240: Please specify a frame size. <-- Hide

You have tried to decode a video format that encoder does not understand. Try again with one of our supported formats.
http://www.encoding.com/wdocs/SourceFileFormats

<-- Hide

Could not write header for output file (incorrect codec parameters?): The specified codec are not supported for this format, or need special parameters to be specified. For example: 3GP format require libamr_nb audio codec for correct encoding. <-- Hide

This depends on the type of error that has occurred.  If the error reported is during the upload process or because you are attempting to upload an unsupported format, there is no charge.  Otherwise, you will only be charged for the source video encoding bandwidth and not for the output files that have resulted in error.

<-- Hide

One of the reason may be inconsistency of specified segment duration and framerate/keyframe pair. You should try to keep at least 3 keyframes per segment. E.g. if you specify segment duration 5 sec and keyframe 15 fps, the keyframe parameter should not be greater than 25, so we have at least one keyframe per every 25 frames, and there are about 3 keyframes per segment (it's duration is 15*5 = 75 frames).

<-- Hide