Ticket #1648 (closed defect: fixed)

Opened 2 years ago

Last modified 22 months ago

Measure-29 on XO 1.5

Reported by: tabitha Owned by: walter
Priority: Normal Milestone: 0.90
Component: Measure Version: 0.84.x
Severity: Unspecified Keywords:
Cc: Distribution/OS: OLPC
Bug Status: Assigned

Description

Sound slider when moved past approx 90% on the range of the oscilloscope goes erratic. Math bug in display? It goes vertical and spikey and off screen all of a sudden.
Still works when you take the slider back.
Sugar build 54 on XO 1.5. Firmware Q3A18.

Change History

Changed 2 years ago by walter

  • priority changed from Unspecified by Maintainer to Normal
  • milestone changed from 0.84 to 0.90

Changed 2 years ago by walter

  • status_field changed from Unconfirmed to Assigned

Changed 2 years ago by walter

If you use alsamixer from the Terminal activity and then turn off mic boost then it seems to work as expected.

I'll investigate setting the proper parameters on launch.

Changed 2 years ago by GenJamGuy

The problem is due to the way the slider is mapped to capture_gain in the cb_page_sizey() method of toolbar_side.py. Instead of mapping the continuous slider position to the capture_gain with a formula, it is mapped discretely to one of 5 fixed levels in an if/else block. The discontinuity at the "approx 90%" point is caused by that point being a threshold between a gain of 100 and a gain of 300.

From a user interface perspective, one could change the slider to lock on one of 5 positions and keep the discrete mapping to capture_gain. A better solution would be to map the continuous slider position to a continuous capture_gain, provided the hardware supports more than 5 sensitivity levels.

Changed 23 months ago by walter

I've removed the crazy math from the slider in the version in git. (The code had been hardwired for the XO 1.0 hardware that had only 4 levels.) Hope to have this sorted out when I release v30. See Ticket #1070

Changed 22 months ago by walter

  • status changed from new to closed
  • resolution set to fixed

Should be fixed in v30.

Note: See TracTickets for help on using tickets.