Hi All,
I'd be very grateful for some insight on how Microsoft On Demand Smooth Streaming works.
The smooth streaming on demand file family, when generated by your typical file encoder would usually include the following:
1) ISMV (Video file in container)
2) ISM (Server Manifest)
3) ISMC (Client Manifest)
It is my understanding that the client manifest be stored relative to the server manifest, but I further understand that I ought to be able to specify fully qualified URIs for my ISMV files. For some strange reason, the IIS 7.5 + Media Services 4.1 combo that I have running on an Amazon EC2 Windows Server 2008 R2 instance does not seem to like it when I address my ISMVs absolutely (500 Error, Akamai Error 3222 on their test player). This is even the case when I the absolute URL matches the physical location of the relative URL-yes, relative URLs work perfectly. The usual stuff( MIME, handler mappings, etc.) have been taken care off.
My gut feeling is that Microsoft have somehow closed off absolute URL referencing (both on domain and off domain). Has anyone managed to implement this out-of-the-box with IIS and Media Services, without workable 3rd party tools like Unified Streaming Platform's stuff?
I'd appreciate all feedback that anyone can spare, thanks very much!