[Clam-devel] Bugtracking, time to change?

[JunJun]

I tested the Windows installers for the last stable release: CLAM-Annotator-0.3.10_setup.exe. In the normal testing cicle, it works fine, and the bug listed in bug tracking tool "Annotator 3.6 crashes on selecting song of a chord project" seems unable to be reproduced in 3.10. (As Pau said, time to update the bugtracking.)

 

Afterwards, several tricks are tried to play with Annotator. I summarized some bugs and user-friendly related issues here:

1.       Configuring the “Project properties” lead to crash.

For example, I configured a new project in “project properties”, such as:

[

Project file: ./test.pro    (BTW, the rightside “openfile” icon doesn’t work)   

Descriptors scheme: ../CLAMDescriptors.sc                            

Descriptors file suffix: .pool                                         

Extractor command: ../ ClamExtractorExample.exe

]                       

It worked fine. 

Then I edited the “project properties” of the same project into: 

[

Project file: ./test.pro                                               

Descriptors scheme: ../Chords.sc                                                          

Descriptors file suffix: .chords                                       

Extractor command: ../ ChordExtractor.exe                             

]

Press “ok”, then it crashed, 

and the backtrace gave:

[

##########################################################

################### ASSERTION FAILED #####################

##########################################################

At file src/Schema.hxx line 230

Accessing an attribute 'Frame':'MelFrequencyCepstrumCoefficients' not in the sch

eme.

 Unable to adquire symbols names for the backtrace

terminate called after throwing an instance of 'CLAM::ErrAssertionFailed'

  what():  Accessing an attribute 'Frame':'MelFrequencyCepstrumCoefficients' not

 in the scheme.

]

Looking into the test.pro file, I found the <views>...</views> section was not modified relatively, which led to the crash.

 

2.       Users tend to omit the step from “modified project” to “save project”, making the flow kind of awkward. Another thing is, it would be better to show the project name in the title of the window, such as “test.pro- Music Annotator” instead of “Music Annotator”. 

 

3.       Why does Annotator require an existing Pool file of a song?

When adding a new song, Annotator requires the song to already have a compatible pool file.

Otherwise, it will crash when clicking on a song, and the backtrace gives:

[

##########################################################

######################## WARNING #########################

##########################################################

At file scons/libs/core/src/XMLStorage.cxx line 118

Restoring from an unopened file with filename <F:/music/angelofthemorning.mp3.no

nchords>

terminate called after throwing an instance of 'CLAM::XmlStorageErr'

  what():  Unable to open the document source

]

Given the scheme, it’s better for Annotator to automatically create a related pool file, rather than require a predefined one. Consequently, it may avoid several related crash-bugs. 

 

Although above are several trivial bugs, I suppose reporting them here may be useful. Next I will continue the work of Windows MinGW cross compile.   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clam-project.org/pipermail/clam-devel-clam-project.org/attachments/20080411/41ab60ac/attachment-0004.htm>