This project is read-only.

Feature Requests

May 21, 2009 at 12:52 AM

What features would be nice to add to the plugin?

May 25, 2009 at 3:41 PM


Thanx for the great effort you guys have put in to Project Starlight. I've started using parts of the managed library because were interested in the failover capabillity when using .asx playlists as source that Project Starlight implements.

I've found the following issue when using the asxParser.ParsePlaylistAsync() method. When i send an .asx playlist through that contains a live broadcast source as one of it's elements, the associated mediaelement often goes into an infinte loop of firing the mediaelement.BufferingProgressChanged event over and over again. It seems that this is a known issue with the Silverlight mediaelement.

Has Project Starlight come up with any solutions for this?




May 26, 2009 at 5:46 PM

No, we have not.  In general, the behavior of multiple unicast streams failing over is not something we have tested a great deal.  The major use case we have been targeting with the playlist functionality is failing over from a multicast stream to a unicast stream, which does work properly.  We will most likely end up implementing something like was proposed in the first link (timer checking buffering progress) if this become necessary.


May 27, 2009 at 8:49 AM

Thx, that's what I have ended up doing aswell. :-)

May 29, 2009 at 12:06 AM

If you are using a modification of the Starlight code it would be wonderful if you could upload a patch containing your changes so that we can incorporate those changes into the base project.  The license does not require this, so if you can't/don't want to, no worries.

Aug 6, 2009 at 2:30 PM

Does the plugin support closed caption for multicast stream?  I used MarkerReached event to display closed caption.  It works for unicast stream, but not for multicast stream.  Any suggestion on how to add CC support for multicast?

Thanks for your great effort.

Aug 6, 2009 at 5:02 PM

Unfortunately it is not feasible to support markers embedded in the stream.  The problem is that the MediaStreamSource API provides no way to report that these events have occured (see