Question regarding running SageTV as service

[jarredduq]

Hello,

I set up my SageTV to run as a service yesterday, and lost the pass through of DTS/Dolby Digital over SPDIF with MKV files. I then disabled the run as service, and the pass through was restored.

My question is, does SageTV use a different properties file when run as a service, or is this a bug? I'm running v6.5.13.

Thanks,

Jarred

[HelenWeathers]

If the only difference is running SageTV as a service, then I would report this as a bug.

Edit: do not report as a bug -Opus4

[Razillian]

When run as a service sage splits up many of the settings into two properties files: sageclient.properties and sage.properties

The decoder used was probably reset to whatever sage thinks it should use for MKV (h264?) files and not what you have previously set. Compare the videoframe section of the sage.properties and the sageclient.properties files to look for a difference.

[stanger89]

Exactly, I'd just double check your settings in Detailed Seutp for audio/video/DVD and make sure they're what you expect them to be when you're running the service.

Another possibility is to delete the sageclient.properties file and restart the Sage UI with it configured to run as a service. I believe that should cause Sage to rebuild the sageclient.properties file from the server's config.

[HelenWeathers]

Every day I learn something I didn't know. I haven't had a SageClient.properties file in my SageTV folder on my server since I did a clean install of SageTV 6.5.11 beta (then .12 and .13). I wondered why. It turns out that I have never run SageTV on my server since putting Sage into service mode and ergo - no SageClient.properties file was ever created.

I need more coffee before I even think about thinking.

[Opus4]

As mentioned by others above: this is not a bug.

For future reference, it might be useful to check out the SageTV PDF manual: Chapter 2's "Controlling SageTV’s Service Mode Options" covers the property file difference, as does Appendix A.

- Andy