Sound is captured from microphone or line input, expressed as digital
audio samples, resampled at a frequency congruent with the display,
and then drawn as a graph. Some time is then allowed to elapse before
doing it again.
Where possible, the calculations for capture, resampling, and
formatting are handled by very fast C code in libraries; ALSA, Numpy,
Cairo, and GTK. This ensures the waveform can be updated many times a
second.
The best guide to the logic is the source code
https://github.com/sugarlabs/Measure
A visualisation tool such as pydeps may be of use for understanding
the code structure quickly.
My advice is to look for JavaScript waveform capture and display
modules.
On Thu, Mar 12, 2020 at 08:20:20AM +0530, Abhishek Tanwar wrote:
> I am porting the Measure activity of Sugar to Sugarizer. Can anyone please
> help
> me understand the logic used in measure Activity .
> I would be very thankful to you.
>
> Thank You
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
--
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
