Can HD-PVR Brightness, Saturation, Contrast, etc. Be Controlled From Properties File?

[egeller]

I just noticed that Hauppauge posted a new HDPVR beta driver on Oct 24. In the documentation they say:

Initialize ProcAmp values in Firmware (helps Linux/Mac installations)
sys_status.brightness = 128;
sys_status.contrast = 64;
sys_status.hue = 0;
sys_status.saturation = 64;
sys_status.sharpness = 128;

I wonder if this will eliminate the manual workaround for updating sage.properties found with the driver version 1.6.29207.

[gplasky]

Originally Posted by egeller

I just noticed that Hauppauge posted a new HDPVR beta driver on Oct 24. In the documentation they say:

Initialize ProcAmp values in Firmware (helps Linux/Mac installations)
sys_status.brightness = 128;
sys_status.contrast = 64;
sys_status.hue = 0;
sys_status.saturation = 64;
sys_status.sharpness = 128;

I wonder if this will eliminate the manual workaround for updating sage.properties found with the driver version 1.6.29207.

Don't know. But it only references that for Linux and Mac installations. Because they read it from the firmware. Windows does not.

Gerry

[Mesh]

I'm having the same problem since I added another tuner card. I've tried the fix but for some reason the settings reset once I restart sage after I making the changes.

thanks,
Mike

[doncote0]

Originally Posted by Mesh

I'm having the same problem since I added another tuner card. I've tried the fix but for some reason the settings reset once I restart sage after I making the changes.

thanks,
Mike

As with any sage.properties change, all instances of sagetv.exe and sagetvservice.exe must be ended before changes are made. Failing to do so will not enable permanent changes.

Exit the sagetv gui and use "net stop sagetv" for the service (or you can use the SageTV Service Controller app).

Check in the TASK MANAGER before making changes. (End task any remaining Sage processes.)

[MattHelm]

Could someone post their entire HD-PVR section of the properties, I think I messed mine up.


