[mythtv-commits] Ticket #1660: database updates in *recorder.cpp cause dropped data

[MythTV]

#1660: database updates in *recorder.cpp cause dropped data
----------------------------------------+-----------------------------------
 Reporter:  ajlill at ajlc.waterloo.on.ca  |        Owner:  cpinkham
     Type:  defect                      |       Status:  reopened
 Priority:  minor                       |    Milestone:  0.21    
Component:  mythtv                      |      Version:  head    
 Severity:  medium                      |   Resolution:          
----------------------------------------+-----------------------------------
Changes (by ylee at pobox.com):

  * status:  closed => reopened
  * resolution:  fixed =>


Comment:

 I'd like to report my experiences with the above patches. Bottom line: I
 hope ajlill's asyncdb patch stays in the code.

 I have two FireWire cable boxes and an ATSC capture card, and routinely
 simultaneously record from all three sources. I've been using the asyncdb
 patch (to be accurate,
 [http://svn.mythtv.org/trac/attachment/ticket/1660/asyncdb.2.patch
 asyncdb.2.patch with the typo correction I submitted]) on top of my
 0.20-fixes setup for several months now. With it, 60-minute FireWire HD
 recordings typically come in at 59:55 to 59:59; i.e., exactly as long as
 they should, barring startup times.

 Since the ATrpms 0.20-fixes package now incorporates r12919 I tried
 building it without the asyncdb patch. Not so much luck here; the same
 60-minute FireWire recordings came in about 30-250 seconds short, and
 during replay I saw frequent MPEG errors from dropped frames (slight skips
 in the video or the image blurring for a moment). (Interestingly, ATSC HD
 recordings were seemingly unaffected.)

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