#9813 NORM 1.5-sof: Camera does not work correctly in Etoys

[Zarro Boogs per Child]

#9813: Camera does not work correctly in Etoys
--------------------------------------+-------------------------------------
           Reporter:  bert            |       Owner:  bert                             
               Type:  defect          |      Status:  new                              
           Priority:  normal          |   Milestone:  1.5-software-final               
          Component:  etoys-activity  |     Version:  Development build as of this date
         Resolution:                  |    Keywords:  os54 os56                        
        Next_action:  diagnose        |    Verified:  0                                
Deployment_affected:                  |   Blockedby:                                   
           Blocking:                  |  
--------------------------------------+-------------------------------------
Changes (by bert):

  * keywords:  os54 => os54 os56


Comment:

 Tested again in os56.

 When turning on the machine and opening the camera in Etoys, I get a fully
 magenta image with white random dots on it.

 But after a little while, this time I do see parts of the camera image.
 Etoys uses the camera's "preferred mode" by default, which indeed is YUYV.
 And that decoding seems to work, as I can see parts of the picture.

 What it looks like is that the picture is filled in from the top but stops
 midway. Sometimes 50 lines get transferred, sometimes less, or more, and
 sometimes it starts in the middle of the frame not the top. When waiting
 long enough, occasionally even a full frame gets drawn.

 All this does not happen fluidly but there is maybe 30 seconds of
 inactivity then a burst of partial updates at maybe 3 fps.

 It looks to me like a synchronization issue, as if a source buffer is
 modified while copying it.

 Interestingly, that partially updated image *stays the same* when
 restarting Etoys. To me this would suggest that the garbled frame is
 actually already garbled in the driver, not on the Squeak side.

 There is a warning in the Etoys log about "VIDIOCMCAPTURE1: Invalid
 argument". Not sure what that signifies.

 I saw the same "magenta plus white noise" image very briefly when starting
 Record, but it gets overdrawn with the right frame contents afterwards. A
 single line of it remains visible at the bottom of the Record preview.

 When switching back to Etoys after trying Record, the last Record frame
 appears to show in Etoys. It looks stretched vertically, possibly because
 Etoys uses a 320x240 size by default. After waiting some time this clean
 frame gets overwritten with the partial updates again as before.

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