Using keyzones to select Phrases is problematic for me (due to many of my Kontakt patches using all of the available 88 key range).
I suggested here that an alternative method of Phrase selection and application be made available via pattern commands.
In my view, not only would this provide a workaround for folks who find themselves very short of space to define keyzones within any given instruments, but would also provide a much more ‘tracker centric’ way of manipulating Phrases directly from the pattern data.
Is it possible to select which phrase is to be played using a method other than key zoning?
I see. For me that’s a shame as I’m working with Kontakt instruments that use much of the available key range. Any remaining space is left over to key switches for the patch.
Phrases would have been a lovely way to make ostinatos and have them transpose and vary in character.
Well, nothing is absolutely set in stone here. I’m simply saying how it is currently. Share your thoughts and ideas of how you think it could work, if simple keyzones are not getting the job done for you. :]
For me a simple pattern command to choose the Phrase number would be optimal.
It would also be very useful if the method of swapping were flexible, too. For example I might want to go immediately to Phrase 0E respecting the position in the currently playing Phrase. On the other hand I might want to have it play the next Phrase I select from the top, regardless. Or perhaps specify an arbitrary offset.
Further thinking on the general workflow here;
It would be nice to be taken directly to the Phrase referenced by the pattern command at the edit cursor with a shortcut.
Furthermore, the option to clone the Phrase, make changes and have that new Phrase inserted in the pattern at the edit point would be pretty fast!
Actually the velocity (volume) aspect works fine now. Playing a Phrase first at full velocity, then at maybe 50% does scale all the contained note volumes nicely.
At least from my point of view it’s the concept of zoning across the key range as the sole means of Phrase selection that presents the problem.
But what you suggest does also sound like an interesting dimension to Phrases. The possibility of altering the pattern data content of a Phrase, beyond its relative volumes, according to the trigger velocity would be superb, but in my view only as an optional dimension. The way it behaves currently is absolutely how I’d expect it to.
To be clear, the problem is that key zoning is the only means of selection. Of course there are many uses for it as it stands and I can understand why the devs went in this direction with phrase selection. But within the tracker environment I would have thought pattern commands were obvious candidates for a selection method.
This might be a better idea, as it would be immediately obvious that this particular instrument is playing a phrase.
Also, it would be cool if “ghosts” of the phrases were displayed, meaning when a phrase is selected in the pattern, the notes that it plays are visible and, let’s say, semitransparent to distinguish them from regular notes.
Another aspect to all of this is that I imagine that the Phrase selection command might be able to apply Phrases not associated with the current instrument.
Currently, as I understand it, you add Phrases inside an instrument and those Phrases are only available to other instruments by saving them as a preset and then loading that preset into any further instruments you may wish to apply the Phrase to.
Phrases are bound to instruments, essentially, through the key zoning paradigm.
My suggestion that Phrases ought to be selectable and applicable via pattern commands could transcend the afore mentioned limitation, and simply apply a Phrase to the current instrument regardless of the Phrases binding elsewhere.
So looking at all currently loaded Phrases as a pool from which any can be freely chosen and applied.
That doesn’t preclude the current regime of course, more adds to the flexibility by giving the user direct access to Phrase data, ignoring the current ‘packaging’ of Phrases within instruments.
Quite aside from my specific problem with keyzoning, keeping controls pattern-command centric is in the spirit of tracking. It’s what makes it powerful in the first place.
I understand that Redux is looking at a different slice of the market but I think both ideas could be served without compromising either.
I actually really like this idea. I was thinking earlier how phrases allow me to do some of the sorts of this that I could do with my old Korg KARMA. Having phrases selected by note-on, note-off, velocity, mod wheel etc could make them incredibly expressive! (Don’t know how feasible it is though)
I am also wondering if it wouldn’t be nice to have an effect command that turns the phrase on/off …
When of , it plays as a regular sample …when on =phrase is activated .
To put it simple , automate the phrase ON/OFF button
