Annoyances caused by sporting events

[snagglewest]

http://www.livepvrdata.com/events.jsp

Unfortunately it doesn't monitor racing (nascar & F1) anymore which cripples it.

Snag

[mvallevand]

http://www.livepvrdata.com/events.jsp

Unfortunately it doesn't monitor racing (nascar & F1) anymore which cripples it.

Snag

It was inadvertently disabled on the monitoring site, it should be working again. I do need to post an update soon though.

Martin

[mvallevand]

http://www.livepvrdata.com/events.jsp

Unfortunately it doesn't monitor racing (nascar & F1) anymore which cripples it.

Snag

Thanks for the report, it was inadvertently disabled on the monitoring site, Slugger the developer and current support of the site go it working again. I do need to post an update soon though but the bigger worry is no one has stepped up on the SageTV site to maintain it when Slugger steps back soon. Anyone here with server side skills is free to pipe up here http://forums.sagetv.com/forums/showthread.php?t=57364

Martin

[BrettB]

Thanks for the report, it was inadvertently disabled on the monitoring site, Slugger the developer and current support of the site go it working again. I do need to post an update soon though but the bigger worry is no one has stepped up on the SageTV site to maintain it when Slugger steps back soon. Anyone here with server side skills is free to pipe up here http://forums.sagetv.com/forums/showthread.php?t=57364

I've noticed (after the fact) that the last 2 Sunday evening recordings have been "cut short" due to their actual start times being pushed back. So I went to check on NextEnd. And, after a little looking, I found that the site it uses for game data (livepvrdata.com) no longer exists. Then I found we were warned by Martin in this post that this was coming. BIG BOO!!!

In the thread on the SageTV forum, there is reference to a similar service offered by SchedulesDirect. I believe that sub has incorporated that as an option for extending recordings of actual sports events. But, I don't believe that he's done anything to use that information to extend recordings after those events. (Which is my primary use for NextEnd)

So, I'm wondering if Martin and Sub can let us know their thoughts about any work they might already be doing or thinking about doing to address the issue of programs getting pushed back due to sports events.

[sub]

The info that comes from SchedulesDirect only covers sports events, and unfortunately the app has no way to know what might have happened to shows following a sports event that ran late.

The action the broadcaster would take be up to them, and would probably vary on lots of factors, like how late they are, how long the show following it was, whether it was the type of show that had to air that day, whether they had an appropriate duration filler to get them back on scheduler, etc. ie, they might just play the show late, or they might not play the show at all (instead replacing it with another shorter show that gets them back on schedule), or might defer it to next week, etc.

[BrettB]

The info that comes from SchedulesDirect only covers sports events, and unfortunately the app has no way to know what might have happened to shows following a sports event that ran late.

The action the broadcaster would take be up to them, and would probably vary on lots of factors, like how late they are, how long the show following it was, whether it was the type of show that had to air that day, whether they had an appropriate duration filler to get them back on scheduler, etc. ie, they might just play the show late, or they might not play the show at all (instead replacing it with another shorter show that gets them back on schedule), or might defer it to next week, etc.

Yes, the data source that Martin's NextEnd used also only covered sports events. And we know that broadcasters do various things to "fix" the situation when sports run long. But based upon trying to be "better safe than sorry" or "better to have too much than not enough", NextEnd would detect when monitored sports events before scheduled recordings ran long. And, if it detected that situation, then it would (attempt) to lengthen the (post-padding?) recording time of the following scheduled recordings to cover the situation where the broadcaster just pushed everything back. This solution worked very well on Sundays and Thursdays for long NFL games.

[mvallevand]

I will have a look I have been out of the country. I did some work early to use some new URL's from SageTV and also can support SD in NextEnd, but haven't followed closely for months.

Martin

[BrettB]

I will have a look I have been out of the country. I did some work early to use some new URL's from SageTV and also can support SD in NextEnd, but haven't followed closely for months.

Great. Thanks, Martin!

P.S. While you're looking at it, if you can see/think about extending the --Sunday functionality to work on other/all days (so that Late Night will work on Thursdays without having to record the news between the NFL game and it, etc.), that would be nice, too. :-)

[mvallevand]

Ok I have an update that will

- use the local instance of livepvrdata like sage tv
- use schedules direct stillRunning API (server appears broken now, Robert is checking)
- do a late nite check on the --sunday option and extend recordings starting from 10:30 - 1:30

If anyone wants to beta test this let me know. You need to have java and download and run a java web server called jetty and I will provide the livepvrdata.war app.

Martin

[BrettB]

If anyone wants to beta test this let me know. You need to have java and download and run a java web server called jetty and I will provide the livepvrdata.war app.

Definitely count me in.