waveform view, data structures, etc

[jamesholdenmusic]

• dict structure:
• filename
• markers: (an array)
  • marker pos
  • divisions (to next marker)
• how about: it background scans waves loaded for key, rhythm events (via bonk) and intensity? etc, stores them in json files that live near the wavs?
• let the user tag slice markers with other properties, such as loop start/end, or even a 'drop' marker that auto-advance stops just before?
• these things would be easier if you could listen to the active marker or whatever through the cue out

?

• types of marker would be good: regular / individual
  • regular is what was in v2-4, markers evenly spread across designated range
  • individual is when it's just a list
  • editting a marker from reg mode should turn it into individual

[jamesholdenmusic]

use FluCoMa to tag waves (especially energy levels for the wave scan plugin but also pitches etc)