Onset-based regression (JIT-MFCC example)

I mean, this is why you guys are hired - to contribute to interface research in creative coding - so I’m happy we got there in the end :slight_smile:

Seriously, I agree, especially for readability of old patches, that verbose attribute names, if painful to enter, are much easier to read…

It depends™ :slight_smile: what i tend to do now is trial and error. What is it you cannot do now? If you ask a specific optimisation question, then maybe @weefuzzy @groma and/or me will have specific ideas. For me, if you get good results with similar training sizes (40-50 hits per class) then stop there and make music until something clear pops out… this is your usual modus operendi but now I’ve lost the plot in this thread on what is actually needed to improve…