melizalab / chirp Goto Github PK

As described in the wiki, cloning the repository like so git clone https://github.com/dmeliza/chirp.git results in a directory with only the following items:

chirp_logo.png   doc        index.html   params.json
chirp_mask3.png  index.css  javascripts  stylesheets

Hi - I installed from git master, after pip installing the dependencies etc. This is on Ubuntu 13.04, Python 2.7.4. When I run "chirp" from a command line I get:

Traceback (most recent call last):
  File "/usr/local/bin/chirp", line 9, in <module>
    load_entry_point('chirp==1.2.1', 'gui_scripts', 'chirp')()
  File "/usr/local/lib/python2.7/dist-packages/distribute-0.6.45-py2.7.egg/pkg_resources.py", line 343, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/local/lib/python2.7/dist-packages/distribute-0.6.45-py2.7.egg/pkg_resources.py", line 2354, in load_entry_point
    return ep.load()
  File "/usr/local/lib/python2.7/dist-packages/distribute-0.6.45-py2.7.egg/pkg_resources.py", line 2060, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/usr/local/lib/python2.7/dist-packages/chirp-1.2.1-py2.7-linux-x86_64.egg/chirp/gui/chirpgui.py", line 18, in <module>
    from chirp.gui.PitchOverlayMixin import PitchOverlayMixin
  File "/usr/local/lib/python2.7/dist-packages/chirp-1.2.1-py2.7-linux-x86_64.egg/chirp/gui/PitchOverlayMixin.py", line 11, in <module>
    from chirp.pitch import tracker as ptracker
  File "/usr/local/lib/python2.7/dist-packages/chirp-1.2.1-py2.7-linux-x86_64.egg/chirp/pitch/tracker.py", line 14, in <module>
    from chirp import template, particle, vitterbi
ImportError: cannot import name template
zsh: exit 1     chirp

Although I can calculate the pitch of a loaded signal I cannot save this data using the 'Save Elements' command (either using a shortcut or the drop-down menu). No '.ebl' or '.plg' files are ever saved.

The 'Batch Analysis'>'Compare Signals' function window is not resizable and cuts off just after the "Progress:" text field (i.e. what I'm assuming are the 'Start' and 'Close' buttons are not visible; I'm assuming they exist).

In the 'Batch Analysis'>'Compare Signals' window, when I select a directory holding wave files for analysis, use the default 'chirp.cfg' configuration file, set the comparison method to 'pitch_dtw' and storage format to 'file', and tab to 'Start' (which is invisible) and click it the resulting '.clg' results file is empty. (If the wavefiles' corresponding '.ebl' files are needed before this step, this may not actually be an independent problem.)

When opening a new signal, the spectrogram is drawn, then the dynamic range is updated, and then the spectrogram's redrawn, so there's a visible flash as the colormap changes. Either need to suppress drawing until the colormap's set correctly or change some buffering settings for this backend.

The keypress controls do not appear to work (e.g. 'p' to play back audio)

All of the inline images in Pages are broken.

This is because image src is dmeliza.github.io when it should be melizalab.github.io.

For some reason, when the application is run under windows, the standard method for binding to keypresses does't work, making it impossible to mark or alter regions.

The 'Batch Analysis' > 'Calculate Pitch' function fails with the error message: "Error: Can't pickle : it's not found as chirp.pitch.batch._job"

This one is not a major worry for me, but I expect it would trip some people up:

The first soundfile I opened was a 24-bit WAV file. The GUI didn't show anything. I didn't know if it had loaded or not. Then I realised that the commandline was showing a problem:

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/chirp-1.2.1-py2.7-linux-x86_64.egg/chirp/gui/chirpgui.py", line 505, in on_open
    self.load_file(infile)
  File "/usr/local/lib/python2.7/dist-packages/chirp-1.2.1-py2.7-linux-x86_64.egg/chirp/gui/chirpgui.py", line 381, in load_file
    fp = ewave.wavfile(fname)
  File "/usr/local/lib/python2.7/dist-packages/ewave.py", line 71, in __init__
    self._load_header()
  File "/usr/local/lib/python2.7/dist-packages/ewave.py", line 258, in _load_header
    raise Error, "invalid bits per sample: %d" % bits
ewave.Error: invalid bits per sample: 24

24 bits-per-sample is not truly "invalid" but if ewave can't cope with it, that's a limitation one might have to live with. But it would be nice if the GUI would catch the exception and show the user that there was an error in loading.

Hi Dan,
I'm hoping this is the correct place to report potential bugs. First, thank you for the updated installation instructions for getting Chirp working on a Windows machine; it's very clear now and I got the GUI running quickly. I've played around with the GUI for a couple hours now and have noticed a few issues (I hope not entirely related to my complete ignorance of Python). In case it's useful, I'm using Windows 7 and installed all the recommended versions of packages and dependencies as suggested on the website. Here are the issues I've encountered so far:

1. Although I can calculate the pitch of a loaded signal I cannot save this data using the 'Save Elements' command (either using a shortcut or the drop-down menu). No '.ebl' files are ever saved.
2. The keypress controls do not appear to work (e.g. 'p' to play back audio)
3. The 'Batch Analysis' > 'Calculate Pitch' function fails with the error message: "Error: Can't pickle <function_job at 0x000000000AE2E668>: it's not found as chirp.pitch.batch._job"
4. The 'Batch Analysis'>'Compare Signals' function window is not resizable and cuts off just after the "Progress:" text field (i.e. what I'm assuming are the 'Start' and 'Close' buttons are not visible; I'm assuming they exist).
5. In the 'Batch Analysis'>'Compare Signals' window, when I select a directory holding wave files for analysis, use the default 'chirp.cfg' configuration file, set the comparison method to 'pitch_dtw' and storage format to 'file', and tab to 'Start' (which is invisible) and click it the resulting '.clg' results file is empty. (If the wavefiles' corresponding '.ebl' files are needed before this step, this may not be an issue once issue #1 is fixed.)
   Hope this info helps in debugging.
   Thanks,
   Julian