[mythtv-commits] Ticket #799: DTV recordings sometimes show doubled recording length

MythTV mythtv at cvs.mythtv.org
Wed Nov 14 19:41:37 UTC 2007


#799: DTV recordings sometimes show doubled recording length
---------------------+------------------------------------------------------
 Reporter:  danielk  |        Owner:  janne   
     Type:  defect   |       Status:  assigned
 Priority:  major    |    Milestone:  0.21    
Component:  mythtv   |      Version:  head    
 Severity:  high     |   Resolution:          
  Mlocked:  0        |  
---------------------+------------------------------------------------------

Comment(by Tom Dexter <digitalaudiorock at hotmail.com>):

 Replying to [comment:33 jonner at teegra.net]:
 > I have some recordings that show double the correct total time and
 otherwise behave fine. I also have more problematic recordings that
 display incorrect total time. Though that incorrect time is usually double
 of what it should be, it is sometimes even greater than double.
 >
 > Since I don't know what's going on inside, I can't say what the precise
 relationships are between these behaviors. I may be seeing the same bug as
 ylee at pobox.com on some recordings and an entirely different bug on others.
 My guess is that they're somehow related.

 Actually I don't think they are.  The temporary display of doubled length
 of a recording (when recording completes while you're watching the
 recording) is caused by the length reported by the recorder, which doesn't
 know the frame rate at all.  If you see a doubled length when playing it
 back later, that doesn't involve the recorder at all...and I've never seen
 any such thing myself.  I believe that calculates the length based on the
 frame rate from the file itself and data in the recordedseek table.

 The only 'pertinent' incorrect lengths I ever see are one hour shows that
 display as around 51 minutes.  For me these are always dramas recorded off
 of NBC HD.  They are apparently using different frame rates for
 commercials and myth as yet does not handle that...since it assumes one
 frame rate, it causes that much of an error...but certainly never doubled
 or anything like that.  By the way...I believe that this is one of the
 reasons that nobody has addressed the issue of the recorder not knowing
 the frame rate, as the handling of multiple frame rates is a much more
 complex issue that's yet to be hashed out.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/799#comment:34>
MythTV <http://svn.mythtv.org/trac>
MythTV


More information about the mythtv-commits mailing list