Bugs

Luscinia has been developed by one person, and runs to more than 10,000 lines of code. I have made an attempt to diligently check code for bugs, especially for bugs related to important algorithms that could generate spurious results, and I have been helped by the users who have reported errors to me. Nevertheless, Luscinia is not completely bug-free. If Luscinia behaves in a way that seems wrong:
1) double-check that Luscinia really isn't performing correctly!
2) check the list of unfixed bugs below
3) if the bug is still unexplained, please contact me! ( rfl5 AT duke POINT edu)

List of unfixed bugs (incomplete)

1) Syllable and element bars do not always get drawn correctly when time zoom is used
2) Guide spectrogram does not align 100% properly (does not draw last bit of spectrogram)
3) Playback occasionally produces white noise. Due (almost certainly) to misalignment of bytes for the starting position. Need to investigate further exactly what causes this. (Might have been inadvertently fixed with shift to proper time syllables). Check with odd wav file formats.
4) Syllables should be more sophisticated than a chunk of time: should encompass annotation plus ability to deselect elements from syllable if necessary (e.g. overlapping male and female parts in a duet that should be encoded as separate syllables).
5) UI of individual details is pretty ugly!
6) UI of login window doesn't really work right: items do not become enabled correctly after user actions
7) UI of computer analysis is too complicated (too many windows)
8) Should allow comparison and analysis to be performed separately so that comparison does not have to be repeated if an extra stat is requested