Hi guys,

Got a little problem that I can't seem to remedy with regards to the midi in Predator. More to the point, with midi between patches in a bank. I make sound #1 with my mod wheel latched to F1 cut. Save the bank (not an individual preset). Then I make sound #2 in the same bank, and want that patch to that the LFO speed controlled by my mod wheel. Set CC, or latch, Save bank again. Now I go back to sound #1, and it's lost it's latch to F1 cut, and the LFO spped is now getting modulated... obviously these are global midi sets and latches.

Is there any way to have preset #1 have the mod wheel controlling the cut and in preset #2 controlling the LFO speed (or what eve other control I choose) all in the same bank?? I thought about the fact that it may be possible if I save every preset individually, but then, how do I create a bank of presets that retain that property, but that still comes up as a bank in Predator under the bank menu?? Is there a way to make a subfolder that would lump presets together?

Cheers,
George

PS: I typed "midi latch" in the quick search in the RP forum and read EVERY thread, start to finish (seriously, I've been here reading about midi latching for almost 2.5 hours), and couldn't find anything on this...

Midi cc's are set globally, they are stored in the registry or preferences (pc or mac).

However you can say ECS files, which saves all the midi latch settings, and load in the appropriate ECS file for that presets. So in one ECS mod wheel control filter cutoff, in the other LFO speed, you load in the appropriate one for that preset your self.

Or you can use the modulation screen to modulate the controls via midi input, so setting the source being the mod wheel for instance, and the destination being the filter cutoff. This can be different in different presets.

Hope this helps.

Cheers

Jon : RPCX

Hey Jon, I figured that global thing from the manual, but decided to post my question in anyway... then, after I'd gone to bed and was thinking bout this... it finally clicked, "duh, use the mod section with the source set as ModWheel...". One thing that this does is add a limit to range of motion (amount applied), if you need it, which I actually was wondering about as well, so that solves 2 problems. In saying that though... if someone else loads my bank, how will they know to unlatch all other MIDI (I assume if you've set your source to ModWheel in the mod section, nothing actually needs to be latched right?)?

Sorry for all the Q's, I'm busy programming a commercial bank that's due for release SOON.

Cheers,
George

PS: I'll submit a copy to you and Rob once I'm done, for approval, before I start selling it (I assume that's how you guys do it).

Hi there

If I understand what you want, you want to determined the midi latching bank that people should use with your bank, even if it is no latching at all, then you can save the required midi latching settings in an ecs file, include that with the bank file and in a readme or something similar, say that you suggest people load in that ecs file so that their midi latching settings are as required.

And yes your right, if you use the mod slots for modulation you don't need to use an latching.

Hopefully this helps.

Cheers

Jon

PS And thanks for the offer to send us the bank, I hope things go well and we look forward to seeing it.