Flowplayer + Lighttpd = Pseudostreaming
 

I finally configured a local server to serve my streaming FLV files. The surfer can seek the timeline at any time while watching the FLV movie.

This is extremely useful if you plan to have a tube site.

Now, I just need my sys admin to set-up lighttpd on a separate server so that I can serve FLV movies.


http://flowplayer.org/plugins/stream...streaming.html

also works with a apache module: http://h264.code-shop.com/trac

no extra server needed

I thought seeking the timeline without wait time was only capable using mp4 instead of
flv.

Are you sure of this???

Edit: Just checked it out and yeah, works with FLVs :thumbsup

i'd like to know whats the benefit of using flv when it's actually nothing else than mp4 with extra features that no one uses anyways.

Yes on FLVs but be sure to process the clip through a metadata injector (flvtool2, yamdi, etc.) that inserts the keyframe and byte offset objects. Encoders like FFmpeg do not automatically add metadata to this extent.

ffmpeg started doing this over a year ago on flvs....

I use FLV MetaData Injector GUI 1.05 for Windows.
Work good if you are cutting your own videos.

http://www.buraks.com/flvmdi/

I went with LIGHTTPD because I wanted to keep my server load down. I am actually just getting a web server for videos.

The most benefit was that flv was the official Flash Video format.

So since the video player is made in Flash, flvs were the option.

Other video formats can't be played in a flash player except mp4.

sorry but only an idiot would use apache to stream vids.

everyone uses wowza / flashmedia player / red5 / light http

apache sucks ass for content delivery its only good for scripts and low traffic sites.

My sys admin is going to run both on one server. Apache and Lighttpd working together :)

That's news to me, and I've been testing the latest builds.

Is there a switch that does this? Frankly, I'm surprised FFmpeg bothers with the extended metadata as their support for FLV has never been it's strong suit, despite every tube site using it.

The only "MP4" Flash supports is H.264 in an MP4 container. Some people use "MP4" to mean MPEG-4, and Flash doesn't support that.

FLV is quite different from MPEG-4 and H.264. You use FLV when you want compatibility with versions of Flash Player prior to Version 9 Update 3 (also referred to as v9 r115). Anything earlier will not play H.264. Adobe does not volunteer penetration percentages for updates within versions, but in my experience, it's something like 10% of the general population that has a version prior to v9r115.

Like TheSenator says, Lighttpd is doing the video serving. Apache is used for anything else on the page.

The following page demonstrates Flowplayer fetching pseudo content from a CDN, plus fallback if H.264 is not supported by the user's version of Flash.

http://flowplayer.org/demos/plugins/...streaming.html

For anyone else wanting to do this, do keep in mind that pseudostreaming is effectively just like progressive download, that is, once the download begins at X point, it proceeds until either the video is completely downloaded, or the surfer goes to another point in the timeline, or he switches to a different page. It's not like true streaming, where the server will stream only so much at a time, then stop.

we have at xxxhostit.com nginx streaming flv with flowplayer in members area via joomla and apache for scripts for quite sometime now, i do love the setup (i do love lighttpd as well tho ) :)

hello...

do you guys know the best way to serve picture content ?

light http, nginx...or something else ??

then i am probably an idiot, remind me next time when i buy a link from you

although i doubt there will be a next time after my last experience