On do, 2008-01-17 at 23:21 +0100, Wessel de Haas wrote: > -Hauppauge PVR-500 with Samsung tuners > > > -If I do: ivtv-tune -teurope-west -c22 /dev/video0 > I get: /dev/video0: 479.250 MHz > -And if I do: ivtv-tune -teurope-west -c22 /dev/video1 > I also get: /dev/video0: 479.250 MHz > i.e. it's as if I only have one tuner, although 2 tuners seem to be > recognised by ivtv (see below).
Try: ivtv-tune -teurope-west -c22 -d /dev/video1 (notice the extra -d) > -When I installed MythTV, I can only select: tuner1, not tuner0 as is > indicated in most how-to's / installation instructions for MythTV. Correct, the PVR-500 appears as 2 pvr-150's each with only 1 tuner. > -The picture quality issues appear both in MythTV and in mplayer > /dev/video0, cat /dev/video1 > test.mpg etc. > -I've seen many entries on various webfora on this card and esp. on > difficulties with the Samsung tuners (so much for doing your research > before you buy...), but haven't found any tips there that have > improved my situation: The Samsung tuners are notorious for bad quality, I got rid of mine. > -Initially I ran with the ivtv version that came with Suse 10.3 > (0.10.xxx), later I removed the 'ivtv*' packages using Yast and > compiled version 1.0.3 from source (as this was the recommended > version for my kernel on the wiki). This made no difference to the > performance of the card. I've also upgraded the firmware from the > version that came with Suse 10.3 to the latest. The 1.0.x versions of ivtv only includes the ivtv-fb and the saa717x module plus the userland tools like ivtv-tune. The 0.10.x is for kernels 2.6.18 through 2.6.22 and this does include all from 1.0.x and ivtv. > -I've switched inputs to the Composite input and sampled a bit of > footage from my camcorder, which resulted in an excellent picture. I > believe this proves that it's really the tuner and not the MPEG2 > encoder or anything. Yep, the Samsung tuners are to blame. > Any help would be greatly appreciated, AFAIK there is no solution for the Samsung tuner quality issues. The developers have tried various fixes but none with satisfactory results. The ivtv init you posted look fine to me. Greets Sander _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
