I’ve got another inconsistency (or misunderstanding), but don’t want to muddy the waters yet. I’m certainly open to the fact that I’m making a mistake or misunderstanding, so please correct me.
I’d love to read other developers comments on this. If that is in fact how computeSpectrum() works, I think I would prefer the docs say that it was using “22kHz stereo sampling”. In other words, a single measurement retrieves both left and right channel data. Usually, the “samples” are a stereo measurement (for stereo sources). But, that is not how I usally see audio data represented. That would at least make the numbers work out.
Does the “44.1kHz sampling” alternate between left and right channel samples? 0058 seconds, yet according to Audacity, the matching graph is. Since I’m using the default params to computeSpectrum(), I expected 256 samples (looking at, say, the left channel only) at 44.1kHz to represent. Through very careful comparison, I believe I found the section of the sound in both my Flash sample and in Audacity. I then took the MP3, loaded it into a sound editor (I used Audacity).
Basically, I load an MP3, play it, acquire and graph the data (as practically all computeSpectrum() samples do). If you analyze the resulting data very closely, something *may* not add up. I actually think there is either something wrong with the computeSpectrum() method or the documentation is overly vauge, but I haven’t found anyone discussing it anywhere.
0 kommentar(er)
