And if there’s anything you think the community could contribute to helping it get nearer release readiness…
Well, that would be wonderful
I’ll try to see whether I can tidy up things slightly and put them on github.
If you want to help that would be amazing, there’s one thing which I would love to have but which I am unable to do: a general off-line processer of buffers via “lambda” paths. I have been doing HOA lately and it’s painful to wait for a playback and record, whereas I could just take a buffer, pass it through ICST/SPAT/HOA tools and have it bounced. Think of a [ears.process~] that takes a buffer and uses a sort of bach-like lambda inlet/outelt behavior for signals. You would be able to process offline any treatment (say, your own beloved timestretcher, and not the ones from rubberband and paulstretch provided). That would be a game changer in the library, I think.
After discussing with Andrea it looked like this was not possible and seemed more likely that the behavior should have been poly~-like instead (which I hate, but the best is enemy of the good).