[Schedules Direct] SageTV developers: new API

[wayner]

Yes, but back then you could also buy boxes from Rogers or FutureShop for decent prices. So Rogers wasn't overly concerned about monthly revenue from cable boxes. I think the best deal I got was something like $200 for a 3250HD or 4250HD with a $100 programming credit for Rogers. I had about 10 boxes and I owned them all. They are starting to die, but I need at least two connected to the HD-PVRs on my SageTV server. You can still find them used on Kijiji.

It is interesting that TiVo was never able to really capitalize on what was revolutionary technology. I wonder if they were just in a weak competitive position due to the strength of the cable/sat providers, or if they screwed up their business strategy.

My first DVR (circa 2001) was a hacked Series 1 TiVo since they didn't sell their service in Canada. But you could download the guide data from XMLTV, reformat it and FTP it to your S1 TiVo. But you needed a special TiVonet card to do that. That was WAY harder then keeping a SageTV server running. From there I went to BeyondTV to WinMCE and then to SageTV.

[EnterNoEscape]

I just want everyone to note that the Schedules Direct API is versioned in that we can tell it what version of the API we want to use. SageTV is not in any peril if their insanely longstanding support for their first XML API is any indication. The only thing this is likely to mean is that we won't be able to take advantage of new features. I have posted a question in their forums about this specific thing.

[nyplayer]

Originally Posted by EnterNoEscape

I just want everyone to note that the Schedules Direct API is versioned in that we can tell it what version of the API we want to use. SageTV is not in any peril if their insanely longstanding support for their first XML API is any indication. The only thing this is likely to mean is that we won't be able to take advantage of new features. I have posted a question in their forums about this specific thing.

Thanks.

[newyankee]

Originally Posted by EnterNoEscape

I just want everyone to note that the Schedules Direct API is versioned in that we can tell it what version of the API we want to use. SageTV is not in any peril if their insanely longstanding support for their first XML API is any indication. The only thing this is likely to mean is that we won't be able to take advantage of new features. I have posted a question in their forums about this specific thing.

+1 Thanks, just what I needed to know

[tvmaster2]

Originally Posted by EnterNoEscape

I just want everyone to note that the Schedules Direct API is versioned in that we can tell it what version of the API we want to use. SageTV is not in any peril if their insanely longstanding support for their first XML API is any indication. The only thing this is likely to mean is that we won't be able to take advantage of new features. I have posted a question in their forums about this specific thing.

Thanks. Good idea to look in their forums a well. The more Sage people who use that and comment could help going forward...

[VCRUser]

Originally Posted by tvmaster2

Thanks. Good idea to look in their forums a well. The more Sage people who use that and comment could help going forward...

I checked into their forum, but couldn't find the place where this is discussed. Can you post a link? I'd be glad to add a supportive comment if I could find the right place.

[NetworkGuy]

Originally Posted by VCRUser

I checked into their forum, but couldn't find the place where this is discussed. Can you post a link? I'd be glad to add a supportive comment if I could find the right place.

+1. I will also.

[nyplayer]

https://forums.schedulesdirect.org/v...7&p=9987#p9987

[wayner]

Originally Posted by nyplayer

https://forums.schedulesdirect.org/v...7&p=9987#p9987

Those forums are comatose!

[tvmaster2]

Originally Posted by wayner

Those forums are comatose!

but maybe the SD people look in?

[VCRUser]

Originally Posted by nyplayer

https://forums.schedulesdirect.org/v...7&p=9987#p9987

Thanks. I found the topic, but can't post to it because apparenty though I'm registered with the SD service, I may not be registered with the forum - and i can't find a link to use for registration. I used the "contact us" so maybe the board admin will help me out. Meanwhile, if you know where they hide the registration link...

[emveepee]

Are you guys really serious about abandoning SageTV because of this? That would be pretty much be the only case you could make.

If I was on the SD end I'd tell you to look at an XMLTV options they source, using their native service, mc2xml, or epg123. It's a business and why run a parallel service indefinitely for a few users. It might be different if there was a developer here willing to give some time estimates.

Martin

[btrcp2000]

My preference is to stay put, but per your comment about developers, lots of things would be different or better if any were available. I think we are probably okay for a while, and I'm okay putting time in, but I'm not putting more money into sage at this point.

I'm learning about Channels because it's interesting anyway, but I don;t want us to be without a DVR for a week while I figure it out. Done that before and it's very annoying.

[wayner]

Originally Posted by emveepee

Are you guys really serious about abandoning SageTV because of this? That would be pretty much be the only case you could make.

The problem is that we are losing so many of the folks that did all of the developing. I believe the original SD work was done as a plugin by Slugger which was an alternative to the original guide data that still came from SageTV. A lot the work in recent years on SageTV, including the Android TV client development was done by stuckless but he has recently left. Fuzzy used to also help out and was a great resource in helping folks, but he also appears to be gone. Sure there are still a few folks around doing some great work - so thanks to all of those people.

If something big changes that SageTV depends on then who is going to be left to fix it? We have to start to get prepared for that to happen.

[EnterNoEscape]

I hope you all can take some comfort in that I have previously stated, I will do whatever is required to keep the Schedules Direct EPG working. If they EOL the current API version in a year, I will make sure we are already using the new version before then. I may poke around the beta version over the next few months, but I will not push any changes to the main project until the new API is out of beta.

One of the things a lot of users will like is that the service will start to allow up to 5 tokens at a time so you don't have multiple servers fighting over who gets the token.

[KeithAbbott]

Originally Posted by EnterNoEscape

I hope you all can take some comfort in that I have previously stated, I will do whatever is required to keep the Schedules Direct EPG working. If they EOL the current API version in a year, I will make sure we are already using the new version before then. I may poke around the beta version over the next few months, but I will not push any changes to the main project until the new API is out of beta.

One of the things a lot of users will like is that the service will start to allow up to 5 tokens at a time so you don't have multiple servers fighting over who gets the token.

On behalf of every active SageTV user, thank you!

[jpwegas]

Originally Posted by EnterNoEscape

I hope you all can take some comfort in that I have previously stated, I will do whatever is required to keep the Schedules Direct EPG working. If they EOL the current API version in a year, I will make sure we are already using the new version before then.

Thank you for this!

--John

[wnjj]

Ditto on the thanks. As a long time user of only OTA and ripped DVD's I would certainly step up to take on SD changes but that would be a big task. Thankfully I don't have to for the near future at least.

[tvmaster2]

Originally Posted by EnterNoEscape

I hope you all can take some comfort in that I have previously stated, I will do whatever is required to keep the Schedules Direct EPG working. If they EOL the current API version in a year, I will make sure we are already using the new version before then. I may poke around the beta version over the next few months, but I will not push any changes to the main project until the new API is out of beta.

One of the things a lot of users will like is that the service will start to allow up to 5 tokens at a time so you don't have multiple servers fighting over who gets the token.

of course, besides Todd Rundgren, you’re now ‘our hero’

[EnterNoEscape]

What I find most interesting is that downloading images with the new API now requires authentication. I suspect we'll need to create a custom path in the image downloading code to know when to use a Schedules Direct token.

What I would prefer is that SDRipper can register a custom handler with the part of SageTV that handles image downloading (probably via an interface) and that would be how we can make sure we have a valid token for each request. I might attempt to implement this mechanism in the mean time.