New to SageTV

[Mountainbreeze]

Hello everyone.

I am in the early stages of converting over to SageTV from BeyondTV. For now, I am checking out the functionality of STV and I got say, it is really nice and I am liking it a lot.

What I have done so far is to load version 9 on a Vista OS box, set up one of my HDHR tuners without guide data, and installed the Commercial Detector UI add-on.

I'm sure I'll be needing more help in the future and I'll try not to ask until I have attempted to find a solution on my own.

For now, I wanted to enquire about something and I want to be sure I have not done something wrong...

After the initial install of STV, I went through the setup without issue. After checking out a few things, I decided to set it up to run as a service. After doing so, and restarting the UI, it is forcing me to go through the setup again. Is this normal?

Thanks

[wnjj]

Yes (I think). I believe the normal mode (which is a client and server) and service mode (server only) have different .properties files, which is where the setup stuff goes. When you connect to the server as it runs in service mode, I think a sageclient.properties file is used for the client settings and sage.properties is still used for the server settings.

[Fuzzy]

Sage really has two different sets of configurations involved. There is the backend properties (scheduling, source configs, storage locations, etc), and the frontend properties. In Standalone mode (service disabled, sage launched via SageTV.exe), both sets of properties come from Sage.properties. When in service mode, however, the backend stuff (read by SageTVService.exe) comes from Sage.properties, while the frontend stuff (read by SageTV.exe on the server, or SageTVClient.exe on a client pc) comes from SageClient.properties.

So, after running through the wizard in standalone mode, you've setup all the backend and frontend stuff in Sage.properties, but then when you switched to service mode, the backend stuff is still configured just fine, but the frontend stuff needs to be configured again, so ti runs you through the wizard again. The backend stuff (source, storage locations, etc) should all be configured already as you are going through the wizard the second time, so you can just 'next' on through those steps.

[Mountainbreeze]

That makes perfect sense. Thanks for the explanation. Here's a beer for you