 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows Media Server / May 2007Streaming audio is un-seekable
I am trying to play audio from a server running Windows Media Services on Windows Server 2003 through a MMS URL (mms://***). When I try to seek to an unbuffered position in Windows Media Player, it throws an error saying "Cannot connect to the sever". If I let the file play at its own pace, it plays fine and also if I try to seek to a location which is already buffered, playback happens normally. I am suspecting that there might be some setting or error in the server which prohibits seek or random access. Please someone help me in this regard. Do revert back if you need any further clarifications / inputs. >I am trying to play audio from a server running Windows Media Services on >Windows Server 2003 through a MMS URL (mms://***). [quoted text clipped - 3 lines] >at its own pace, it plays fine and also if I try to seek to a location which >is already buffered, playback happens normally. At that point, your video is completely cached in the player. If you view the Statistics -> Advanced, it will say CACHE as the Transport. To get random access of videos from WMS, your videos must be encoded with "Indexing". There's a checkbox in WME which is usually checked, and I think it's defaulted checked when you select streaming profiles. An alternative is to reprocess (not re-encode) using the WM file editor included with the WME package, and select "Save As and Index" from the menu, rather than Save As. HTH Cheers - Neil ------------------------------------------------ Digital Media MVP : 2004-2007 http://mvp.support.microsoft.com/mvpfaqs Neil: Thanks for your prompt reply. It was really helpful. As suggested below I tried looking at the TRANSPORT (Statistics->Advanced) while Audio Stream was playing unbuffered. In certain cases, I could see that the transport is RTSP, and in these cases the seek was happening fine. Whereas, on some other machines, the same file is being played through a HTTP transport. In these cases, the seek is not happeing fine. This behaviour is very understandable as HTTP is not a streaming protocol. Now I am wondering why the same mms link is played with different transport in different situations. Could someone please shed some light on this. Thanks, Prashant > >I am trying to play audio from a server running Windows Media Services on > >Windows Server 2003 through a MMS URL (mms://***). [quoted text clipped - 20 lines] > Digital Media MVP : 2004-2007 > http://mvp.support.microsoft.com/mvpfaqs Well, mms is a "pseudo protocol" not a real transport, and it's only used in WMP11 for "rollover", that is stream selection based on negotiation with the server about what the player can receive over the network So sometimes you'll see http and other rtsp, that depends on how the server's configured to stream (and if the http plugin is enabled, for example), as well as on how the player's Network settings are eg some of these players may be set to use a streaming proxy, or have http streaming disabled by group policy, if they're in a corporate network. The worry I have is the "seek not available over http" sounds rather like you've connected to a web server instead of the media server, though that can't happen when using an mms URL. HTH Cheers - Neil >Neil: Thanks for your prompt reply. It was really helpful. > [quoted text clipped - 37 lines] >> Digital Media MVP : 2004-2007 >> http://mvp.support.microsoft.com/mvpfaqs ------------------------------------------------ Digital Media MVP : 2004-2007 http://mvp.support.microsoft.com/mvpfaqs |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.