#10008 NORM Not Tri: Record Activity has problems

[Zarro Boogs per Child]

#10008: Record Activity has problems
------------------------------------+---------------------------------------
           Reporter:  mikus         |       Owner:                                   
               Type:  defect        |      Status:  closed                           
           Priority:  normal        |   Milestone:  Not Triaged                      
          Component:  not assigned  |     Version:  Development build as of this date
         Resolution:  duplicate     |    Keywords:                                   
        Next_action:  never set     |    Verified:  0                                
Deployment_affected:                |   Blockedby:                                   
           Blocking:                |  
------------------------------------+---------------------------------------
Changes (by Quozl):

  * status:  new => closed
  * resolution:  => duplicate


Comment:

 Thank you for your concern.  The Record activity at Sugar Labs certainly
 does need someone to maintain it.  The last significant code change in the
 master branch was in June last year.

 However, some of what you say is not caused by Record activity, but only
 demonstrated by it.

 All the comparisons I've done between GStreamer manual invocation and
 Record have shown the Record image quality issues are based on the camera
 or the driver, and not on Record at all.

 To do comparison between software drivers for camera data transfer,
 compare OpenFirmware against Linux; the OpenFirmware command is:

 {{{
 test /camera
 }}}

 So I'm closing this ticket as a duplicate of a couple of others, and
 moving the critical observations there:

  * camera image quality is covered by #9853, and closed ticket #9804
 included a change to programmed brightness levels in the !OpenFirmware
 camera test, therefore I presume that we're just waiting for #9853
 brightness changes to be done in kernel,

  * #9949 covers smoothness of audio recording, and a symptom is reported
 there that relates to not saving audio; because the audio was not given
 enough time to get started given the high CPU demand of the unaccelerated
 video stream ... to correct for that in your testing allow a longer time
 to elapse before trying to stop the recording.

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