What is the problem?
The midi capability feels slightly limiting. 32 channels of midi out capability, but only 8 single note tracks.
I’m not Vangelis or anything, but a few suggestions that could make the p+ better.
What should this feature achieve?
“midi only mode at project level” - mute the usb audio out engine(for CPU gain). Allow all 16 tracks to be midi only. Possibly also allow the variation to behave slightly differently, and allow variation to only be 1 pattern per channel, but have variation patterns running all the time. This would potentially give 32 tracks of midi.
I appreciate you can have any step trigger any midi channel, but larger arrangements get messy if you do this too much. Once you’re triggering chords, rhythm, FX, and adding layers - you run out of tracks very fast. With 32 available midi channels, the 8 addressable steps per tick, runs out fast.
Second thing would be a midi CC trig. So I can hold a pad, go to chance and can choose a midi CC trig and supply CC number and value. There’s a few ways I can think to add the 2 value input required, but the Devs would know best. This gets around the CC limit in a crude way but does give flexibility.
Third would be allow incoming CC on a channel to be recorded to step automation. You could log it using midi trig above. Harder to implement due to the flexibility of the p+ but would be nice.
Are there any workarounds?
None I’m aware of
Any links to related discussions?
–
Any references to other products?
The Novation tracks, handles midi CC recording deletion by choosing delete function, then wiggling a CC knob. It then removes the entire CC from that channel.
You can overwrite a CC by overdubbing, but you can’t edit the recorded CC per step.
This would work for p+. So you “can record incoming CC, and clear it, but you can’t micro edit it”