#10045 BLOC 1.5-sof: XO-1.5 Record audio/video are out of sync with each other

[Zarro Boogs per Child]

#10045: XO-1.5 Record audio/video are out of sync with each other
---------------------------------------+------------------------------------
           Reporter:  wad              |       Owner:  dsd                              
               Type:  defect           |      Status:  new                              
           Priority:  blocker          |   Milestone:  1.5-software-update              
          Component:  record-activity  |     Version:  Development build as of this date
         Resolution:                   |    Keywords:  camera record XO-1.5             
        Next_action:  diagnose         |    Verified:  0                                
Deployment_affected:                   |   Blockedby:                                   
           Blocking:                   |  
---------------------------------------+------------------------------------

Comment(by mikus):

 Running Record-67 on os121.  With unmodified glive.py, the audio and video
 appear to live on separate planets (sync is too much to ask for):  On
 playback, managed once to hear one second of audio when recording in
 'High' quality (and again managed once on playback to hear one second of
 audio when recording in 'Low' quality).  On playback after recoring in
 'Best' quality, managed to hear audio (appeared to be at normal speed) -
 but the playback started with something like the 25th second of what I was
 trying to record (the whole beginning of the "audio track" was left out).

 Added after writing original comment content:[[BR]]I find myself UNABLE to
 test Record on the XO-1.5.  There is too much variation from run to run,
 and too much simply not working.  In particular, the function deteriorated
 rapidly from run to run (even when I erased
 /home/olpc/.sugar/default/org.laptop.RecordActivity between runs).
 Although the clip itself showed motion on playback, the picture on screen
 during recording (on later runs) was static.  Eventually, when I clicked
 on the circle to stop recording, the activity was no longer able to "save"
 the clip it had been making.  Whatever is wrong, my unsubstantiated
 opinion is that it is much more fundamental than "playing with
 parmameters" can cure.


 [[BR]]Could not make change (1) -- jnettlet appears to have a different
 version of glive.py than I do.  Made a stab at where to insert "latency-
 time=100", the picture shown on screen during "recording" never changed,
 and the activity never "saved" the clip it was supposed to have created.
 [I tested change (1) last - it may have been the general deterioration of
 the Activity that was a t fault. not my stab at change (1)].

 This is a subjective impression - change (2) appeared to make "making a
 video recording" better behaved -- but I have no *evidence* whatsoever for
 that.  Note, however, that this change is in the playback routine, not in
 the record routine -- so I was seeing the same antics as with the
 unmodified glive.py -- audio output only a fragment of what should have
 been there; video playback appeared "frantic" (speeded up?) in comparison
 to what should have been there.

 Change (3) did not appear to have affected anything.

 [I only did one change at a time.]

 mikus

-- 
Ticket URL: <http://dev.laptop.org/ticket/10045#comment:16>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system