Possibilities for Plugin Parameters » History » Version 5
Version 4 (Chris Cannam, 2014-05-07 03:05 PM) → Version 5/14 (Chris Cannam, 2014-05-07 03:07 PM)
h1. Possibilities for Plugin Parameters
Two directions we could take:
# No parameters
# Enough parameters to be interesting
h3. h2. Fast and Slow modes
A problem with "no parameters" is that there is such a big difference in [[Speed|processing speed]] between different configurations. There's a strong case to be made for offering at least a choice between fast/draft mode and slow/thorough mode.
* The most obvious difference would be that "fast mode" should suppress the 5-step shift factor.
* We might also consider using a finer-grained time step in "slow mode". I think the current 40ms step results in audible jitter, though I may be wrong (possibly any timing imprecision results mostly from some other aspect of the method).
h3. Instrument restrictions
Presumably the method can run much faster if we are able to tell it that a piece has only one instrument in it. We might offer a dropdown of "all known instruments", "piano", "trombone" etc.
h2. Possibilities for Plugin Outputs
Currently we have
* Note transcription
* Raw constant-Q
* Filtered constant-Q
* Pitch activation
What else does the plugin know, that might be interesting?
* Identity of predominant instrument, or of the estimated instrument for each note (not currently returned through the note transcription)
Two directions we could take:
# No parameters
# Enough parameters to be interesting
h3. h2. Fast and Slow modes
A problem with "no parameters" is that there is such a big difference in [[Speed|processing speed]] between different configurations. There's a strong case to be made for offering at least a choice between fast/draft mode and slow/thorough mode.
* The most obvious difference would be that "fast mode" should suppress the 5-step shift factor.
* We might also consider using a finer-grained time step in "slow mode". I think the current 40ms step results in audible jitter, though I may be wrong (possibly any timing imprecision results mostly from some other aspect of the method).
h3. Instrument restrictions
Presumably the method can run much faster if we are able to tell it that a piece has only one instrument in it. We might offer a dropdown of "all known instruments", "piano", "trombone" etc.
h2. Possibilities for Plugin Outputs
Currently we have
* Note transcription
* Raw constant-Q
* Filtered constant-Q
* Pitch activation
What else does the plugin know, that might be interesting?
* Identity of predominant instrument, or of the estimated instrument for each note (not currently returned through the note transcription)