prev/next

Temporary Storage HTTP Destination

Save some time on your encodes!

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

 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.

<-- Hide
tools: email  |  print  |  share  |  click to rate (rated 10 times):
  • BlinkList
  • Del.icio.us
  • Digg
  • Facebook
  • Google Bookmarks
  • LinkedIn
  • MySpace
  • Newsvine
  • Reddit
  • Sphinn
  • Technorati
  • Twitter

iPhone streaming creating TAR file on output

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

 More -->

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

<-- Hide
tools: email  |  print  |  share  |  click to rate (rated 2 times):
  • BlinkList
  • Del.icio.us
  • Digg
  • Facebook
  • Google Bookmarks
  • LinkedIn
  • MySpace
  • Newsvine
  • Reddit
  • Sphinn
  • Technorati
  • Twitter

Using Encoding.com a a temporary storage for your encoded video

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 ID and click on the

 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 ID and click on the "Download" link. If you are using our notification feature the http url will be available in the field of the email or XML notification we send once the job is complete. Encoding.com will store your encoding ouptut temporarily for up to 15 days or 100GB, which ever comes first. If you reach your 100GB limit we will automatically delete the oldest files first.

Please note that this is not available for .m3u8 files, aka Apple iPhone / iPad Streaming HLS files.

<-- Hide
tools: email  |  print  |  share  |  click to rate (rated 2 times):
  • BlinkList
  • Del.icio.us
  • Digg
  • Facebook
  • Google Bookmarks
  • LinkedIn
  • MySpace
  • Newsvine
  • Reddit
  • Sphinn
  • Technorati
  • Twitter