As an example, avi encodes mp4. Just to point out that codecs and the ways 
video contents are encoded are always two distinct things.

If you can use a javascript to test the end user installed OS, you will get way 
to serve the adapted video format for each different target. Not a painless 
configuration to set up but it will work as expected against any client-side 
config.

If the medias have mainly to be online streamed, Darwin Streaming Server (free 
version of Quicktime Streaming Server) will always provide best results, 
fluidity and multi-platform availability (RTSP)  than Apache (HTTP). I used it 
to serve live conferences and VOD contents for the Sorbonne University 
(2005/2008) via the Renater 3 french universities network with 100% of 
reachability on Mac and Windows clients (both web pages and Rev standalones 
clients). The Darwin Streaming Server runs as well under MacOS X than under 
Linux. Lots easiest to configure than Red5 Media Server witch can, for its own, 
embed the same codecs as DSS with the ability to serves them as flash contents.

We always need to get in mind that video streaming is a very big bandwidth 
consumer + lots of RAM + fast hard drives needed on the server side. In some 
cases, YouTube hosting can really become the best maxi-min way to go.

Le 18 janv. 2013 à 03:38, J. Landman Gay a écrit :

> Thanks for all the responses. The audio/video files will be prepared by my 
> client and served over the internet to customers. We have control over the 
> format, the names, whatever is needed.
> 
> The catch is that the people who will be viewing the media can be on any 
> computer, often one they don't own (i.e., student labs, coffeeshops, their 
> neighbors, etc.) and we can't require any software installation. The app 
> itself will almost always be on a thumb drive.
> 
> No software installs means the media can't require QT, any special codecs, 
> etc. Whatever is the lowest common denominator is what we have to use. For 
> Macs I can depend on QT but for Windows users I can't.
> 
> If the decompressor or codec can be shipped with the app then that may be 
> something we could do. But I always thought codecs were installed into the 
> OS, and we can't do that.
> 
> I'm pretty sure my client, who is an audiophile, wouldn't be happy with 
> MPEG-1. So I'm open to suggestions.
> 
> -- 
> Jacqueline Landman Gay         |     jac...@hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

--
Pierre Sahores
mobile : 06 03 95 77 70
www.sahores-conseil.com


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to