General Information

Looking for access Vid.ly URLs and thumbnails via HTTPS? Look no further. All you need to do is make slight adjustments to your embed code and your URL structure for this to work.

For Amazon S3 access, please format as follows:

Poster:
https://d3fenhwk93s16g.cloudfront.net/[media_short_link]/poster.jpg

Thumbnails:
https://d3fenhwk93s16g.cloudfront.net/[media short link]/thumbnail_1.jpg - 33%
https://d3fenhwk93s16g.cloudfront.net/[media short link]/thumbnail_2.jpg - 66%
https://d3fenhwk93s16g.cloudfront.net/[media short link]/thumbnail_3.jpg - 90%

Note: S3 URLs are default for all HTTPS Vid.lys

For Rackspace:

Poster:
https://c197913.ssl.cf1.rackcdn.com/media short link/poster.jpg

Thumbnails:
https://c197913.ssl.cf1.rackcdn.com/media short link/thumbnail_1.jpg – 33%
https://c197913.ssl.cf1.rackcdn.com/media short link/thumbnail_2.jpg – 66%
https://c197913.ssl.cf1.rackcdn.com/media short link/thumbnail_3.jpg  - 90%

Note: For access to the Rackspace CDN, please specify <CDN>RS</CDN>

Here's an examples of HTTPS embed code from the AWS CDN for thumbnails:

<iframe frameborder="0" width="640" height="360" name="vidly-frame"
src="https://vid.ly/embeded.html?link=5u4h3e&autoplay=false">
<a target='_blank' href='https://vid.ly/5u4h3e'>
<img src='https://d3fenhwk93s16g.cloudfront.net/5u4h3e/poster.jpg' />
</a></iframe>

####

HTTPS will differentiate one sender and receiver from another. During transfer, SSL will take the data and encrypts it. This means that SSL uses an algorithm to hide the true meaning of the data. The hope is that this algorithm is so complex it is either impossible or prohibitively difficult to crack.  Encryption begins when the owner of the Web site purchases a trusted certificate authority.

We are actively working on integrating a third party advertising solution so that you can directly monetize your videos with pre-roll and post-roll advertising. Why re-invent the wheel? We are currently in discussion with the leading video ad platforms in the market and will have a solution implemented by end of year.

Very soon, you will have the ability to limit the 20+ output profiles that you want to support. For example, if you are only interested in supporting iOS devices, you can limit the number of output renditions that we create to only those that are relevant to the iOS platform.

In the meantime, there's Vid.ly lite. Check out the link for more information. 

We are currently building the ability to customize output profiles to best meet your specific requirements. This feature will be implemented very soon. With this feature, you will be able to customize any of the 20+ output renditions including bit rates, frame sizes and more.

Today? No. But, we are actively adding more networks and will eventually give you the ability to use your own existing vendor.

Wanna add a CDN to our Feature Request list for Vid.ly --> http://vidly.uservoice.com/forums/125877-general

Via Vid.ly, today you have two Content Delivery Network options: Akamai (via Rackspace) or CloudFront (via Amazon Web Services). We are actively working on adding other popular CDNs as well.

Yes! Not only do we provide a unique Vid.ly URL and javascript embed code for each of your source videos, we also provide a FLV URL to plug directly into your custom, commercial or open-source Flash player - JW Player, Flowplayer, OMS, etc... Here's an example: http://cf.cdn.vid.ly/5v2l9v/flv.flv

Of course you can. In fact, we think this is a great use of Vid.ly because so much consumption of these services happens on mobile phones... and many current video views are lost because the videos are not properly formatted for all devices before posting. You can simply share the Vid.ly URL in a Tweet and when the end user clicks on the link, we'll deliver the correct version of the video for that mobile device.

For each Vid.ly URL generated, we provide you with the javascript embed code for that unique Vid.ly. All you need to do is put this code in your HTML and you're done. We will detect what browser the end user is using to view your video and serve up the correct video for that platform. If they are using a newer browser that supports HTML5, we will detect which specific browser they are using and deliver the correct default video via our HTML5 video player. If they are using an older browser, we will deliver the video via our Flash player. Here's an example of the embed code:

