Feedback on ClipFlair Studio application Basic terminology  Viewed 69019 time(s), 3 post(s), 2/17/2013 4:25:29 PM - by rovira

The test player is something that the Microsoft Expression Encoder creates to try a smooth stream. It's the same player technology (Silverlight Media Framework) with another "skin". We're in the process of creating our gallery UI where videos will be played inside ClipFlair Studio even when one wants to preview them.

I've already updated "(play)" links in the existing gallery page to do so.

When one visits the folder where a smooth stream exists at http://gallery.clipflair.net/video/... they can see the test player but eventually this will be removed (since it also takes spaces on the server, adds a player copy for each smooth stream) and user will be redirected to the appropriate ClipFlair Studio URL automatically to view the video in it instead

As for links, the smooth stream URL ends in .ism/Manifest and this is the VIDEO DATA, the one you refer to as "test player" link is just a link to the folder where it exists which shows the video in a PLAYER (currently the test player but soon will show in ClipFlair Studio)

So when you pass on a URL to our Clip component's "Media URL" property to play a video you're supposed to pass the URL to the VIDEO DATA, not the URL to a web page that can preview that VIDEO DATA (which is provided extra as a convenience)

it's similar to downloading a file on the web, each file has a unique URL that identifies it, but it may also have a web page that previews it or shows information about it etc. If you give the file URL to a browser you download it, if you give the web page URL you see info about the file (and some download button etc.)