Testing Bits on the Run for important project and it isn;t working

Delivery is now working, but question remains....

While I would like to use your service, I cannot pay for this service if it is not reliable for my requirements.

Please can someone advise.

How soon after uploading did this happen? I suspect that maybe seeding took longer than expected. In any case this is very uncommon.

On the other hand server not found sounds like a connection troubles, but I haven't had any other report from the UK (where you appear to be located), so in that case it sounds like there must have been an issue on your ISP level or lower, or I would have been inundated under reports that things are broken.

Hi, thanks for the swift response - that is appreciated.

It happended as soon as I tried to play the video directly after transcoding.

Would you suggest if we use your service that we allow time after transcoding for things to settle before driving our traffic to the video files?

My experience is that generally it works almost instantly, and given that you got a server not found rather than a file not found, chances are there was a routing bug or DNS issue at your ISP level rather than that the seeding was slow. It never hurts to test playback of the video etc before pushing things live though.

Absolutely! Unfortunately at the moment we don't know how long we have between receiving the required video files and the traffic starts to come in. We will try and maximise this period of time as much as possible, but its not entirely in our control.

My client has a YouTube partner account. I like JWPlayer, I like your transcoding tools, but can you tell me what makes your solution stand out from using an alternative such as YouTube who don't seem to charge me for bandwidth usage?

In short: control and customization.

Customization:

• You can pick (and even create) your own skins.
• The player can be extended with (almost) all skins that can be found in the JW player plugin library
• If you're a developer: Bits on the Run has a very extensive API, everything that is done in our own dashboard is done via our API, so if you wish to allow users to upload their own videos or something like that, that is very well possible. Similarly our player has a very rich API too which allows you to build interaction with the player

Control

• YouTube decides whenever a video is "monetizable". When YouTube considers a video monetizable it will throw ads before or on top of it that you cannot control.
• YouTube will show a youtube logo over the video that makes it very clear who is hosting the video and if people click the YouTube logo they will move away from your site to the YouTube site.
• Your video will always land up on youtube too, even if you don't want that.

Sorry, just went to test my embed and got the same server could not be found message. Do you think this is a DNS issue?

I just realized something else: are you behind a corporate firewall or some sort of proxy by any chance? That also causes this sort of issue. We are going to roll out an update in October that is a bit more adept at punching through firewalls, but I have just switched your delivery type to HTTP (which is also used by YouTube). Can you see if that makes any difference?

Once we have rolled out the player update you might want me to switch delivery back to RTMP, as RTMP has a smoother bitrate switching experience and helps you save bandwidth.

Hi Thanks for that!

Yes we are behind a firewall in our serviced offices. I went to another floor that runs on a different network and tested and it worked fine (although it could be the http switch over).

I have reported the issue with the building manager and IT support company that looks after the infrastruture to see if they can help.

I appreciate your time and will continue to test on your systems for a few more days. I like your paid support option too and I will probably set up a pro account early next week.

Once again thanks for your time and assistance.

If your IT folks prefer that the people in the office do not watch video unless it is officially sanctioned, they will probably want to keep things as they are, especially since we will improve the tunneling fallback in the near future and this will probably fix the issue that you saw.