<div class="gmail_quote">On Mon, Aug 29, 2011 at 1:20 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 08/29/2011 11:26 AM, Jerry Rubinow wrote:<br>
>> On 29/08/2011 12:56 AM, Jerry Rubinow wrote:<br>
</div>>>> On Sat, Aug 27, 2011 at 12:28 AM, Jerry Rubinow wrote:<br>
<div class="im">>>><br>
>>>> On Fri, Aug 26, 2011 at 11:28 PM, Jerry Rubinow wrote:<br>
>>>>> I just upgraded the firmware on my HD-PVR from version 0x12<br>
>>>>> May 7, 2009 to the latest from the Hauppauge web site, 0x17<br>
>>>>> July 27, 2011. Now all recordings from the HD-PVR are way<br>
>>>>> oversaturated. Catting /dev/video0 and playing the file with<br>
>>>>> vlc yields the same result. According to v4l2-ctl -l, the<br>
>>>>> settings are all at defaults.<br>
</div><div class="im">>>>> I tried adjusting the brightness and contrast in the channel<br>
>>>> change script, via:<br>
>>>><br>
>>>> /usr/bin/v4l2-ctl --device=/dev/video0 --set-ctrl=brightness=100<br>
</div><div class="im">>>> It seems like Myth must be setting the hd-pvr to a default state after<br>
>>> running the channel change script.<br>
</div><div class="im">> That's an excellent kludge, thanks for the idea. I'll try that out tonight<br>
> and hopefully that'll last until I'm able to find older firmware or<br>
> otherwise figure out why this started happening.<br>
><br>
> Janne, Jarod, or anyone who's familiar with the driver, any ideas? Is there<br>
> a potential kernel incompatibility with the firmware? I wanted to save<br>
> doing a full system update as a last resort since things are otherwise<br>
> pretty stable.<br>
<br>
</div>I'm definitely not "anyone who's familiar with the driver", but I will<br>
say that for other analog encoders (such as the IVTV devices), MythTV<br>
always sets the contrast, brightness, color (or colour, as the case may<br>
be), and hue according to the values you specified--which all start at<br>
default values.<br>
<br>
You can change the default values by using G in Live TV playback to set<br>
the capture card picture controls. Note that this will not work on a<br>
digital capture device (DVB/ATSC/QAM/Firewire/...) because those aren't<br>
actually recording the video, but just writing the provided recorded<br>
video stream.<br>
<br>
Using G to set the capture card picture controls differs from using F to<br>
set the playback picture controls. F is used in Live TV or recording<br>
playback to change the contrast, brightness, color, and hue at<br>
playback--and affects playback of all recordings and videos, regardless<br>
of channel and capture device. Note, also, there's a per-channel<br>
picture control available, in which you can specify contrast,<br>
brightness, color, and hue for individual channels using the<br>
mythtv-setup or MythWeb channel editor. You also don't want<br>
this--especially if you have, for example, an IVTV card recording from<br>
the same channel.<br>
<br>
I don't know if this applied to HD-PVR, but before you go and set up a<br>
hack, try G--and then tell all the others who are using the hacks if it<br>
works properly for the HD-PVR. :)<br></blockquote><div><br></div><div>Mike, thanks for that, I will try it tonight. Are the settings accessed by G saved in the database, or do they just apply to the current mythbackend session?</div>
<div><br></div><div>-Jerry</div></div>