<iframe frameborder="0" width="640" height="360" name="vidly-frame" src="http://s.vid.ly/embeded.html?link=5u4h3e&autoplay=false"><a target='_blank' href='http://vid.ly/5u4h3e'><img src='http://cf.cdn.vid.ly/5v2l9v/poster.jpg' /></a></iframe>

Vid.ly Pro is a pure usage model based on three monthly variables: # of Vid.ly URLs, storage (in GB) and delivery (in GB). You only pay for what you use. And, the more you use Vid.ly, the lower your per-unit pricing across each of the three variables. To see the pricing tiers, please click here.

Vid.ly was designed and built for video content publishers and mobile application developers who want to maximize their audience by enabling their videos to play for everyone on every platform... but, don't want to manage the complexities and costs of running their own infrastructure to accomplish this.

Over the past couple of years, we've heard a common theme from many of our Encoding.com customers: "Can you just take my source videos and make them work for everyone across all platforms?" Yes, we can. Video made possible with Vid.ly.

It's so simple that my mother has created a few Vid.lys. You tell us where your source video is located and we do all the heavy lifting from there. We will give you a unique Vid.ly URL and the embed code for each source video. You can share the Vid.ly URL across Facebook, Twitter and other social networks, or place the embed code into your web pages and mobile applications.

We convert your source video into 22 output renditions to cover more that 6,000 devices and browsers in market. We store the videos. When an end-user requests the video (clicks on the play button, clicks on the link, etc.), we detect what device she is using and then deliver the correct and optimized video for that device / browser. Brilliant!

Have you run out of bandwidth on a free Vid.ly that you've created and would like to create a free account for unlimited Vid.ly access. As the free vid.ly owner, you can visit vid.ly url / upgrade  (e.g vid.ly/a1b2c3/upgrade) and add billing information to convert your free vid.ly to a paid vid.ly and vid.ly account.  This is a great solution if you have created a free vid.ly or two on the web interface and would like upgrade it to a paid and metered account without using the API or encoding.com

Note: the limit on free Vidl.lys is 50GB per month.

Vid.ly is a universal video service delivered within a single short url and embed code.The vid.ly service seamlessly integrates a HTML5 video player, Flash video player, transcoding, storage, delivery, and device detection.  When you chose the vid.ly preset within the Encoding.com UI, Watch Folder, or API we automatically transcode your source video into 24 different video formats and create 5 thumbnails.  When processing is complete, we deliver a short url and embed code via email or a XML http post.  When the embed code is rendered within a HTML page we use browser or device detection to deliver the appropriate video format (H.264, Ogg, WEBM, or a Flash fallback)   If a mobile device visits the  short url directly we will use a powerful device detection to deliver the best quality viewing for experience for thousands of feature phones, popular tablets, and all major smart phones.

If you're a current Encoding.com customer, utilizing our API to create content, try adding this to the mix:

<format>
    <!-- Format fields -->
    <output>vidly</output>
    <vidly_destination>[aws|rs]</vidly_destination>
</format>

You're create a URL that can be accessed via any browser with the correct, optimized version served up whether its a mobile, ipad or browser. 

Have more questions about Vid.ly? Perhaps...what's it all mean? Look no further: http://m.vid.ly/user/

Have a billing question for the Vid.ly service? Please drop us a line at billing[at]encoding[dot]com.

Also, please feel free to give us a call!

You can reach the support line at 800.513.1740

Want your Vid.lys to play automatically in an embeded location? No problem. Just make this change to your embed code:

old code:

<iframe frameborder="0" width="640" height="360" name="vidly-frame" src="http://vid.ly/embeded.html?link=2o2i9a&autoplay=false">
<a target='_blank' href='http://vid.ly/2o2i9a'><img src='http://cf.cdn.vid.ly/2o2i9a/poster.jpg' /></a></iframe>

