Midi control?

I’m using the software with a midi controller or 2.Can i change tracks?Without using the mouse?Fed up with mousing around....Thanx

I dont mind mousing about,its actually much better than using an interface a lot of the time,more direct......But some things like tracks are just plain annoying.I guess i can find this info in the manual if i look but hey...

Workaround: ctrl + [ or ]

dsy73 wrote:Workaround: ctrl + [ or ]

Hmm......I’m using MBP and that does not seem to do anything.Whats the (or)?

he is referring to the key '[' or the key ']' for you to change tracks with the keyboard.

COOlio...........just worked it out too...................... Command and [ or ] ha.That def makes things easier.Gonna spend time getting to know this programme better now and less time fukin with hardware~!!!! Cheers

dryad-66 wrote:I’m using the software with a midi controller or 2.Can i change tracks?Without using the mouse?Fed up with mousing around....

You can change tracks with a program change message.

Alternatively you can use program change messages to change programs and sequences.
You can change the setting for this in the general preferences menu.

The Ken wrote:You can change tracks with a program change message.

Alternatively you can use program change messages to change programs and sequences.
You can change the setting for this in the general preferences menu.

Nifty. The problem with that is Prog Change + pad (on the MPK Mini MK3) just changes the currently selected Midi track's Program, permanently. Why would on the fly program changes be useful? If changed during a recording, doesn't that affect all previously recorded notes, too?

Also, when I tap my pads with Prog change on, a few of them don't do anything, and the others just select programs that are not sequential. How do I map those (if I had to)?

GuruVirus wrote:
The problem with that is Prog Change + pad (on the MPK Mini MK3) just changes the currently selected Midi track's Program, permanently.

The way the MPK mini does program changes is more the issue. If you just had program change on an encoder, the benefits would be readily apparent.

Why would on the fly program changes be useful? If changed during a recording, doesn't that affect all previously recorded notes, too?

There are many reasons why a user might want to map midi program change messages to MPC programs. You don't necessarily have to do it on the fly, or while recording. If you had some midi notes laid down for a track and you wanted compare how different plugins or keygroups sounded, you could simply change the program instead of loading the midi data on a track for each of the programs you wanted to audition. You can do the same thing switching drum kits.

As far as recording, you could have two or more programs with bass instruments that were slightly different. While recording that track you could use program change to "modulate" the sound by switching on the fly, as you put it.

Also, when I tap my pads with Prog change on, a few of them don't do anything, and the others just select programs that are not sequential. How do I map those (if I had to)?

My guess is that you need to use the MPK editor to assign what program change number each pad sends. They may not be set up sequentially.

Thanks for clarity, Ken.

GuruVirus wrote:
Nifty. The problem with that is Prog Change + pad (on the MPK Mini MK3) just changes the currently selected Midi track's Program, permanently.

This behaviour can be changed in the prefs. See p.96 of the manual:

General

Program Change: This determines what an incoming MIDI program change message will change: a Program, Sequence, or Track.

Thanks for digging that up for me, dude. I think a Sequence change (like a DJ controller's Cue function) would be more useful for me than a track change (single click solution or Ctrl + [ or Ctrl + ]) or a Prog change (which I can't imagine doing on the fly; it would sound so terrible unless the progs were really similar).