 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows Media Server / January 2009Push publishing point does not stop when the encoder does.
Hi All, I have a problem where the publishing point starts and does not sto when the encoder stops. This causes problems for me because I a relying on the archiving function of the publishing point to creat separate archives of the content. The publishing point is a broadcast with multicast enabled. The encoder is set up as a push model. I have written an automation interface in Delphi to start and stop it but I get the same result whether I use my interface or the Window Media Encoder. Eventually the publishing point times out and stops, but this leaves m with an archive containing lotsa black video. I'm sure it will be a server config issue (open to ideas!!) as I'v done this a couple of times before with success. thanks in advance for any help. Mar -- mark http://forums.techarena.i Try to disable "Enable Broadcast auto-start" property of the publishing point. Hope it will help. Vladimir V. Polischuk www.voynex.com - custom software development, solutions for Windows Media (pay-per-minute billing, streaming content protection, access control) > Hi All, > I have a problem where the publishing point starts and does not stop [quoted text clipped - 17 lines] > > Mark Use 'pull' rather then 'push' for better control of your archiving Thanks for your replies I have already tried disabling and enabling the "Enable Broadcas auto-start" property to no avail. The push model is necessary as we are controlling the start/sto process from AMX touchpanels within lecture theatres, so the end use must be able to start and stop the publishing point by starting an stopping the encoder I am wondering if it could be connected to the DCOM permission matche between encoders and the server. Can anyone shed any light on the DCO requirements for this to work correctly thank mar -- mark http://forums.techarena.i Hi All, it's been a few weeks since I got a reply to this, does anyone have any ideas? I really need to put this one to bed and am still stumped. thanks Mark > Hi All, > I have a problem where thepublishingpointstarts and does notstop [quoted text clipped - 25 lines] > > http://forums.techarena.in Hello Mark, The solution that will definitely work relies on the custom programming. Using COM API of the WME and WMS It is possible to develop an application which will control both WME (windows media encoder) and WMS. If you need assistance with the programming, feel free to contact via www.voynex.com Regards, Vladimir V. Polischuk www.voynex.com - custom software development, solutions for Windows Media (pay-per-minute billing, streaming content protection, access control) > Hi All, > it's been a few weeks since I got a reply to this, does anyone have [quoted text clipped - 32 lines] >> >> http://forums.techarena.in Hi everyone, is there somebody who already got a working solution to this problem. When the connection from the encoder is lost the publishing point will stop after 50 to 60 seconds. I would like it the stop as soon as the connection from the encoder is lost. Because otherwise people will have to wait 50 to 60 seconds before the failover option work Thank you Cho  Signaturecho http://forums.techarena.in >Hi everyone, > [quoted text clipped - 6 lines] >Because otherwise people will have to wait 50 to 60 seconds before the >failover option work You need to use the WMNoDataTimeout (for encoder failures) and WMNoDataTimeout2 (for user initiated encoder stop) URL modifiers - i.e. query string parameters - as discussed at the bottom of this page http://msdn.microsoft.com/en-us/library/ms753592.aspx and in more detail at http://www.microsoft.com/windows/windowsmedia/howto/articles/urlmodifiers.aspx which also notes WMReconnect=1 would try to reconnect once (instead of the default 5 times) then failover to your alternate content source. HTH Cheers - Neil ------------------------------------------------ Digital Media MVP : 2004-2008 http://mvp.support.microsoft.com/mvpfaqs Thank you for your reply but it still doesn't work. Maybe i have to tell you that i want this to work in a Push scenario from the encoder. When i use the pull option it works fine. But for some reason (firewall etc) we should use the push option. So with the pull option when the connection with the encoder is lost the failover works fine, but with the push option when the connection from the encoder is lost the failover will start after +/- 50 to 60 seconds Signaturecho http://forums.techarena.in >Maybe i have to tell you that i want this to work in a Push scenario >from the encoder. Yes, sorry I hadn't read that, as it was in the post subject. >When i use the pull option it works fine. But for some reason (firewall >etc) we should use the push option. [quoted text clipped - 3 lines] >from the encoder is lost the failover will start after +/- 50 to 60 >seconds Can you post the WSX which you use on the publishing point for failover ? Cheers - Neil ------------------------------------------------ Digital Media MVP : 2004-2008 http://mvp.support.microsoft.com/mvpfaqs Hi Neil i have been on a holiday so here's my reply I have worked out a solution that works for me now. I have used the performance monitor of windows. I created an alarm t check on a publishing point. The counter i used is "current file rea rate" Then i set the alarm when the value is under 1, this means that i there are less then 1 bytes send to the publishing point then the alar is activate. Also put the interval on 6 seconds In the action tab i used "run this program" i put the path to a simpl batch script i wrote. In this batch file i used the wmcontroller too (http://shootingstarbbs.kicks-ass.net/wmcontroller) to stop th publishing point. So what happens now is that the alarm will check every 6 seconds i there are bytes sent from the encoder to the publishing point and if no stops the publishing poin -- ch http://forums.techarena.i |
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.