Apart from the initial upload we account all traffic generated by streaming your video's to a viewer, but since we stream, we only account the part that is actually watched (+ a small buffer). When a viewer watches a part of stream twice, that part is accounted twice, because streams cannot be cached.

Finally we account for each video that is downloaded directly, or which is otherwise retrieved from our servers (e.g. via our API).

Thumbnails, playlists, players and the overall use of our system are all free.

• ± 4.5 hours/GB for our small (320px) videos.
• ± 3 hours/GB for our medium (480px) videos.
• ± 2 hours/GB for our large (720px) videos.

Please note these are averages and are no guarantee for your videos, it can be a bit more or less.

For our custom subscription plans we also offer custom payments (e.g. by wire transfer). Pleae contact us to discuss your wishes and options.

The link can be used for searches, rss feeds and syndication, so others can link back to your videos.

Step one

Log into our video management system via https://manage.bitsontherun.com/login

Step two

Start up our upload application. You will notice that the uploader tells you that it does not have acces to your account. You need to grant the application access. Click "OK" to do so.

Step three

Now let's actually login, so click "login".

Step four

After you click login the application opens a new window or tab in your default browser. On this webpage you can grant access to the uploader by clicking "Yes". If by chance you are not logged in, you get the chance to login first.

Step five

Go back to the uploader application and click continue.

Step six

You can now start with uploading videos to bits on the run.

Good luck!

However for all javascript interaction you need to have the player id. Retrieving the ID of a player can be done with javascript as well, because it is possible to retrieve a player by its parents ID or in some similar way. Each of our players is placed inside a div that has the class "botrplayer" and an id with a random string. The id of the player is the same as the one for the div except we append swf to the id. This way we can retrieve the video's id like this:

function getPlayerId(parentId) {
    divs = document.getElementById(parentId).getElementsByTagName('div');
        for (var i = 0; i < divs.length; i++) {
            if (divs[i].className == 'botrplayer') {
                return divs[i].id + 'swf';
            }
        }
    return false;
}

Once you have the id, you can do everything that is mentioned in the tutorial.

Smaller videos (less than 300 pixels wide) render faster. Videos that are over 700 pixels wide render noticable slower.

We are constantly tweaking the predictions (about 5 minutes...) the CMS gives when building conversions, but given the huge differences between video formats this is a trial-and-error task.

There are many APIs out there and they all work differently. Sometimes this is natural because of the service offered, but every new API scheme adds to the developer workload.

We played around with the various APIs currently out there and especially liked the one from Flickr. It has a great permission system, which allows authorization on different levels for individual applications.

• Syndication (YouTube upload, iTunes publishing and sharing of videos to other users)
• Skinning for the videoplayer (dramatically change the look by providing your own SWF graphic).
• Integration of preroll, midroll and postroll advertisements.
• Adding chapters/cue points to videos.

We will also introduce our affiliate plan, which'll allow design, production and webhosting companies to brand and resell the Bits on the Run system for their clients (please contact if you're interested).

Long-term, we might focus on an installable version of the complete system, including hooks to services such as FMS, Wowza and Windows Media Server. This'll allow clients to install and deploy Bits on the Run within their own datacenter. At present, we still focus on optimizing the hosted service though!

We are currently scaling up our hardware to a peak bandwidth capacity of 10gbps (about 10.000 concurrent streams). If you want to learn more about our bandwidth capabilities and guarantees, feel free to contact us.