Or another reason why a perfectly running HD-PVR would start acting up.
(mine didn't even need daily resets, and now even a NEW one crashes within a few hours of reboot)

[bling_bling_vr6]

This is the the HDPVR section of my .properties file:

---start---
mmc/encoders/-431556906/2/0/available_channels=
mmc/encoders/-431556906/2/0/brightness=-1
mmc/encoders/-431556906/2/0/broadcast_standard=
mmc/encoders/-431556906/2/0/contrast=-1
mmc/encoders/-431556906/2/0/device_name=
mmc/encoders/-431556906/2/0/hue=-1
mmc/encoders/-431556906/2/0/last_channel=
mmc/encoders/-431556906/2/0/provider_id=0
mmc/encoders/-431556906/2/0/saturation=-1
mmc/encoders/-431556906/2/0/sharpness=-1
mmc/encoders/-431556906/2/0/tuning_mode=
mmc/encoders/-431556906/2/0/tuning_plugin=
mmc/encoders/-431556906/2/0/tuning_plugin_port=0
mmc/encoders/-431556906/2/0/video_crossbar_index=0
mmc/encoders/-431556906/2/0/video_crossbar_type=2
mmc/encoders/-431556906/3/0/available_channels=
mmc/encoders/-431556906/3/0/brightness=128
mmc/encoders/-431556906/3/0/broadcast_standard=
mmc/encoders/-431556906/3/0/contrast=64
mmc/encoders/-431556906/3/0/device_name=
mmc/encoders/-431556906/3/0/hue=120
mmc/encoders/-431556906/3/0/last_channel=
mmc/encoders/-431556906/3/0/provider_id=0
mmc/encoders/-431556906/3/0/saturation=64
mmc/encoders/-431556906/3/0/sharpness=128
mmc/encoders/-431556906/3/0/tuning_mode=
mmc/encoders/-431556906/3/0/tuning_plugin=
mmc/encoders/-431556906/3/0/tuning_plugin_port=0
mmc/encoders/-431556906/3/0/video_crossbar_index=0
mmc/encoders/-431556906/3/0/video_crossbar_type=3
mmc/encoders/-431556906/5/0/available_channels=
mmc/encoders/-431556906/5/0/brightness=128
mmc/encoders/-431556906/5/0/broadcast_standard=
mmc/encoders/-431556906/5/0/contrast=64
mmc/encoders/-431556906/5/0/device_name=Motorola
mmc/encoders/-431556906/5/0/hue=127
mmc/encoders/-431556906/5/0/last_channel=190
mmc/encoders/-431556906/5/0/provider_id=962137800645
mmc/encoders/-431556906/5/0/saturation=64
mmc/encoders/-431556906/5/0/sharpness=128
mmc/encoders/-431556906/5/0/tuning_mode=
mmc/encoders/-431556906/5/0/tuning_plugin=C\:\\Program Files (x86)\\SageTV\\Common\\LMSTVIRTuner2.dll
mmc/encoders/-431556906/5/0/tuning_plugin_port=0
mmc/encoders/-431556906/5/0/video_crossbar_index=0
mmc/encoders/-431556906/5/0/video_crossbar_type=5
mmc/encoders/-431556906/90/0/available_channels=
mmc/encoders/-431556906/90/0/brightness=128
mmc/encoders/-431556906/90/0/broadcast_standard=
mmc/encoders/-431556906/90/0/contrast=64
mmc/encoders/-431556906/90/0/device_name=Motorola
mmc/encoders/-431556906/90/0/hue=120
mmc/encoders/-431556906/90/0/last_channel=123
mmc/encoders/-431556906/90/0/provider_id=0
mmc/encoders/-431556906/90/0/saturation=64
mmc/encoders/-431556906/90/0/sharpness=128
mmc/encoders/-431556906/90/0/tuning_mode=
mmc/encoders/-431556906/90/0/tuning_plugin=C\:\\Program Files (x86)\\SageTV\\Common\\LMSTVIRTuner.dll
mmc/encoders/-431556906/90/0/tuning_plugin_port=0
mmc/encoders/-431556906/90/0/video_crossbar_index=0
mmc/encoders/-431556906/90/0/video_crossbar_type=90
mmc/encoders/-431556906/audio_capture_device_index=-1
mmc/encoders/-431556906/audio_capture_device_name=
mmc/encoders/-431556906/audio_capture_device_num=0
mmc/encoders/-431556906/audio_processor=
mmc/encoders/-431556906/broadcast_standard=
mmc/encoders/-431556906/capture_config=1050624
mmc/encoders/-431556906/default_device_quality=Best-H.264
mmc/encoders/-431556906/delay_to_wait_after_tuning=4000
mmc/encoders/-431556906/device_class=DirectShow
mmc/encoders/-431556906/dshow_tv_type=
mmc/encoders/-431556906/encoder_merit=4
mmc/encoders/-431556906/encoding_host=
mmc/encoders/-431556906/forced_video_storage_path_prefix=
mmc/encoders/-431556906/last_cross_index=0
mmc/encoders/-431556906/last_cross_type=5
mmc/encoders/-431556906/live_audio_input=
mmc/encoders/-431556906/never_stop_encoding=false
mmc/encoders/-431556906/video_capture_device_name=Hauppauge HD PVR Capture Device
mmc/encoders/-431556906/video_capture_device_num=0
mmc/encoders/-431556906/video_encoding_params=Best-H.264
mmc/encoders/-431556906/video_processor=
---end---

[KeithAbbott]

Originally Posted by MattHelm

Or another reason why a perfectly running HD-PVR would start acting up.
(mine didn't even need daily resets, and now even a NEW one crashes within a few hours of reboot)

Maybe your power supply is going bad.

[MattHelm]

Originally Posted by bling_bling_vr6

This is the the HDPVR section of my .properties file:
...

Thank you for the quick response!!!!

[jperquin]

Originally Posted by KeithAbbott

Maybe your power supply is going bad.

+1 on the power supply. I was on a wild goose chase for a while too. Changed out the power supply for a really fat one (I believe it is a generic laptop adapter), and all is good.

[freewheeling]

I had 5 instances of the HDPVR settings and all but 1 were set to -1 for those settings. I changed the one that wasn't set to -1 to the recommended settings and everything works fine. Hauppauge has replacement power supplies for HDPVR for about $12.00 I think. Any 5V @ 2.0 Amps will work though.

[davidk21770]

Originally Posted by wbarber69

My bad I meant to also mention that you need to take these values that the program gives you for hue, contrast, etc. And plug them into the sage.properties file where it shows your hdpvr settings

I just "upgraded" from XP to 8.1 and this saved me a lot of time. The default values have changed with the 8.1 drivers that I was using and I couldn't figure out where to set them! I found the defaults by loading the HDPVR into graph edit and looking at the properties page, but every time that sage loaded, it changed them back...

(New values appear to be: Brightness 128, Contrast 64, Hue 0, Saturation 64, Sharpness 128).
[Edit: I had to set hue to 128 in SageTV to get 0 on it's properties page in graph edit.]

Thanks!