Start Client mode Fullscreen, server to tray

[jchiso]

Is there a way to set parameters such that a system starts in Client mode fullscreen, while running the server minimized to the system tray? I know this is easy to do manually, but I'd like to set that as a default startup profile.

[GKusnick]

I'm not clear on what you're asking. If you use the SageTV Service, it runs invisibly in the background, and you can configure the UI startup mode however you like. If you don't use the service, then there's only one component that includes both the UI and the server functionality, and again, you can configure the UI to start up either way.

This is all assuming you're running on Windows. If not, your question might make more sense in the Linux or Mac forums.

[jchiso]

I'm running XP.

I have a system running a SageTV server (or SageTV Media Center, or whatever it's called now; a SageTV back-end. I want to use this system as a network encoder for another server (back-end) and as a client to another server (or server). I'd like this to start up full screen as a Client; not as a server, since the only "serving" it will be doing is encoding for another server.

[GKusnick]

I'm not an expert on network encoding; is it not possible to run the encoder in service mode? Then you can do whatever you like with the client.

[jchiso]

Originally Posted by GKusnick

I'm not an expert on network encoding; is it not possible to run the encoder in service mode? Then you can do whatever you like with the client.

For the PC in question it is the client.

PC1: Main server system with two (2) satellite STBs and two (2) OTA ATSC tuners.

PC2 (the one in question): An instance of SageTV server (Media Center/backend/encoder) with one (1) satellite STB and two (2) OTA ATSC tuners, acting solely as network encoder for PC1.

PC2 would run as a Client (backend) to the PC1 server; I want PC2 to run (start) in fullscreen Client mode and start its server (network encode) in the system tray.

I could manually start the Server, minimize it to the tray and start a second instance with the -client option and set it to run full screen. I just want to be able to do that without manual intervention ...

[Fuzzy]

I think there is a way to set sage to start minimized. In which case, whatever setting that is, configure that in the sage.properties file. Then configure it to start fullscreen in the sageclient.properties file. Should work, as starting with the -client switch uses the sageclient settings.

[jchiso]

Originally Posted by Fuzzy

I think there is a way to set sage to start minimized. In which case, whatever setting that is, configure that in the sage.properties file. Then configure it to start fullscreen in the sageclient.properties file ...

Well, there is a ui/startup_type property that's set to "0" in the SageClient.properties file and "1" in the Sage.properties file, but there is no mention of this property in the manual's appendix, so it looks like I'll just have to try to manipulate this property and see what happens ...

[GKusnick]

Originally Posted by jchiso

I could manually start the Server, minimize it to the tray and start a second instance with the -client option and set it to run full screen. I just want to be able to do that without manual intervention ...

You could always make a batch file to start them up and send them Full Screen or Minimize commands as apprpriate. Appendix D tells how to send Sage commands from the command line.

I'm still not clear on why it's better to have the network encoder running as a foreground app, but minimized to the tray, rather than as a background service that doesn't appear on the desktop at all. But if that's the way you want it, I'm sure it's possible somehow or other.

[jchiso]

Originally Posted by GKusnick

You could always make a batch file to start them up and send them Full Screen or Minimize commands as apprpriate ... I'm still not clear on why it's better to have the network encoder running as a foreground app, but minimized to the tray, rather than as a background service that doesn't appear on the desktop at all ...

I'm not familiar with the Service Mode. I think I tried it many years ago, but I'm sure they've changed stuff since then, and I don't really understand the purpose of it. I just wondered if there was a simple way to automate the process. I'll probably just go with a batch file at startup ...

[GKusnick]

The purpose of service mode is to make the server component run invisibly in the background, without having to launch an app at startup. Services start as soon as Windows boots up, so you don't have to be logged in for them to work, and they'll keep running if you log out and back in as a different user. They can also restart themselves automatically in case of a crash. Basically anything you want to run continuously, without interruption, regardless of what happens at the keyboard, you want to run as a service.

[Fuzzy]

To enable it, you run the SageTVServiceControl.exe file (it should be in your start menu).

[jchiso]

Originally Posted by GKusnick

The purpose of service mode is to make the server component run invisibly in the background, without having to launch an app at startup ..

Originally Posted by Fuzzy

To enable it, you run the SageTVServiceControl.exe file (it should be in your start menu).

Thanks for the info. I'll look into going this route; encoding server in service mode, client (mode) in fullscreen, desktop mode ...

[jchiso]

Tried a couple of different things. Running as service and setting a client-mode instance to start fullscreen still does not work. The system always starts with the server running fullscreen. Also tried running the server on the desktop, specifying its startup state as "Minimized to Tray", then starting a second instance in Client mode, and set its startup state to "Fullscreen". Upon reboot, the system starts with just the server instance in fullscreen mode ...

[Fuzzy]

Do you still have the server instance set to run at startup? Once you enable the service, you no longer have to actually launch sagetv.exe on startup, it will be running invisibly in the background.

[jchiso]

Originally Posted by Fuzzy

Do you still have the server instance set to run at startup?..

Yes, I tried it that way and it failed to start the client-mode user interface ...

[Fuzzy]

Originally Posted by jchiso

Yes, I tried it that way and it failed to start the client-mode user interface ...

I'm saying you DON'T want to be running sagetv for the server process. All you will want to do si run the sagetv -client command when you want the UI up.

[jchiso]

Originally Posted by Fuzzy

I'm saying you DON'T want to be running sagetv for the server process. All you will want to do si run the sagetv -client command when you want the UI up.

That's what I tried to do. I started the client instance, and set it to start in fullscreen mode. I set the server to start as a Service. When it rebooted it starts the SERVER in fullscreen and does not launch the Client-mode instance at all ...

[Fuzzy]

The setting in detailed setup isn't going to work for your client instance. You'll just have to make your own shortcut in the startup folder with the -client parameter.

Personally, my way of fixing it would be to get rid of the kludgy network encoder, and move everything to a single server...

[jchiso]

Originally Posted by Fuzzy

The setting in detailed setup isn't going to work for your client instance. You'll just have to make your own shortcut in the startup folder with the -client parameter.

Hopefully that works. I'll give it a shot.

Personally, my way of fixing it would be to get rid of the kludgy network encoder, and move everything to a single server...

The problem is that the server has maxed out on physical slots and cabling, and the network encoder and associated set-top box are in a different location ...

[Fuzzy]

Originally Posted by jchiso

The problem is that the server has maxed out on physical slots and cabling, and the network encoder and associated set-top box are in a different location ...

Upgrade to dual tuner cards, with two of them in your main server, or get a new board with more slots for the main server. Probably pay for themselves in the power costs of running the second machine in about 2 years...