There are 4 issues we are discussing here (streaming server,
web server, browser and player). I'll try to give you somr
advice to solve all of them:
You need to use the protocol in the URL for the stream that
matches the protocols supported by the server that hosts the
ASF file (either WMA or WMV). If the file resides on a
standard web server, you must use HTTP; if the file resides
on a streaming server, you need to use MMS (this is true for
WindowsMediaServices, while non-Microsoft streaming servers
may use other protocols).
This URL must be used both in WindowsMediaPlayer and the ASX
metafile (either WAX or WVX).
You can use the URL in InternetExplorer or any other browser
(e.g. in a direct link from the web page) only if it is HTTP
and the file resides on a standard web server (the streaming
server's HTTP protocol, if enabled, does not make it a
standard web server), otherwise you need to link to the ASX
that references the MMS URL.
If you use the ASX, it must reside on a standard web server
and it must be linked using a HTTP URL.
The exact behavior when you link an ASX depends on the
browser and the web server configuration.
The web server should be configured to set the correct
Content-Type header (for example, video/x-ms-asf) when
serving the ASX. By default, InternetInformationServers come
configured this way and newer versions of Apache are
supposed to be also, but older versions will not set the
correct Content-Type, so that the browser will handle the
ASX as text/plain or application/octect-stream.
The browser on its end must be configured to download this
Content-Type as safe and execute it with a player that
supports WindowsMedia. By default, IE comes configured in
such a way.
Post by a***@discussions.microsoft.comAs documented in MSDN articles, my IE browser does not
launch stream sessions using HHTP, it only begins
downloads. Only MMS: works for me.
The Stream Hoster seems to have clarified that the WAX/ASX
files on used in my HTML files on the CLIENT side and
should reside in client side web files. Ok, understanding
that and creating test, the ref href name.WAX line onlly
result in a new browser window opening and some title text
written on screen. Hoster indicates this is sign that my
APACHE webserver is interpreting the WAX files as text,
not WM files. I have added the WM MIME types where I can
in the Control panel but same result occurs.
Jim
-----Original Message-----
The URL that works uses the MMS protocol, the URL in the
ASX playlist uses the HTTP protocol. MMS and HTTP are
not the same and they are handled differently. The HTTP
fall-back of MMS is not a standard HTTP. Your test,
try using the same protocol, first use HTTP both in WMP
and in the ASX and then use MMS both in WMP and in the
ASX.
Post by ***@wirelesstechradio.comThe hoster I am trialing for On-Demand streaming
services suggests WAX files should reside on the client
side and WSX files on the server side.
I have been unable to get basic ASX or WAX metafiles as
described in the KB article to work from his server. I
get a "file not found" error message after the media
player launch and the metafile name appears inside the
media player.
mms://64.202.98.36/NNKOL/w0218043.wma works
<ASX VERSION="3.0">
<ENTRY>
<REF HREF="http://64.202.98.36/NNKOL/w0218043.wma"
/> </ENTRY>
</ASX>
DOES NOT WORK.
I've been loading http://64.202.98.36/NNKOL/wtr.wax
into my browser to test it.
It does not work with the error message returned above.
I am trying to get a playlist functionality to link
encoded files into a continuous or end-end stream.
All thoughts and solutions appreciated.
THanks, JIM SUTTON
www.wirelesstechradio.com
--
/**
* Alessandro Angeli
*
* MVP::DigitalMedia
*
* a dot angeli at biosys dot net
*/
.
--
/**
* Alessandro Angeli
*
* MVP::DigitalMedia
*
* a dot angeli at biosys dot net
*/