Opened 14 years ago
Closed 13 years ago
#1911 closed defect (fixed)
OLPC-Measure activity- Recording duration is not accurate
Reported by: | Ruwan F'do | Owned by: | gpollice |
---|---|---|---|
Priority: | High | Milestone: | Unspecified |
Component: | Measure | Version: | |
Severity: | Major | Keywords: | |
Cc: | Distribution/OS: | OLPC | |
Bug Status: | Resolved |
Description
Description
Time durations in the drop down list is not matching with the actual result. It doesn’t stop at the given point.
Precondition
- Power on OLPC
- Wait for the activity ring/ activity Icons (Desktop).
- Open the measure activity
- Go to the sound tab
- Select 30second on drop down list
- Click the record button
Actual Result
Recording doesn’t stop at the given time period.
Expected Result
Recording should stop at the given time period.
Tested Environment
OS Build: 802b5
Machine Type: XO1
Firmware: Q2E42
Security Disable: Yes
Sugar Version: 0.82.1
Activity version: 27
Change History (7)
comment:1 Changed 14 years ago by Ruwan F'do
- Summary changed from OLPC-Measure activity- time durations don’t stop at the given point to OLPC-Measure activity- Recording duration is not accurate
comment:2 Changed 14 years ago by sascha_silbe
- Component changed from sugar to Measure
- Distribution/OS changed from Unspecified to OLPC
- Owner changed from tomeu to walter
- Priority changed from High to Unspecified by Maintainer
- Version 0.82.x deleted
comment:3 Changed 14 years ago by walter
- Priority changed from Unspecified by Maintainer to High
comment:4 Changed 13 years ago by gpollice
- Bug Status changed from New to Resolved
- Owner changed from walter to gpollice
- Status changed from new to assigned
comment:5 Changed 13 years ago by ganderson
We reproduced the problem on version 29 and version 30. As of version 30 on the XO1.5, it seems to be fixed.
comment:6 Changed 13 years ago by walter
Please see http://bugs.sugarlabs.org/attachment/ticket/1070/Measure-30.xo (the latest version of Version 30). Should be able to test it on the XO 1.0 too.
comment:7 Changed 13 years ago by walter
- Resolution set to fixed
- Status changed from assigned to closed
dup of #1905?
Note: See
TracTickets for help on using
tickets.
This has been fixed. There are a couple of issues here. First, the assumption that selecting a time in the combo box means that Measure will sample for that period of time and stop is a bad assumption. Selecting a time actually means that a sample will be taken continually at the end of the duration, until the user clicks the stop recording button. However, if the Now is selected, it means take a single snapshot when the Record button is pressed.
We changed the text on the combo box items to be more clear and added more descriptive tool tips to the record button. We also cleaned up the audio sampling toolbar.
Finally, we noticed that the time was not correct, depending upon the processor so we added a timer thread to determine when to log the sample.