I saw your post regarding your Vimeo infrastructure and it's intriguing. You said, "My solution was to build a stream server which uses header redirects to point users to the file."
How does this work? Do you know if there is sample code somewhere or a guide we could use to engineer our own solution? OR would you be willing to sell us the code?
Category5 wrote:We too use Vimeo Pro for our Roku feed. When you're a pro user, you can visit the "Video Files" tab and grab the direct links for all the hosted files.
We had been using S3 with Cloudfront, but that became cost prohibitive. I was shocked to find Vimeo Pro was so cheap and would work, and did some testing where it actually ran very, very fast. Doing a wget on one of our Vimeo-hosted files, I am still in awe at how cheap it is.
The one thing with Vimeo is that the filenames have a ? in the name. My solution was to build a stream server which uses header redirects to point users to the file. This works GREAT for Roku but also our RSS feeds. Another nice thing is that it allows us to track a great deal of information about each and every view -- see https://status.category5.tv/. An easier solution might be to simply use YOURLS or another link shortener (to hide the ? from Roku, which tends to break things in some cases).
See http://v.cat5.tv/a/2hpFuOQ7/v/e/i/1410/q/hd/CAT5TV-383-Memories-of-Me-HD.m4v <- if you grab it with wget you'll see what's "actually" happening behind the scenes... but the inevitable endpoint is... you guessed it... Vimeo.