Ruud Huynen wrote:
Ruud Huynen wrote:
Around release 0.3.7f (algorithm) modifications were made to egalize
the volume difference between 350 and 500.
I never tried those releases after 0.3.7b(or d).
With the tagged 0.4.0 release I notice a big difference. The 350 is
twice as load as the 500.
I lived with the older 0.3.7 release, but I never noticed such a big
volume difference as with the 0.4.0 release.
I remember them well, since I made them :)
You're saying if you record the same content on both cards
simultaneously at the same volume settings (check ivtvctl -d (dev)
-Y), you get a different volume for each card? The code is there to
map them both to the same range, and in my objective testing they
were the same in recorded files. This is on a pvr-150, but it should
be the same on a 500.
I noticed a difference:
[EMAIL PROTECTED]:/usr/local/bin> ./ivtvctl -d /dev/video0 -Y (PVR350)
ioctl: VIDIOC_QUERYCTRL
Brightness = 127
Contrast = 63
Saturation = 63
Hue = 0
Volume = 62225
Mute = 0
[EMAIL PROTECTED]:/usr/local/bin> ./ivtvctl -d /dev/video1 -Y (PVR500-1)
ioctl: VIDIOC_QUERYCTRL
Brightness = 127
Contrast = 63
Saturation = 63
Hue = 0
Volume = 61952
Mute = 0
[EMAIL PROTECTED]:/usr/local/bin> ./ivtvctl -d /dev/video2 -Y (PVR500-2)
ioctl: VIDIOC_QUERYCTRL
Brightness = 127
Contrast = 63
Saturation = 63
Hue = 0
Volume = 61952
Mute = 0
I don't set the volume. Is this the calculated volume from the driver,
where the value can be different to receive the same volume.
Do I have to set them to the same value.
Yeah this appears to be set to 95% volume on all tuners. The
PVR150/500 code rounds down to the nearest 512 boundary so trying to set
it to 62225 would result in it coming out 61952. Those /should/
theoretically come out with the same volume. I wonder why your 350 is
so loud :/
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel