TAPESTREA : Known issues, bugs, constraints

version: (tap tap)

home: http://taps.cs.princeton.edu

Contrary to popular belief, the TAPESTREA software is not entirely perfect (yet). Here are some problems we are aware of and hope to fix in future versions. Please also see the wiki for a further list of bugs and desired features. If you come across difficulties not listed yet, let us know by posting to the mailing list or emailing us directly.


  • Sound files must be the same sample rate as taps, or the sample rate conversion settings may need to be changed.
  • Reverb tails causing high CPU usage was fixed, but perhaps not entirely.
  • There have been reports of the UI flickering on some Linux platforms (like Mandriva). If this happens even while hardware graphics rendering is enabled, we are not sure what causes it. Tips from users who know more about this would be appreciated.


  • Changing fft size and analysis window size may cause unexpected behavior if a template was extracted at settings different from the current settings.
  • Need improvement to UI : handling of residues. The residue needs to be saved before it can be played.
  • Need improvement to UI : saving of templates to library only. Saving a template opens up a file dialog box so that you have the option of saving it to file as well as to the library. To save to library only, you need to hit the cancel button.
  • Saving residues requires both a .tap file and an extracted .wav file (by default, res_xxx.wav). As a result, residues aren't very portable.
  • Also, the res_xxx.wav file may be overwritten when new separations are performed, further complicating residue template saving. To get around this for now, you can always specify a unique name while saving a residue.
  • The "use energy ratio" option in transient analysis is not always stable (it may crash the taps session).


  • Repeatedly playing a timeline by rapidly hitting the space bar can cause a crash due to concurrency issues.
  • Transient time/frequency warps are CPU intensive, making transients impractical to loop in high densities. This also holds for raw templates and files.
  • On some machines, stopping and quickly restarting a residue template may cause crashing (non-deterministically).


  • Repeatedly playing the selected tracks by rapidly hitting the space bar over and over can cause a crash due to concurrency issues.
  • Editing a track modifies the original template, which is good except when a track is cut; then the original template has only the first cut segment.


  • TapsTemp.readFromFile() works only if the .tap file is in the same directory as the script.


  • Needs documentation and refining. Undergoing identity crisis.

taps | soundlab | cs | music