Utility: SageTV Registry Settings

[babgvant]

SageTV Registry Settings is a simple GUI application that exposes all of the registry settings SageTV can use with a short explanation of what the setting does (as a tool tip).



The UI is dynamically driven from the included xml file, so future settings can be added easily.

bin

If anyone knows of any settings that aren't in the tool let me know and I'll add them.

[jaminben]

This looks like it will come in very handy.

Nice job

[pedz25]

Originally Posted by jaminben

This looks like it will come in very handy.

Nice job

Agreed! Thanks for putting this together.

[Brent]

I played around with this app over the weekend - a great idea indeed!

I'm curious how to use this setting:
"Custom Demux GUID"

[babgvant]

Originally Posted by Brent

I played around with this app over the weekend - a great idea indeed!

I'm curious how to use this setting:
"Custom Demux GUID"

It's the GUID for an alternate demuxer filter. I've messed with it in the past, and it seems to work fine (in some cases better, at least before the new sage demuxer got stable) for recorded tv; but fail horribly (crashing the client in some cases) for live tv.

To use it, you'll need to get the filter's CLSID from GraphEdt or GraphStudio.

GraphStudio:

[QueOnda]

Use Larger Buffers For Network Capture - Enables optimizations that help with network encoding file transfers by using much larger packet sizes (off by default, 1 enables it)

Does this help/hurt with HDHR recordings? When disabled what is the packet size? And Enabled what is the packet size?

[Narflex]

The Large Buffers For Network Capture setting only applies to network encoders (not the HDHR). It affects buffering on the output from the directshow capture device before it is sent to the network. Many capture devices output in 2K chunks; and that's not optimal for network transfers; so that option buffers them up and sends them as larger chunks (64k). It's not heavily tested though; which is why its not on by default. This setting would need to be made on the machine running the network encoder.

[QueOnda]

OIC, Thanks for the explanation. Anyone have good experience with the Max java heap size greater than 512? I read in another thread someone put theirs to 1GB and had issues.

[antplugger]

Does this work for Vista (32 and 64 bit) ?

Thanks

[babgvant]

Originally Posted by antplugger

Does this work for Vista (32 and 64 bit) ?

Thanks

It probably doesn't. But that's easy enough to fix.

[jaminben]

Could you add an option for:

ui/enable_hardware_scaling_cache=false/true

Cheers

[babgvant]

Originally Posted by babgvant

It probably doesn't. But that's easy enough to fix.

I mean it does work in x86, x64 probably puts the values in the wrong place

[babgvant]

Originally Posted by jaminben

Could you add an option for:

ui/enable_hardware_scaling_cache=false/true

Cheers

it only does registry settings, although it would be cool if it could manage properties as well.

[babgvant]

Originally Posted by babgvant

I mean it does work in x86, x64 probably puts the values in the wrong place

updated (same link)

[peternm22]

Originally Posted by babgvant

it would be cool if it could manage properties as well.

Yes... yes it would be cool...

[jaminben]

Originally Posted by babgvant

it only does registry settings, although it would be cool if it could manage properties as well.

I was thinking it would be nice to have a tool that has all the hidden enhancements available in one place. Then when you have to re-install for what ever reason you could use one tool to set all those forgotten options.

[babgvant]

Originally Posted by jaminben

I was thinking it would be nice to have a tool that has all the hidden enhancements available in one place. Then when you have to re-install for what ever reason you could use one tool to set all those forgotten options.

agreed. I'll have to see if I can change sage properties through their api.

[71_Cuda]

Originally Posted by QueOnda

OIC, Thanks for the explanation. Anyone have good experience with the Max java heap size greater than 512? I read in another thread someone put theirs to 1GB and had issues.

I'm having good luck using 1 GB. In fact, I seem to be much more stable there. I upped from 256 to 512, then to 1024 (shows up as 1065), and I seem to have fewer random crashes. I tried 1 GB because I was maxing out 512, but I max out 1024, too. Still haven't figured out why. I had a posting about this issue related to accessing migrated dvr-ms files, but didn't get any real helpful responses. I haven't tried any higher.

[alfi33]

Thanks! Great tool! How about adding an option to change the Numbuffers setting in the registry?

[babgvant]

Originally Posted by alfi33

Thanks! Great tool! How about adding an option to change the Numbuffers setting in the registry?

Last night's build included settings for the beta demuxer (is that what you're talking about?). If not, I need the key/value location.