Hi Devin,
Devin Heitmueller wrote:
Try an actual TV and see if it can receive the channel.
That is my next step. Either that or live without the channels.
This would indeed be an interesting data point (if your TV can receive
the channel but the HVR-1600 cannot).
OK, I hope to try it on Monday.
Generally speaking, my goal is for the Linux driver to work "as well
as WIndows". I do this because I know the Hauppauge developers who
work full-time on the Windows drivers put a hell of a lot more time
into tuning/optimization of both the hardware and software, so I
basically take for granted that if it doesn't work under Windows, it's
not going to work at all. There are always exceptions to the rule, of
course.
Yes, makes perfect sense and it's the reason I gave up last Spring.
One thing that might also be interesting to try: hack a channels.conf
file so that it has the frequencies in question, and run azap against
the frequency. Then see if it shows a lock. This might be some weird
case where you are getting a signal lock but the video/audio PIDs are
not being setup properly, or some weird edge-case where scan is
failing when it shouldn't. You can paste the output of azap in an
email if you want me to take a look.
I've thought about that, but I have no idea what values to try for the video &
audio pids. For the few channels I have, the video pids range from 64 to 7217 and
the audio pids are video pid +1. It would be nice if silicondust.com's web site had
that info, but it doesn't. Can you suggest some reasonable values to start with?
Thanks,
Helen
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
