On Thu, Jun 10, 2010 at 07:41:42PM +0000, Paulus, Mark G wrote:
>
>
> --
> Mark Paulus
> 2424 Garden of the Gods Rd | Phone: v622-5578 / 719-535-5578
> 0419/117 - LEC Access ; C1-1207 | FAX: 719-535-7060
> Colorado Springs, CO 80919
> AIM : mgpaulus1 / sametime : mark.paulus@vzb.verizon.com
> > -----Original Message-----
> > From: ivtv-devel-bounces@ivtvdriver.org [mailto:ivtv-devel-
> > bounces@ivtvdriver.org] On Behalf Of D. Hugh Redelmeier
> > Sent: Thursday, June 10, 2010 1:25 PM
> > To: ivtv-devel@ivtvdriver.org
> > Subject: [ivtv-devel] CX18: ffmpeg -i says: Seems stream 0 codec frame
> > rate differs from container frame rate: 59.94 (60000/1001) -> 29.97
> > (30000/1001)
> >
> > When I record an analogue signal using my Hauppauge HVR-1600, and pass
> > it to ffmped, I get this diagnostic.
> >
> > Seems stream 0 codec frame rate differs from container frame rate:
> > 59.94 (60000/1001) -> 29.97 (30000/1001)
> >
> > I've seen this in lots of postings (including my own) but have not
> seen
> > a reasonable explanation of why this happens. One reply I got
> > suggested that the container has the field rate while the stream has
> > the frame rate.
> >
> > I'm running Ubuntu 10.4 AMD64 with Mythbuntu packages. I'm using a
> > driver fetched from <http://linuxtv.org/hg/v4l-dvb> on June 6 (but it
> > has happened with all the previous versions that I've fetched).
> >
> > I used this as a guide to setting up the HVR-1600 in MythTV:
> > <http://www.mythtv.org/wiki/Hauppauge_HVR-1600>
> > The firmware in /lib/firmware/ matches a freshly fetched set from
> > <http://linuxtv.org/downloads/firmware/>
> >
> > Originally I reported this problem the the MythTV Users' list. But
> now
> > I've tested with a simple dd from the tuner card:
> > dd if=/dev/video1 of=junk.mpeg
> > I interrupted this after a little bit and then examined the result.
> > ffmpeg gives the diagnostic on that file. (The card was initialized by
> > previous MythTV recording activities.)
> >
> > Googling through the ffmpeg list, it seems that this comes up once in
> a
> > while. They don't seem to answer people's questions on this anymore.
> > But this message seems to make it clear that they would consider this
> a
> > bug in whatever created the file.
> >
> > <http://lists.mplayerhq.hu/pipermail/ffmpeg-user/2008-
> > December/018095.html>
> >
> > The video container specifies a framerate, as does the video
> > stream itself. In some cases, usually caused by badly written
> > encoding programs, the two can disagree. When this happens,
> > ffmpeg is obviously forced to believe one and not the other.
> >
> > Is ffmpeg wrong? I don't want to spend the Swiss Francs to buy the
> > relevant standards to figure out who is right.
> >
> > Is MythTV setting up the HVR-1600 incorrectly, causing this problem?
> >
> > Is the cx18 driver wrong?
> >
> > Is the firmware wrong?
> >
> > Futher details of my system here:
> > <http://www.mythtv.org/pipermail/mythtv-users/2010-June/290280.html>
> > <http://www.mythtv.org/pipermail/mythtv-users/2010-May/288527.html>
>
> What about installing M$ Windows on that machine, or moving the card
> to a M$ Windows machine, and make a recording there? Then you can run
> ffmpeg against that file and see if it's the card or firmware.
I think this is because the MPEG2 is interlaced and so technically
holding 60 half frames but displayed as 30~ whole frames per second.
Actually ffmpeg will give you this error from files it has created
itself, like asf/wmv1/wmav2 do this.
Newer versions of ffmpeg don't output the message for the MPEG2 produced
by the cx3241X chips, older ffmpeg's didn't always calculate this
correctly because of the interlaced nature of the MPEG.
Thanks,
Chris
>
> >
> > _______________________________________________
> > ivtv-devel mailing list
> > ivtv-devel@ivtvdriver.org
> > http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
--
Chris Kennedy
c@groovy.org
_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
> --
> Mark Paulus
> 2424 Garden of the Gods Rd | Phone: v622-5578 / 719-535-5578
> 0419/117 - LEC Access ; C1-1207 | FAX: 719-535-7060
> Colorado Springs, CO 80919
> AIM : mgpaulus1 / sametime : mark.paulus@vzb.verizon.com
> > -----Original Message-----
> > From: ivtv-devel-bounces@ivtvdriver.org [mailto:ivtv-devel-
> > bounces@ivtvdriver.org] On Behalf Of D. Hugh Redelmeier
> > Sent: Thursday, June 10, 2010 1:25 PM
> > To: ivtv-devel@ivtvdriver.org
> > Subject: [ivtv-devel] CX18: ffmpeg -i says: Seems stream 0 codec frame
> > rate differs from container frame rate: 59.94 (60000/1001) -> 29.97
> > (30000/1001)
> >
> > When I record an analogue signal using my Hauppauge HVR-1600, and pass
> > it to ffmped, I get this diagnostic.
> >
> > Seems stream 0 codec frame rate differs from container frame rate:
> > 59.94 (60000/1001) -> 29.97 (30000/1001)
> >
> > I've seen this in lots of postings (including my own) but have not
> seen
> > a reasonable explanation of why this happens. One reply I got
> > suggested that the container has the field rate while the stream has
> > the frame rate.
> >
> > I'm running Ubuntu 10.4 AMD64 with Mythbuntu packages. I'm using a
> > driver fetched from <http://linuxtv.org/hg/v4l-dvb> on June 6 (but it
> > has happened with all the previous versions that I've fetched).
> >
> > I used this as a guide to setting up the HVR-1600 in MythTV:
> > <http://www.mythtv.org/wiki/Hauppauge_HVR-1600>
> > The firmware in /lib/firmware/ matches a freshly fetched set from
> > <http://linuxtv.org/downloads/firmware/>
> >
> > Originally I reported this problem the the MythTV Users' list. But
> now
> > I've tested with a simple dd from the tuner card:
> > dd if=/dev/video1 of=junk.mpeg
> > I interrupted this after a little bit and then examined the result.
> > ffmpeg gives the diagnostic on that file. (The card was initialized by
> > previous MythTV recording activities.)
> >
> > Googling through the ffmpeg list, it seems that this comes up once in
> a
> > while. They don't seem to answer people's questions on this anymore.
> > But this message seems to make it clear that they would consider this
> a
> > bug in whatever created the file.
> >
> > <http://lists.mplayerhq.hu/pipermail/ffmpeg-user/2008-
> > December/018095.html>
> >
> > The video container specifies a framerate, as does the video
> > stream itself. In some cases, usually caused by badly written
> > encoding programs, the two can disagree. When this happens,
> > ffmpeg is obviously forced to believe one and not the other.
> >
> > Is ffmpeg wrong? I don't want to spend the Swiss Francs to buy the
> > relevant standards to figure out who is right.
> >
> > Is MythTV setting up the HVR-1600 incorrectly, causing this problem?
> >
> > Is the cx18 driver wrong?
> >
> > Is the firmware wrong?
> >
> > Futher details of my system here:
> > <http://www.mythtv.org/pipermail/mythtv-users/2010-June/290280.html>
> > <http://www.mythtv.org/pipermail/mythtv-users/2010-May/288527.html>
>
> What about installing M$ Windows on that machine, or moving the card
> to a M$ Windows machine, and make a recording there? Then you can run
> ffmpeg against that file and see if it's the card or firmware.
I think this is because the MPEG2 is interlaced and so technically
holding 60 half frames but displayed as 30~ whole frames per second.
Actually ffmpeg will give you this error from files it has created
itself, like asf/wmv1/wmav2 do this.
Newer versions of ffmpeg don't output the message for the MPEG2 produced
by the cx3241X chips, older ffmpeg's didn't always calculate this
correctly because of the interlaced nature of the MPEG.
Thanks,
Chris
>
> >
> > _______________________________________________
> > ivtv-devel mailing list
> > ivtv-devel@ivtvdriver.org
> > http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
--
Chris Kennedy
c@groovy.org
_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel