drxcm wrote: ↑
Thu Feb 27, 2020 3:49 am
Great beat chop!
Yup it’s tight internally and when clocking other modules.
Thanks! Just wanted to show something cool, fun and tight, as we're also bashing Arbhar a little.
I want us all to be informed about what it can and cannot do, at what it shines and what could be improved
I still love this peace of gear
And I hope we'll get the trigger out option that will echo the external trigger "post-latency", so I could work my way around the latency when need be.
But as I said before, a little latency will be inevitable. Maybe a super-short-latency mode can be thought of, in which the internal parameters are optimized for this kind of use. I'm well aware that in software development, or engineering in general, every choice is a trade-off. And I think most choices in Arbhar have been trade-offs in favor of making the granular/cloudy side perform brilliantly.
Like, it has a gazillion CV input options, that probably takes some time to scan; they all need to be noise-filtered before the unit can decide whether there is a CV and what to do with it. (opposed to some sample player that just has trigger and pitch CV) If there would be a mode in which only the CV inputs for rhythmic use would be considered, that probably takes away some of the latency.
But then again; Does Instruo want to add the complexity of such a mode to the system? Does that fit their view and design philosophy? Choices!