Open Source Project

[Fuzzy]

Ah.. okay.. Sorry, I thought I saw reference to it in the EPG area, but that system property is likely what I saw.

[Narflex]

Originally Posted by Fuzzy

Ah.. okay.. Sorry, I thought I saw reference to it in the EPG area, but that system property is likely what I saw.

Or you saw the old 'access code' stuff which is when we first launched SageTV in 2003 and actually charged separately for EPG data...but that phase didn't last very long.

[Fuzzy]

Originally Posted by Narflex

Or you saw the old 'access code' stuff which is when we first launched SageTV in 2003 and actually charged separately for EPG data...but that phase didn't last very long.

That could be.

[sacrament055]

Originally Posted by Fuzzy

So, with the source opened up, i was able to alter the user-agent that Sage uses. By spoofing XBMC's user-agent, PlayOn now sends 720p, so that's a good level of success. Requires a sage.jar from v9, which seems to break some other things (looks like gemstone doesn't like v9 yet - haven't looked into that one yet). But yeah for being a few steps closer to a new feature as a result of open sourced sagetv!

Any chance you'd share your customer sage.jar that allows for HD Playon support?

[Fuzzy]

Originally Posted by sacrament055

Any chance you'd share your customer sage.jar that allows for HD Playon support?

The ability has been merged into the v9 master branch, just a matter of someone compiling it up. I won't be able to for a few days (away from my main computer).

[Pumpkinhead]

Originally Posted by Narflex

Actually...it would work. The EPG server doesn't care what client you are on. It just cares about a valid key. All you'd need to do is put your SageTV license key in a file called 'activkey' in the same folder as your SageTV install. You can deduce that by looking at the 'startsage' and 'startsagecore' startup scripts for it.

That's cool. I still, I still have an older key for SageTV version 4 (IIRC) with a lot more characters in it that wouldn't work for SageTV 7. So I take it the much older key will work in the OpenSource version for EPG since it is indeed a valid licensed key that allowed me to get EPG in a much older version.

[Fuzzy]

I believe it should in theory, though in practice, they likely didn't add those old keys to the EPG server.

[nycjoe]

Narflex, do you want people to add external utilities to the github project? I have some shell scripts that I run outside of SageTV entirely. Should those come in the form of a pull request?

Would you prefer that questions like this come in the form of a github issue?

[Narflex]

Originally Posted by nycjoe

Narflex, do you want people to add external utilities to the github project? I have some shell scripts that I run outside of SageTV entirely. Should those come in the form of a pull request?

Would you prefer that questions like this come in the form of a github issue?

It all depends upon what the external utility is. There's definitely already quite a few in the open source repo.

Everything to submit should be a pull request (at least that's what's been happening so far..and this is my first usage of GitHub). And we are already using the Github issue tracker for a few things, so feel free to open up new ones.

[AtariJeff]

Originally Posted by jm9843

1. Linux built from source: put your SageTV license key in a file called 'activkey' in the same folder as your SageTV install
   

When I install SageTV from the compiled .deb file where does it install?

[Taddeusz]

Originally Posted by AtariJeff

When I install SageTV from the compiled .deb file where does it install?

For the server:
/opt/sagetv/server

For the client:
/opt/sagetv/client

[AtariJeff]

Thanks. That did the trick.