Instant Map update (Bendy/McNally)

[amcnally336]

Hey guys! Started working on my set-up again (for looping), and everything seems to be working fine, but even when I changed the keystrokes for clip launch to the one you recommended, the focus does not seem to switch when I have moved some controls on the VST plug-in...ie I arm the clip to record with the scene select, I open the view for the actual VST, I move some controls on the VST gui, then I try to hit the foot pedal to record, but the clip will not launch. Am I missing something here? Thanks for the reply! Also, just noticed your new package. It looks great! Does this package include the progression builder aswell? The link seems to be down. Thanks!

[Stray]

It's been awhile since I've worked with the set up you have. For starters, we found a better focus changer...just "tab tab". So for clip launch, try "tab tab enter". That should work for you.

The new version doesn't include the progression builder as standard. This will be provided as an upgrade....haven't quite worked out exactly how to do it yet. Soon though. And I'll post new vids as soon as that's all worked out.

[amcnally336]

Thanks for the help. I have a few more questions, if you don't mind:
1) How do you go about assigning the global controls...I would like to change some of these to better suit my purposes. Also, is there a way to set these to toggle...ie, one global control for overdub on AND off, one for open AND close browser, one for metronome on AND off, another for quantize on AND off, etc. This would simplify things and open up more buttons for global use (I understand you are limited to 5, correct?)
2) How do you map the plug-in browser open/close? It is supposed to be ctrl P, but this does not seem to work for me. Am I missing something?
3)Could you possibly post a link or email me the als file for the progression builder? I would really like to incorporate this on the scenes that hold vst synthesizers. I actually plan on making one for major keys as well! (I believe yours is minor, isn't it?) Or if you could just talk it through a bit, I could probably figure it out
4) I am a guitarist, but want to use the keyboards more. I really don't want to learn a bunch of new scales and chords, so I figured the easiest way to get around this limitation would be to midi map one of the rotary controllers to the pitch controls of the midi clip. That way, I could just use the c major (only white keys) scale and chords for all of the keys, simply by changing the pitch. Would this work, and is this the best way to approach the issue? I was also thinking that perhaps another way of accomplishing this would be to assign some of the pads in each scene that would hold a vst synth to a different key (A, B, C, etc.) allowing instantaneous key changes (hit pad 1, pitch changes to key of A, pad 2=key of E, etc.), while still sticking with the basic chord shapes and scales of c major. Not sure if that is feasible...This combined with the progression builder on each of the synth scenes would be pretty friggin awesome!! I have already designed custom scenes for drum vst's, where the pads are all consistently mapped to the various drum kit sounds...I use all of the pads for drums except two, which are mapped to undo and delete, as I find it is invaluable to have these commands instantly accessible at all times!

Thanks a bunch for all of your help...I really appreciate it!
Feel free to explore and use any of these ideas in your own set-ups...you've probably thought of all of them anyway!

[Stray]

How do you go about assigning the global controls...I would like to change some of these to better suit my purposes. Also, is there a way to set these to toggle...ie, one global control for overdub on AND off, one for open AND close browser, one for metronome on AND off, another for quantize on AND off, etc. This would simplify things and open up more buttons for global use (I understand you are limited to 5, correct?)

You assign CCs to the User Messages in the pK’s Editor…go to MIDI and then Edit Global Data. You may not need to do that if you’re using the old TKP set up as they are already set up for you. They don’t toggle unfortunately, but you can use Bome’s to have them send keystrokes. For example, have User 1 send the letter K and assign K to Metro in Live. Now it will toggle. Same is true for Overdub. For the browser, you could just use Ctrl+B, that would open/close the browser. For quantize, you would need 2 controls since there is no single button for that. There are only 5 User Messages, but you could also use GM On (Message + Pad 3) as that sends out SysEx that gets ignored by Live.

How do you map the plug-in browser open/close? It is supposed to be ctrl P, but this does not seem to work for me. Am I missing something?

I’m not sure how that’s supposed to work to be honest….it’s never worked for me.

Could you possibly post a link or email me the als file for the progression builder? I would really like to incorporate this on the scenes that hold vst synthesizers. I actually plan on making one for major keys as well! (I believe yours is minor, isn't it?) Or if you could just talk it through a bit, I could probably figure it out

I was giving this away some time ago, but it’s actually part of a package I’m selling at this point. And, yes, it just covers minor keys, but you could set it up for major as well. To set it up, you have to create a rack with a bunch of chains (3 for each chord…to cover root position and both inversions). On each chain, you use a Chord plug in to generate the chord. You use the Key Zone editor to assign each chord (and its inversions) to one of your pads. You assign a pad to the Chain Selector so you can switch between inversions. And you put a Pitch plug in at the end so you can transpose to any minor key (or major if you set it up for that).

I am a guitarist, but want to use the keyboards more. I really don't want to learn a bunch of new scales and chords, so I figured the easiest way to get around this limitation would be to midi map one of the rotary controllers to the pitch controls of the midi clip. That way, I could just use the c major (only white keys) scale and chords for all of the keys, simply by changing the pitch. Would this work, and is this the best way to approach the issue?

MIDI clips don’t have a pitch control, but you can use the Pitch plug to transpose them. For major keys, you could just use C major and transpose to any of the other 11 major keys. But, for minor, you’d have to use A minor (which is also all white keys). The easiest way to do this would be to put a Pitch plug in on all your MIDI tracks and assign the Pitch knob for each instance to the same knob on the pK.

I was also thinking that perhaps another way of accomplishing this would be to assign some of the pads in each scene that would hold a vst synth to a different key (A, B, C, etc.) allowing instantaneous key changes (hit pad 1, pitch changes to key of A, pad 2=key of E, etc.), while still sticking with the basic chord shapes and scales of c major. Not sure if that is feasible...

Do you mean use the pads on the pK to switch between keys, but use a keyboard for playing? That’s feasible and would be set up like I mentioned about. Except instead of using a knob, you’d assign the Pitch knob to 12 pads on the pK and scale the range of the Pitch knob to 0 - +11. That would make it so each pad would transpose to a different key. For example, Pad 1 would be C. Pad 3 would be D. That would be more instantaneous that using a knob.

I hope that helps a bit.