Hans Verkuil wrote:
> On Wednesday 08 March 2006 19:26, Bob Cottingham wrote:
>> I have a problem with my PVR-150 having low saturation.
>
> It works perfectly fine for me, so that makes it harder to track down.
>
> But first check that MythTV is not involved by doing the following test
> (done with ivtv-0.4.3, also please supply the START INIT IVTV-END INIT
> IVTV log):

Here is the init msg for the PVR-250s:
http://bobnvic.com/pvr250init.txt

Here is the init message for the PVR-150:
http://bobnvic.com/pvr150init.txt

> Run ivtvctl -Y for the pvr150 and the pvr250 and check that brightness =
> 128 and contrast and saturation are both 64. Hue should be 0. There
> should be no difference between the pvr150 and pvr250 regarding these
> values.

The ivtvctl -Y command gave the same result for the PVR-250s and the
PVR-150, however brightness was set to 127 for both and contrast and
saturation were set to 63 with hue set to 0.

> Now tune both the pvr150 and 250 to the same channel and capture a bit.
> Compare the two mpegs. If they clearly differ (some differences are
> normal, for me the pvr150 is actually somewhat more saturated than the
> pvr350) then I'd like to have the output of ivtvctl --log-status for both
> the pvr250 and 150 while both are capturing, and either the mpegs
> themselves or a screenshot taken from these mpegs.

The PVR-150 capture was clearly under-saturated compared to the PVR-250. 
Here is the ivtvctl --log-status for the PVR-250:
   [4319587.028000] ivtv0: =================  START STATUS CARD #0 
=================
   [4319587.028000] saa7115 0-0021: Audio frequency: 48 kHz
   [4319587.030000] saa7115 0-0021: Video signal:    broadcast/DVD
   [4319587.030000] saa7115 0-0021: Frequency:       60Hz
   [4319587.030000] saa7115 0-0021: Detected format: NTSC
   [4319587.030000] ivtv0: ==================  END STATUS CARD #0 
==================

Here is the ivtvctl --log-status for the PVR-150:
   [4437938.571000] ivtv0: =================  START STATUS CARD #0 
=================
   [4437938.579000] cx25840 0-0044: Video signal:              present
   [4437938.579000] cx25840 0-0044: Detected format:           NTSC-M
   [4437938.579000] cx25840 0-0044: Detected audio mode:       forced mode
   [4437938.579000] cx25840 0-0044: Detected audio standard:   forced
audio standard
   [4437938.579000] cx25840 0-0044: Audio muted:               no
   [4437938.579000] cx25840 0-0044: Audio microcontroller:     running
   [4437938.579000] cx25840 0-0044: Configured audio standard: BTSC
   [4437938.579000] cx25840 0-0044: Configured audio mode:     undefined
   [4437938.579000] cx25840 0-0044: Specified standard:        NTSC-M
   [4437938.579000] cx25840 0-0044: Specified input:           Tuner
   [4437938.579000] cx25840 0-0044: Specified audio input:     Tuner
   [4437938.579000] cx25840 0-0044: Specified audioclock freq: 48 kHz
   [4437938.579000] cx25840 0-0044: Preferred audio mode:      stereo
   [4437938.579000] cx25840 0-0044: Selected 65 MHz format:    system DK
   [4437938.579000] cx25840 0-0044: Selected 45 MHz format:    chroma
   [4437938.579000] wm8775 0-001b: Input: default
   [4437938.579000] ivtv0: ==================  END STATUS CARD #0 
==================

These may not be the best examples. I had thought that a cartoon would
best show off saturation differences, but that doesn't actually seem to be
true as animated shows probably have more saturation to begin with. I may
try some other captures that better reflect what I'm seeing, but these are
already done.

Here is a link to the screenshot for the video capture from the PVR-250:
http://bobnvic.com/pvr250capture.jpg

Here is a link to a screenshot from the video capture from the PVR-150:
http://bobnvic.com/pvr150capture.jpg

I can also make the video available if needed.

> I'd also appreciate it if people with a pvr150/500 and a pvr250/350 in
> NTSC country can do a similar comparison and post the result. All I
> need to know is whether there are major saturation differences and the
> tveeprom messages in the kernel log of the pvr150/500.

Thanks for looking at this. Please let me know if you need anything else.

Bob C




_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to