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
More -->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
<-- HideSave some time with your encodes with this simple step, if you are sourcing from S3, try this URL formatting:
http://[AWS_KEY:AWS_SECRET@][bucket].s3.amazonaws.com/[filename]?nocopy
if 'nocopy' is specified at the end of your URL, the source file will be downloaded directly from your bucket, thus saving time. Please use this only if your buckets are located in the US. If ?nocopy
More -->Save some time with your encodes with this simple step, if you are sourcing from S3, try this URL formatting:
http://[AWS_KEY:AWS_SECRET@][bucket].s3.amazonaws.com/[filename]?nocopy
if 'nocopy' is specified at the end of your URL, the source file will be downloaded directly from your bucket, thus saving time. Please use this only if your buckets are located in the US. If ?nocopy is not specified at the end of your URL, the source will be copied to Encoding.com bucket first. This workflow saves you traffic in the case of non-US buckets and more than one encoding task per source.
<-- HideEncoding.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
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
<-- HideYou've encoded your file and now would like to save a copy, right? In your original request, if you didn't specify a destination URL, S3 / Rackspace / FTP, Encoding.com will store your videos free of charge for 15 days on our servers. Please note, the limit for this storage is 100 GB and your files will be deleted after
More -->You've encoded your file and now would like to save a copy, right? In your original request, if you didn't specify a destination URL, S3 / Rackspace / FTP, Encoding.com will store your videos free of charge for 15 days on our servers. Please note, the limit for this storage is 100 GB and your files will be deleted after 15 days. You can easily download your encoded files by logging into http://www.encoding.com/login --> Selecting 'Encoding Queue' and browsing to the file you wish to download. Expand the task and right click on 'Download.' Your encoded file will now be saved locally.
<-- HideWant to only process certain files in your watchfolders? Use our masking controls in the watchfolder UI. Good stuff!
+ Select 'Watchfolder' --> 'Add New' in the UI
+ Under the 'File Name Control' field, add in the type of content you WANT to process. For example, if you want to process only .mp4 content, then the masking
More -->Want to only process certain files in your watchfolders? Use our masking controls in the watchfolder UI. Good stuff!
+ Select 'Watchfolder' --> 'Add New' in the UI
+ Under the 'File Name Control' field, add in the type of content you WANT to process. For example, if you want to process only .mp4 content, then the masking field would contain, '*.mp4.' Add in multiple files types if you like!
+ Please note this functionality is only for file types, and not file names.
<-- HideThis message is displayed when you have attempted to encode a media file into a video format and no video stream was found in the source file. For example if you are attempting to encoding a .mp3 file into a video format. The media would need to be run into an audio only format.
If you feel this error
This message is displayed when you have attempted to encode a media file into a video format and no video stream was found in the source file. For example if you are attempting to encoding a .mp3 file into a video format. The media would need to be run into an audio only format.
If you feel this error is incorrect, please email support at helpdesk@encoding.com.
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.
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.
<-- HideCurrently, Encoding.com's file size is non existent. With the current limitation of Amazon S3's single source files @ 5 TB, the possibilites are limitless. Here's a the only caveat:
+ Amazon S3 only allows files up to 5 GB to be loaded through their UI. Check out Amazon's link here for current info on their Multipart tool, which
More -->Currently, Encoding.com's file size is non existent. With the current limitation of Amazon S3's single source files @ 5 TB, the possibilites are limitless. Here's a the only caveat:
+ Amazon S3 only allows files up to 5 GB to be loaded through their UI. Check out Amazon's link here for current info on their Multipart tool, which allows much larger uloads. To enable this feature through Amazon, log into your console, select a bucket in which you want to upload the file to in the console. Select 'Upload' under 'Actions.' Select 'Enable Enhanced Uploader (Beta) in the UI. Make sure to verify that you have the correct version of Java running as noted in the UI. That's it, you're ready to use Amazon S3's interface to upload large files.
Want your size XXL files to encode quickly? Turn on turbo for lightening quick encodes of your content.
<-- Hide
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.
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.
<-- HideThe wikipedia article linked here provides an excellent resource to check against for purposes of this article here . When using encoding.com with your hosted (ftp, http, etc) source files, often times passwords, usernames, or even filenames will have what is known as a 'reserved character'. Most common for many users is the; @ characters, ! characters, or -
More -->The wikipedia article linked here provides an excellent resource to check against for purposes of this article here. When using encoding.com with your hosted (ftp, http, etc) source files, often times passwords, usernames, or even filenames will have what is known as a 'reserved character'. Most common for many users is the; @ characters, ! characters, or - characters. These characters need to be URL Escaped or Percent-encoded in order to pass through the system in your string. When sending a path to encoding.com, it may look something like this: ftp://user%40domain.tld:password@ftpserver.tld/path/file You replace the @ character with %40 in the username just like shown. That reserved character, once properly escaped, will let our system know how to hand off the proper credentials to the hosting service in question.
Common special characters and their percent encoded equivalent:
@ = %40
& = %26
+ = %2b
/ = %2f
<-- Hide We use both Amazon EC2 and Rackspace Cloud for our video processing.
Notification HTTP posts are coming from 67.192.242.205 or 67.192.242.206
API requests are sent to manage.encoding.com at 67.192.243.9
FTP on port 21
SFTP on port 22
HTTP on port 80
HTTPS on port
