Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows Media Server / January 2008

Tip: Looking for answers? Try searching our database.

Publishing Point / Playlist Question

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
batkins - 03 Jan 2008 13:17 GMT
We have a large number of Windows Media streams that we are broadcasting to
the web using Windows Media Server 9 (in Windows Server 2003 (SP2)).

I am trying to build a way to be able to stop/restart our streams without
interrupting the stream and leaving "dead air" on our streams.  The software
we are using to encode the streams needs to be restarted periodically.

What we think we want to do is to build a publishing point which contains
our remote publishing point followed by a playlist (consisting of around 7
songs) which we want to play if the publishing point stops playing for any
reason and continue to play those songs until the publishing point is
encoding again and begin playing when it comes up in the rotation.

It looks like I should be able to do that by creating a publishing point
which consists of our remote publishing point followed by a playlist which I
expect to play when the remote publishing point stops streaming.  I am trying
to do that by dumping several songs from each stream in a folder and adding
that directory after that remote publishing point.

When the remote publishing point stops, the playlist doesn't start until I
stop the Windows Media publishing point and start it again.  When it starts
back without the remote publishing point streaming, it will pickup and play
the songs from the playlist.

If I am listening to the publishing point using Media Player, the player
retries to buffer the stream until I stop the publishing point in Media
Server and start it again.  It will then start playing songs from the backup
playlist.
I am not making any changes to the properties of them media items.  Is there
something else I need to do to have the WM publishing point go directly from
our remote publishing point to the songs in the directory when the remote
publishing point stops, or am I using the wrong approach?

Thanks in advance for any assistance.
Signature

Bill Atkins

Neil Smith [MVP Digital Media] - 03 Jan 2008 20:28 GMT
Yeah, this should be pretty simple by setting up a playlist for the
publishing point which uses encoder failover. This page shows an
example of usage with failover to static video or image content :
http://www.microsoft.com/windows/windowsmedia/knowledgecenter/mediaadvice/0068.m
spx#EPG


As noted on the page below, there can be a delay - set that to Zero
using the WMReconnect URL modifier for the encoder URL :
http://msdn2.microsoft.com/en-us/library/ms753592.aspx

You can also detect and set times for failover using URL modifiers :
http://www.iliveu.com/wmserver_en/hosting/streaming/controllingencoderfailoverwi
thurlmodifiers.htm


Obviously, those apply only to pull rather than push encoding.

HTH
Cheers - Neil

>We have a large number of Windows Media streams that we are broadcasting to
>the web using Windows Media Server 9 (in Windows Server 2003 (SP2)).
[quoted text clipped - 30 lines]
>
>Thanks in advance for any assistance.
------------------------------------------------
Digital Media MVP : 2004-2008
http://mvp.support.microsoft.com/mvpfaqs
Bill Atkins - 08 Jan 2008 14:33 GMT
Thanks Neil:

Using the help you gave me in the links, I have setup several publishing
points on a couple of our servers.

I have tried several differnt ways of doing it.

We have 16 ASX streams on each broadcast server streaming 8 formats in 2 bit
rates.

Here is an example of a publishing point I am using now and will run the
stream and fail over to the songs if I stop the stream at it's source:

<?wsx version="1.0" encoding="utf-8"?>
<smil repeatCount="indefinite">
   <media
src="http://b5.radio.amsi:4150?WMNoDataTimeout=1000&amp;WMNoDataTimeout2=1000"/>
   <media src="C:\TheRadio.com\Playlists\IslandSongs\Ub40_-_Wild_Cat.mp3"/>
   <media
src="C:\TheRadio.com\Playlists\IslandSongs\Bob_Marley_-_I_Shot_The_Sheriff.mp3"/>
   <media
src="C:\TheRadio.com\Playlists\IslandSongs\Burning_Spear_-_Marcus_Senior.mp3"/>
   <media
src="C:\TheRadio.com\Playlists\IslandSongs\John_Brown's_Body_-_Land_Far_Away.mp3"/>
   <media
src="C:\TheRadio.com\Playlists\IslandSongs\Lee_Perry_-_Roast_Fish_And_Cornbread.mp3"/>
   <media
