Comment 12 for bug 1070776

Hi Jeffrey,

It looks like the microphone is catching a lot of noise, and the control frequency is very faint on this system.

I played the .wav file at a very high volume with headphones (careful when doing this!) and at the very end I can faintly hear the high-pitched sound.

Also, as you mention, it *is* present in the .csv file showing the spectrum analysis.

But here's the problem: the script has a sensitivity parameter, so it requires the "peak" from the control frequency to be at least 2.5 dB higher than the base level in the recording.

In this case, the base level is at -60.0 dB, so the peak would have to have a magnitude of -57.5 or higher (higher as in "less negative").

However, looking at the data, the peak is too small, here are the relevant data points:

7149.0234375,-60.0
7235.15625,-59.795244979858396 <- this is the one for the control frequency
7321.2890625,-59.99746189117432
7407.421875,-60.0

Since it's only 0.21 dB higher, it's not being considered as a valid peak.

Jeffrey, I'm attaching a tweaked version of the audio_test script, it will use a higher volume and "listen" for longer so it has a better chance of getting a good signal.

Could you please run it (audio_test_1070776 -d -u /tmp/spectrum.csv -a /tmp/audio.wav), post the output and attach both spectrum.csv and audio.wav files? Also, of course, please check whether the script succeeds this time.

Hopefully if these tweaks help solve the problem I can incorporate them into the release version of the script.

Thanks!