Lost settings when converting to service mode

[KiwiBobs]

Before service mode, Sage.Properties is used.

After converting to service mode, service uses Sage.Properties and the UI uses SageClient.properties.

I have already tried deleting SageClient.properties but it still goes through the config wizard and does not import from Sage.Properties.

How do I get SageClient.properties initialized to the values from Sage.Properties? I want the UI to have the same settings as before.

I am running Version 7 (downloaded one week ago)

[Brent94Z]

I had similar happen when I switched to using service mode. I ended up just doing them over again on most of them but some of them (I think my remote settings) I copied and pasted out of the sage.properties file to the sageclient.properties file.

Probably not what you wanted to hear but not sure of an easier way other than hunting and pecking through the properties files and copying/pasting the ones you want while at the same time trying not to break something that is specific to the client.

[KiwiBobs]

I ended up doing a diff between the two files. Anything common to both files that was changed in Sage.properties I copied that line over to SageClient.properties. Here were my lines changed. Your's will vary because you may have changed different things. The big one which will save you a lot of reconfiguring is keyboard_accelerators - copy that over saved me from having to redo all my keyboard mappings.

keyboard_accelerators
ui/epg_font_size2
ui/epg_num_cols=4
ui/epg_num_rows=7
ui/screen_saver_on_sleep
ui/wrap_around_scrolling_enabled/epg_grid_vertical
online_video/update/auto_update
videoframe/audio_decoder_filter=NVIDIA Audio Decoder
videoframe/audio_render_filter=DirectSound\: M-Audio Audiophile USB SPDIF
videoframe/video_decoder_filter=NVIDIA Video Decoder

As to why there are two configuration files I do not understand. That is a bad design. The different applications should use the same properties file and ignore entries that do not apply to the application. In the database world it is called data redundancy - you don't have two sets of the same data because if you update one set, the other is out of date.

[Fuzzy]

sage.properties is supposed to be used for the server settings, and sageclient.properties is used for the UI settings. However, for some reason (I think it's a legacy issue) when you are NOT in service mode, sage.properties contains both the server AND the UI settings. It's one of those things that probably should have been changed many major revisions ago, but at the same time, most people are never switching between service and standalone mode. Personally, I think it would make more sense if they just made service mode the standard method, and got rid of the standalone mode entirely.

Of course, I wish there were a lot of architecture changes that probably won't ever be changed once a product hits the sixth major version. I'd love the licensing to change to have a server license, and x number of client licenses. Those client connections could be either placeshifter, client, or extender. I also wish that you could launch 'helper' services on other PC's that could handle certain tasks, like conversion and placeshifter serving (much like the network encoder feature does now for recording). I think these changes would make the system more flexible - and the licensing especially would help with getting up and running.