src="C:\TheRadio.com\Playlists\IslandSongs\Matisyahu_-_Ancient_Lullaby.mp3"/>
   <media
src="C:\TheRadio.com\Playlists\IslandSongs\Sublime_-_April_29,_1992_(Miami).mp3"/>
</smil>

I am having a problem that the publishing points will drop from the srtream
to the songs for no apparent reason.  The source streams are still
streaming.  I have another server in NLB with this server and the streams
remain connected to the other server when they drop here.

The Troubleshooting section shows Server Warning (0xc00d0029) with the
following details as an example:

The publishing point 'TheActiveRock1' is unable to stream from
'http://b5.radio.amsi:4670?WMNoDataTimeout=3000&WMNoDataTimeout2=3000',
referenced in 'file://C:\TheRadio.com\35\TheActiveRockChart1.wsx'.

I have tried different millisecond values for the WMNoDataTimeout
parameters, from 1000 to 4000 milliseconds, but it seems like it doesn't
really have an effect.

As an example, between 9:00 and 9:20 this morning, I had 5 different streams
with this error.

Thanks again for the help you have given me so far, and for any more help
you can give me.

Thanks

BA

> Yeah, this should be pretty simple by setting up a playlist for the
> publishing point which uses encoder failover. This page shows an
[quoted text clipped - 60 lines]
> Digital Media MVP : 2004-2008
> http://mvp.support.microsoft.com/mvpfaqs
Neil Smith [MVP Digital Media] - 08 Jan 2008 20:56 GMT
>Thanks Neil:
>Here is an example of a publishing point I am using now and will run the
[quoted text clipped - 21 lines]
>I am having a problem that the publishing points will drop from the srtream
>to the songs for no apparent reason.  

The no data timeout may be too short. WME can drop out and not
broadcast properly for a few secods at a time, if my experience
connecting 10 clients to it is any indicator.

>The publishing point 'TheActiveRock1' is unable to stream from
>'http://b5.radio.amsi:4670?WMNoDataTimeout=3000&WMNoDataTimeout2=3000',
>referenced in 'file://C:\TheRadio.com\35\TheActiveRockChart1.wsx'.

That's a different PP than the one quoted above, which uses
WMNoDataTimeout=1000&amp;WMNoDataTimeout2=1000

>I have tried different millisecond values for the WMNoDataTimeout
>parameters, from 1000 to 4000 milliseconds, but it seems like it doesn't
>really have an effect.
>
>As an example, between 9:00 and 9:20 this morning, I had 5 different streams
>with this error.

What happens if you increase the buffering time value in the encoder
profile for that stream ?

>Thanks again for the help you have given me so far, and for any more help
>you can give me.
[quoted text clipped - 67 lines]
>> Digital Media MVP : 2004-2008
>> http://mvp.support.microsoft.com/mvpfaqs 

------------------------------------------------
Digital Media MVP : 2004-2008
http://mvp.support.microsoft.com/mvpfaqs
batkins - 09 Jan 2008 02:18 GMT
Yeah, I stareted playing around with the timeouts today.

I noticed that some of them (all coming from the same broadcast server) need
a longer timeout than others.

I have changed them all to at least 3000 milliseconds.  One of them is up to
8000 milliseconds.  I just set it up from 7000 because it timed out this
evening.

I started setting the time out to 3000 earlier today and have been
monitoring them all day.  3000-4000 is fine for most, but some of them need
more.

There are 16 publishing points on my test bed broadcast machine.

I am going to start setting up other ones tomorrow, since it looks like it
does help stabilize them using the time out.  I wouldn't have expected there
to be such a difference in streams from the same broadcast machine.   After I
started opening up the time out, I noticed that just a couple of publishing
points would failover and I started opening up the time out for those
publishing points and fail overs became fewer and further between.

Hopefully, we are on the road to recovery now.

Thanks for your help and ideas.

BA
Signature

Bill Atkins

> >Thanks Neil:
> >Here is an example of a publishing point I am using now and will run the
[quoted text clipped - 118 lines]
> Digital Media MVP : 2004-2008
> http://mvp.support.microsoft.com/mvpfaqs
 
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.