Sorry, if I misunderstood, a few posts up, you wrote, that the MatriX is on the top of your priority list and everything else comes later. I also thought this is going to go along a bit faster than 'âyearlyâ' updates, especially since we donât know how big the updates are going to be and what can we expect considering you mentioned that itâs processing power is almost capped. Some features and updates are quite important for some of us and waiting another couple of years just isnât an option.
I have a list of things that would want to be addressed but would rather send them over an email with further elaboration, just because forum posts can be a bit lengthy for that purpose. But I do want to check with you what the plans are, because as a live artist I have certain needs and wishes for live performances that I have to solve and canât afford to wait indefinitely.
As far as start/stop/pause functions (a.k.a. midi fitering) there are multiple case uses that would benefit from that, and those workflows usually implement other gear (sequencers) in conjunction with LoopA.
For instance, since it is a midi router, launching a midi clip from another piece of (master clock) gear without LoopA running (but sending in through) and without LoopA being the master clock source. Maybe I like to use another piece of gear as a master clock but wouldnât want LoopA to always start from bar 1. Then I can play whatever I want from my keyboard, tap the tempo in and then launch a clip from LoopA at a given point in time. Another use-case would be, to do some creative restart playing and record those into LoopA, which right now isnât an option if you want then to be synced somehow. Another may be, that if you want to use an extra sequencer, the way LoopA is set right now, LoopA must be the midi master, which means, that the other piece of gear has to use an IN and an OUT, which loses you and extra output or you have to introduce more complexity with extra midi routers (and cables) which eats the always valuable real-estate, which is one of the selling points of LoopA. If you havenât stumbled upon it in hardware units, all DAWs offer basic midi options/filtering like this. Thatâs how you specify the hierarchy when using multiple midi controllers and assure compatibility and different workflow implementation.
Most of these go from a live performance view, which happens to be my point of view, thatâs why Iâm also asking about workflow improvements, because I feel, that some of the features canât be accessed fast or well enough for creative use and improvisation in a live situation. Just to throw one in here: autoloop seems to assume that LoopA is the master clock and doesnât really work with LoopA in slave mode with arbitrary BPM, which means you have to specify the right BPM in any case.
I feel like this is already long enough, Iâd also have to consult my notes to elaborate further.
Cheers!
