On Monday 29 January 2007 10:40, Hans Verkuil wrote:
> > On 1/29/07, Hans Verkuil <[EMAIL PROTECTED]> wrote:
> >> Hi all,
> >>
> >> I had hoped to make a release candidate this weekend, but a nasty
> >> bug was found which took me the whole Sunday to track down and
> >> fix. While testing that bug fix I may have found another bug, so
> >> I'll have to do more testing before I can make a release
> >> candidate.
> >>
> >> However, for all cards except the pvr350 it looks like it should
> >> work fine, so please test the current trunk! Also test with MythTV
> >> with VBI: it should work fine now!
> >
> > First test results:
> > 1. This module is a little pickier about the firmware, it won't
> > accept the greatest and latest pvr-500 fw from hauppauge (based on
> > size), too bad, I had good results with it. :/
>
> Read the README notes: it's the same firmware, just without the
> garbage at the end.
>
> > 2. It loads ok, and works.
> > 3. Without vbi in mythtv tested recording 2 streams at the same
> > time, this results in occasional glitches again, and they seem to
> > be more prevalent than the old 0.9.2 (svn) module.
> > 4. With vbi on, there are occasional freezes, glitches and audio
> > glitches now.
>
> Do you see any messages in the kernel log?
A follow-up: the latest trunk version has a new tool: ps-analyzer. If
you have recordings with glitches then please run this tool over the
recording (ps-analyzer foo.mpg). It gives a full dump of all the pack
headers in the mpeg stream. I recommend using something like:
ps-analyzer foo.mpg | grep -2 Unknown
The main feature is that when the file has a corrupt structure, then the
analyzer reports 'Unknown packet' messages and/or stops with
an 'missing pack marker' error.
Note that the message 'broken stream' is not an error, it just means
that the file ended in the middle of a MPEG packet.
Basically if ps-analyzer doesn't report any problems in the recording,
then I'd say the recording is correct and something else is going on.
Regards,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