change the autoplay attribute to true:

<iframe frameborder="0" width="640" height="360" name="vidly-frame" src="http://vid.ly/embeded.html?link=2o2i9a&autoplay=true">
<a target='_blank' href='http://vid.ly/2o2i9a'><img src='http://cf.cdn.vid.ly/2o2i9a/poster.jpg' /></a></iframe>

Here it is in use:

Have you created a lot of free Vid.lys and they have appeared to stop working? Free vid.lys are limited to a certain amount of views and bandwidth. If this limit is exceeded, then the link will become inactive.

In order to avoid this, please sign up for our Pro Vid.ly account.

Having problems with a Vid.ly on a particular device or browser?

Browse to this link and in order to determine the full details on where / how you are accessing the link: http://vid.ly/myphone/

Good stuff!

In order to best serve our loyal customers, we have implemented a feature request voting system here: http://vidly.uservoice.com/forums/125877-feature-requests.  These feature requests, as they gain votes, will help us on the Encoding.com team prioritize fixes and additions to the system. We hope here at EHow can I check on a Feature Request for Vid.ly?ncoding.com, taking this very hands on approach will help us maintain and grow the largest encoding service out there.

With Vid.ly, we create 5 thumbnail images and provide direct http access to them for use within your HTML or application.  Here are the details:

2 X Poster Images:  Width = 640 pixels and the height is resized proportionally to your source video dimensions.  The poster image is used as the default image displayed within the player before the user clicks the play button. First poster image is taken at 10% mark of the duration of the source video and the second one is taken at the 00:00:01 time stamp of the video.  To obtain the image @ 00:00:01, please use http://cf.cdn.vid.ly/5u4h3e/link.jpg, where "5u4h3e" is your individual vid.ly url code. To access the poster image at the 10% mark, please use http://cf.cdn.vid.ly/5u4h3e/poster.jpg.

3 X Thumbnails Images:  All three have the width of 210 pixels and the height is resized proportionally to your source video dimensions.  The three thumbnails are taken at the 33%, 66%, and 90% duration marks of your source video and can be accessed directly by using http://cf.cdn.vid.ly/5u4h3e/thumbnail_1.jpg,  http://cf.cdn.vid.ly/5u4h3e/thumbnail_2.jpg, or http://cf.cdn.vid.ly/5u4h3e/thumbnail_3.jpg  Where "5u4h3e" is your individual vid.ly url code.

If you've selected Rackspace as the CDN for Vid.lys created via the API, the formatting for thumbnails will look a little different. Format your URLs to pull thumbnails as follows. Just make sure to swap out the shortlinks! This reformatting guide below will help alleviate any pains caused by Access Denied errors on attempts to pull thumbnails.

Poster Images:

http://c197913.r13.cf1.rackcdn.com/5c5l3c/poster.jpg

http://c197913.r13.cf1.rackcdn.com/5c5l3c/link.jpg

Thumbnail Images:

http://c197913.r13.cf1.rackcdn.com/5c5l3c/thumbnail_1.jpg

http://c197913.r13.cf1.rackcdn.com/5c5l3c/thumbnail_2.jpg

http://c197913.r13.cf1.rackcdn.com/5c5l3c/thumbnail_3.jpg

Are you used to sending XMLs to Encoding.com's API? Vid.ly XMLs are a bit different. Have a look! Note the usage of the source & sourcefile tags.

<?xml version="1.0"?>
<query>
  <action>AddMedia</action>
  <userid>[User_ID]</userid>
  <userkey>[User_Key]</userkey>
  <notify>[email_or_URL]</notify>
<Source>
<SourceFile>[SourceFile1]</SourceFile>
<CDN>[CDNType]</CDN>
</Source>
</query>

All API action requests are sent to the http://m.vid.ly/api/ page. Client must send HTTP(S) POST request with single parameter named "xml". The server response is a normal XML document.  Also, an HTML form at http://m.vid.ly/test/test_api.php may be used to send a request to API.