SageTV as an independent server and client? How?

[silkshadow]

I started working on this a while ago, got stuck, got busy and then came back to it too late (SageTV trial expired) and gave up for a bit. I have/had my setup with SageTV on my sage server, Sage Client on my HTPC client and MeeTV recording on the client. That setup stunk badly: way too clunky, lots of instability and MeeTV is really not ready yet. I am finally ready to update it and what I want to do is continue to have SageTV on one box (the sage server) and also have SageTV on the client. I understand I can have SageTV act as a client and also have it work as a network encoder. The thing is, thats not what I am looking to do.

Ok, on the client I want it to be able to record normally. In other words, I want it to have its own favorites list, recording schedule, etc. However, I also want it to be able to "see" all the shows on the sage server with their full information and, of course, play them back. A bonus would be if I could also manipulate favorite options and stuff for the server but, I know that is asking too much. Basically, I am looking to setup the HTPC client as an independent SageTV "server" while also retaining, at least, some of the Sage Cllient functionality.

Finally, if I can accomplish the above, is there any way to either convert my Sage client liscense into a full Sage liscense or, if not, am I allowed to sell the client liscense to someone else (already have a buyer for that)?

Thanks!

[JasonJoel]

Don't think it can be done that way. In fact, I'm sure it can't be done that way. Now with having independant Server A being able to see the recordings AND extended info on Server B.

Of course Server A could see the files on Server B as library imports.. But then you lose the recording information. No way around that. That info is stored on the Sage wiz.bin, and there is no way for two installs to share that file or the information. That is what Sage CLIENT was made for...

