Find your answers here.
The Rackspace Cloud Files platform does not offer the FTP method to send files to their service. Encoding.com added support for our customers to send encoded videos directly to their platform.To specify the source file or output file(s) to be put in a Rackspace Cloud Files folder, you can specify your source or destination URL Read more
There are a few steps that need to occur before videos can be uploaded directly to your blog from Encoding.com. First, ensure that you have downloaded and added the latest plugin to your blog's directory: http://wordpress.org/extend/plugins/encodingcom-wordpress-plugin/ Second, follow the directions on installation here: http://wordpress.org/extend/plugins/encodingcom-wordpress-plugin/installation/ – – – In the WordPress article creation: There is a Read more
The “Content-Type” of a video is an important and in most cases required MIME type for streaming video. Amazon S3 simply echos back whatever MIME type you send when you upload the file. You can set the content-type parameter of a video before sending it to Amazon by appending &content_type= to your S3 destination, for Read more
Check and see if the host is reachable. Can you reach another host? Check connection status and retry.
Please send your API requests to manage.encoding.com at 52.200.5.10 Notification posts are coming from 34.193.0.100 Port Assignments FTP on port 21 SFTP on port 22 HTTP on port 80 HTTPS on port 443 AWS Amazon has a very sophisticated system in place for managing IP ranges across their infrastructure. Everything you need to know about Read more
AWS authentication access is currently not implemented for thumb_destination. Alternatively you can create a separate task with output=thumbnail to use this feature: To quote our API documentation: Instead of using thumb_ parameters within <format>, you can specify separate encoding task with output = thumbnail: <format> <!– Format fields –> Read more
Amazon access permissions are set by the user who creates the object. By default, when Encoding.com sends a encoded file to a user's Amazon S3 bucket it sets the permissions of this file to authenticated-read. If you want your file to be public readable, add ?acl=public-read to your destination URL, like this: http://your.bucket.s3.amazonaws.com/folder/file.ext?acl=public-read This will Read more
When using encoding.com to generate video for hddn.com, video can be directly uploaded to the FTP service hddn provides. HDDN requires passive FTP mode, so the path will require the URL string to append ?passive=yes. For example: ftp://username:password@ftp.hddn.com/path/filename.ext?passive=yes This will solve any issues with upload errors from our service and get the files delivered to Read more
Encoding.com was developed to work seamlessly with the Amazon S3 storage service as either the source location of your video library or the destination location where we send videos after encoding is complete. A basic understanding of Amazons ACL permissions is recommended and we would highly recommend reading through our articles on integrating Amazon S3 Read more
You can use encoding.com's cloud storage location as temporary storage for your encoding output. To accomplish this you leave the “Destination” field empty using any integration method Web Interface. Desktop Application, or the API. To retrieve the direct http url of your you can login to the client interface, click Encoding Queue, expand the job Read more