Re: [nfc-l] missing first few milliseconds of spectrograms made in Raven

2015-01-22 Thread Bill Evans
Thanks for the explanation Dean and Laura, and to everyone else for chiming in. I haven’t made spectrograms of short call notes for publication since the Flight Call Guide back in 2001. I used Canary back then and the method for generating spectrograms must have been different because there

Re: [nfc-l] missing first few milliseconds of spectrograms made in Raven

2015-01-22 Thread Laura C. Gooch
Bill, The Cornell folks could probably answer you more definitively, but I think this is not a bug, but rather a result the way spectrograms are generated. The spectrogram comes from sampling and analyzing successive chunks of the waveform, so until enough time has gone by to encompass the

RE: [nfc-l] missing first few milliseconds of spectrograms made in Raven

2015-01-22 Thread Dean L Hawthorne
It’s not a bug, it’s a deliberate design decision. The first spectrogram frame takes N samples of audio data to compute; where should we say that the spectrogram frame is centered, on sample 0 or in the middle at sample N/2? It was decided that Raven would center the spectrogram frames on the

[nfc-l] missing first few milliseconds of spectrograms made in Raven

2015-01-22 Thread Bill Evans
When I open a short night flight call wav file in Raven, the waveform window begins at 0 sec but the accompanying spectrogram window doesn't begin at zero -- it begins after a few milliseconds. See attached example. It’s not something that one would note unless they are working with very short