On Sunday 28 May 2006 18:05, Harry Orenstein wrote:
> On Sunday 28 May 2006 4:23 am, Hans Verkuil wrote:
>
> <snip>
>
> > Actually, I wasn't aware of this. Please make sure you have the
> > correct encoding firmware
> > (http://www.ivtvdriver.org/index.php/Firmware), and then please
> > post the INIT IVTV messages from dmesg, and the messages in dmesg
> > that you (probably) get when trying to switch channels.
> >
> > Preferably test this without MythTV. Switch channels once without a
> > capture in progress, and once with a capture in progress. These two
> > cases are handled slightly differently so this is useful
> > information for me to have.
> >
> > Thanks,
> >
> > Hans
> >
> > _______________________________________________
> > ivtv-devel mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
> Hans,
>
> Thanks for the reply! Attached are my INIT IVTV messages and a
> section of my mythbackend.log with verbose messages. There were no
> problems changing channels using ivtv-tune, either while capturing or
> not. The problem seems to be specific to mythtv. I know that the
> ioctls changed at some point and that myth uses a ivtv-myth.h of its
> own. Could this just be a problem on my part that I need to be
> running a more current myth? The reason I thought it might be an
> ivtv problem is that I saw messages from others that this was
> specific to 0.4.5 (and my own downgrading to 0.4.4 solved my
> problem). There's nothing I can see in the changelog that would
> indicate that something changed from 0.4.4 to 0.4.5 that would cause
> this, and yet...
>
> Let me know if there are any other tests I can do to help track down
> the problem (if there really is a problem).
Just to be sure, check the MythTV settings whether all the correct
inputs and devices are configured (esp. inputs changes in the past, so
make sure that's OK). If that doesn't help, then upgrade to the latest
MythTV. If that still doesn't solve anything, then someone will have to
go into the MythTV code and see what is going on.
Since I don't use MythTV myself and also don't have the time to look
into it anyway it will be up to other volunteers to investigate. If the
trace ends up in the driver, then I'm happy to try and fix it. Sorry
about that.
Regards,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