Although I really don't understand why you just don't use it as a network encoder (aside from that you said you didn't want to). That would do pretty much what you are saying. Only downside is that you have one server with one list of favorites, and the network bandwidth might not be optimal.

Jason

[Opus4]

Originally Posted by silkshadow

Ok, on the client I want it to be able to record normally. In other words, I want it to have its own favorites list, recording schedule, etc. However, I also want it to be able to "see" all the shows on the sage server with their full information and, of course, play them back. A bonus would be if I could also manipulate favorite options and stuff for the server but, I know that is asking too much. Basically, I am looking to setup the HTPC client as an independent SageTV "server" while also retaining, at least, some of the Sage Cllient functionality.

If you want to have 2 separate servers, then you could share their recordings by making each system's recording dir a library import dir on the other system. But, neither system will be able to see the show details for the other system, nor can they act as clients, affecting the other's favs, settings, etc. The server doesn't believe in equality & won't deal with another server; it will only talk to clients.

Finally, if I can accomplish the above, is there any way to either convert my Sage client liscense into a full Sage liscense or, if not, am I allowed to sell the client liscense to someone else (already have a buyer for that)?

You would have to email SageTV directly for those answers. (I believe there is a clause about not reselling a license in the EULA.)

- Andy

[silkshadow]

Thanks guys!

Although I really don't understand why you just don't use it as a network encoder (aside from that you said you didn't want to). That would do pretty much what you are saying.

The reason I need to do this is because the client is a box that is not actually mine, it was given to me by some friends and relatives who come over to watch TV all the time. I think they got tired of their shows getting bumped constantly when I was running out of HD space. So it would be much easier to have a seperate favorite list. For example, we all want to watch CSI. So its on the favorite list. However, I watch it and delete it (because its automatic) but say, my cousin, hasn't seen it yet - oops. I have one girlfriend who comes back and forth from Japan and sometimes she is away for up to a couple months so her episodes que up. Stuff like that.

Basically, its about show management. With a central favorites, I have to be the one to manage all the recordings and its a pain. Also, I then have to make decisions on HD space and what to delete. The thing is, this client is connected to my LR TV (main TV) and I watch it all the time as well so I need to be able to see my recordings there too.

If you want to have 2 separate servers, then you could share their recordings by making each system's recording dir a library import dir on the other system. But, neither system will be able to see the show details for the other system, nor can they act as clients,

Humm, so my recordings will show up in the "client" as their filename, pretty much? No episode info, subtitles and stuff?

I might be better off runing SageTV and Sage Client on the same box. Wait, is that a possibility? Would that work? If not, does anyone have any possible work-around/strange configuration solutions (no matter how radical)?

Thanks!

[Opus4]

Originally Posted by silkshadow

I might be better off runing SageTV and Sage Client on the same box. Wait, is that a possibility? Would that work? If not, does anyone have any possible work-around/strange configuration solutions (no matter how radical)?

Yes, you can run a server & client on the same system, and the client can connect to the server on another system if you want. (I'm currently doing that right now.) It is probably best to make sure you install them into separate directories, though.

- Andy

[silkshadow]

Thanks Opus 4, I will give that a try. Can the client run with sageTV service is running or would I have to stop the service beore running the sage client?

[Opus4]

Originally Posted by silkshadow

Can the client run with sageTV service is running or would I have to stop the service beore running the sage client?

You can use the service. Again: install the server & client in separate dirs. In service mode, the server's UI (sagetv.exe) will run as a pseudo-client, using Sageclient.peroperties, etc.

The client will run as a regular client, connecting to whatever server you specify, using its own Sageclient.properties, etc. (That's one reason I say to use separate install dirs for server & client.) You might have to use the "-multi" parameter for the client in this case, but I don't remember... it will be easy to run both exes & see.

- Andy

[silkshadow]

In service mode, the server's UI (sagetv.exe) will run as a pseudo-client, using Sageclient.peroperties, etc.

Wait, say that again ? SageTV will run as a pseudo-client while in service mode? I did not know that, thanks! So, another possibility just came to mind. Can I use the SageTV pseudo-client to connect to both instances of SageTV (the local one and the remote one on my sage server). What I mean is, is there a toggle I could use to have sage pseudo-client connect to different servers? In lieu of that, maybe a command line parameter I could use to designate the IP to call from Meedio. Thanks Opus4!

Edit: I definately will install to different directories .

[nielm]

no -- the pseudoclient only connects to localhost

[silkshadow]

Thanks Nielm. Oh well. Humm, maybe I can install SageTV and Sage Client on this computer. Then use command line parameters from Meedio to have the client connect to different SageTVs (local and remote). Then just use SageTV on this box in service mode and never call on the GUI. Would that be possible?

[nielm]

If the client is installed in a different directory, and therefore has a different properties file -- there is no command line parameter to say 'connect to server x', but the auto-connect settings in detailed setup are stored in the properties file.

[Opus4]

Actually, there is a command line parameter: -connect hostname I just tried & had no problem using it to connect to localhost and the IP address of another PC. You may even be able to run both at the same time, but I didn't try that. (I know you can run multiple clients simultaneously, but I just haven't tried doing that when they are connecting to different servers.)

Alternatively, you can still run both the client & server UIs at the same time (or separately)... and easily control each one separately by sending event codes via Windows messages, since the client & server use different Window Class targets.

- Andy

[silkshadow]

Awsome! I can't wait to get home and give this a try. And it solves my "what to do with client license" issue . Will report back later. Thanks alot guys!

[nielm]

Actually, there is a command line parameter: -connect hostname

oops

[silkshadow]

Works great guys! I have setup a couple program modules in Meedio to call Sage client and have it connedct to the desired SageTV instance. I will finish this box up and run it for a bit. Will report if I run into any problems. Thanks again!

[Opus4]

Hmmm... I wonder if I should also mention that I successfully used my other server's IP address when I tried:

SageTV.exe -client -connect ip.address

I believe this comes from the fact that it is possible to set up a full install of SageTV to act as both a network encoder and client of the main server. Note: I did not attempt to run sagetv.exe this way when the service was running on the same system.

- Andy

[silkshadow]

Wow that is pretty cool! Dosen't change anything for me though. Since I have to buy another SageTv license anyway and already have a client one, this makes it a bit easier to program Girder tasks. Thanks though, that is a pretty cool feature!