You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using analyzer.py with --overlap 2.9 causes Begin Time (s) in the output file to be shifted relative to the true begin time in the audiofile. The reported time is a couple of seconds earlier. I didn't notice this behaviour when using --overlap 0.
Expected behavior Begin Time (s) is expected to exactly match the beginning of a call in the audio file, regardless of the --overlap setting.
Selection View Channel Begin Time (s) End Time (s) Low Freq (Hz) High Freq (Hz) Common Name Species Code Confidence Begin Path File Offset (s)
1 Spectrogram 1 1 606.7000000000694 609.7000000000694 0 8000.0 Waldkauz tawowl1 0.0974 path/to/folder/20240425_202300.WAV 606.7000000000694
2 Spectrogram 1 1 606.8000000000694 609.8000000000694 0 8000.0 Waldkauz tawowl1 0.2410 path/to/folder/20240425_202300.WAV 606.8000000000694
3 Spectrogram 1 1 606.9000000000694 609.9000000000694 0 8000.0 Waldkauz tawowl1 0.6160 path/to/folder/20240425_202300.WAV 606.9000000000694
4 Spectrogram 1 1 607.0000000000695 610.0000000000695 0 8000.0 Waldkauz tawowl1 0.8510 path/to/folder/20240425_202300.WAV 607.0000000000695
5 Spectrogram 1 1 607.1000000000695 610.1000000000695 0 8000.0 Waldkauz tawowl1 0.7917 path/to/folder/20240425_202300.WAV 607.1000000000695
6 Spectrogram 1 1 607.2000000000695 610.2000000000695 0 8000.0 Waldkauz tawowl1 0.9630 path/to/folder/20240425_202300.WAV 607.2000000000695
However, the audiofile shows that the first call starts at ca. 610 seconds, about 3 seconds later than reported. In this case, the size of the shift is about the same as the size of --overlap.
Questions
Is this expected?
Can I always add --overlap to the reported Begin Time (s) to create correct audio subsets?
Any help is appreciated!
Session Info
OS: MacOS, 14.2.1
Python 3.9.6
birdnetlib 0.17.2
The text was updated successfully, but these errors were encountered:
I don't know what is causing the issue.
But, would you be willing to try the new birdnet Python package? The release 0.1.1 includes a new way to load the audio.
It would be interesting to test it in your use-case and see if it returns the expected results.
You can find the repository here https://github.com/birdnet-team/birdnet
Hi Stefan,
Many thanks for this amazing set of tools!
Describe the bug
Using
analyzer.py
with--overlap 2.9
causesBegin Time (s)
in the output file to be shifted relative to the true begin time in the audiofile. The reported time is a couple of seconds earlier. I didn't notice this behaviour when using--overlap 0
.Code Used
Expected behavior
Begin Time (s)
is expected to exactly match the beginning of a call in the audio file, regardless of the--overlap
setting.However, the audiofile shows that the first call starts at ca.
610
seconds, about 3 seconds later than reported. In this case, the size of the shift is about the same as the size of--overlap
.Questions
--overlap
to the reportedBegin Time (s)
to create correct audio subsets?Any help is appreciated!
Session Info
The text was updated successfully, but these errors were encountered: