My code using nudio to read a special MP3 shows different results than many other business apps .
Specifically: The node-based code on my audio searches for ~ 1 second silence, before the "audio audio" (a drum pickup) starts before the start of this MP3, the other Apps (Windows Media Player, Realplayer, WavePad) show ~ 2.5 seconds silence before this same drum pickup.
The special MP3 is downloaded like "A Rolling Stone" from Amazon.com. Many other MP3s were tested and no one shows any difference between my code and other apps, most MP3s do not start with such a long silence, so I suspect that this is the source of difference.
Debugging problems:
-
I can not really get it, it's also a way to prove that other apps are correct and that Nudeo / I is wrong, i.e. Blocking the results of my code according to the "best known reference implementation"; So I can not properly define "error" which I want to debug
-
Since my code reads thousands of specimens during those 1.4 seconds without any obvious errors, think about t where to see a bug in the input stream / When to narrow.
-
The heart of the NAudio code is ACMstream Convert () to P / which is a "black box" call that I can not forget about error-checking.
Can anyone think of any trick / technology for any debug?
I am not sure what other media players take to play with MP3, but I doubt that many of them have their own MP3 decoder rather than depending on the operating system.
Comments
Post a Comment