Essentially this is writing code to do [url removed, login to view] live streaming over HTTP progressive download.
Capture [url removed, login to view] LIVE content from ONE of the following (whichever you prefer) RTMP, RTSP, or HTTP Live Streaming (M2TS) and save it to a file.
If a user requests the video, start serving up data from the file at the most recent possible point in the file using plain old HTTP progressive download, including sending a proper moov atom.?
We have LIVE streaming [url removed, login to view] content which is available in any of the following transports (whichever you're most comfortable working with): RTMP, RTSP, or HTTP Live Streaming (i.e. iPhone or chunked M2TS / MPEG-2 TS).
What we need is for this content to be playable LIVE via a player that only supports [url removed, login to view] over progressive download (for example if you were to point it to an MP4 file which gets downloaded over HTTP).
What we are looking for is for someone to create code which runs on Linux that will do the following:
1. Be constantly pulling the live [url removed, login to view] feed and storing that data to somewhere.
2. When a request from an end user comes in, read that data at the appropriate position (i.e. start at the newest point in the file, respecting any [url removed, login to view] data boundaries of course) and serve up a progressive download to the end user.
3. When the request is served to the end user, it MUST start with an appropriate moov atom.
4. Be robust to failure - if the live stream is inaccessible, end users should just see black and hear no audio, and then when the live stream is accessible again, it should resume automatically.
We're looking for a quick turnaround because this may be demoed at an upcoming event. If we are to make that event, we need to get the project completed and then test it and make any fixes prior to then. If it's not possible to meet that deadline, we are still interested, but we wouldn't necessarily be willing to accept a "rush" priced bid.
Please include two timelines + bids - one with the hard due date being Dec 21, 2010, and the other being whenever you choose (though ideally not too far into January).
One condition of this project is that you not be currently working as an employee of any web firm.
1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Employer will receive exclusive and complete copyrights to all work purchased. (It's expected that open source or third party components may be used; however, no GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the employer on the site per the worker's Worker Legal Agreement).
2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
3) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Employer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Employer's environment.
b) For all others including desktop software or software the employer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project.
4) Must be ok with signing the attached NDA
If any of the following technologies are relevant, they are preferred as we may take this project over internally once completed and they are what we are most familiar with. If you want to propose other technologies, please do so in your bid. We might prefer choosing a less efficient technology and just buying a more powerful server in the interest of being able to maintain it ourselves if desired, but this is not necessarily the case.