@JWL said:

I always put in beginning keyswitches just before the first MIDI note data locations on each track just to ensure that the starting patches and volumes are correctly registered with each project.

Hope this helps.

And you must make these keyswitches "legato" so that the correct matrix/patch will play no matter where in the track you start (assuming that your sequencer is set to chase notes).

DG

JWL,
Is there a note chase function in DP? I always have to scroll back befor a note on to get a keyswitch to trigger.

Thanks.

@JWL said:

I always put in beginning keyswitches just before the first MIDI note data locations on each track just to ensure that the starting patches and volumes are correctly registered with each project.

Hope this helps.

And you must make these keyswitches "legato" so that the correct matrix/patch will play no matter where in the track you start (assuming that your sequencer is set to chase notes).

DG
Hey DG-- can you clarify a bit more? Do you mean the length of the keywsitch notes? (I don't get the sense that you mean "legato" patches). Are you saying that your keyswitch durations actually dove-tail?

Hmm... me-thinks herein lies a bit of brilliance. I'd never even considered this-- and for reasons of avoiding MIDI data jamming things, I've always shortened my keyswithes to an 8th or 16th. I still struggle with a little keyswitch issue which Marnix cannot reproduce, but dove-tailing keyswitches will solve a multitude of problems.... that is, of course, if I've understood your tip properly.

@dpcon said:

JWL,
Is there a note chase function in DP? I always have to scroll back befor a note on to get a keyswitch to trigger.

Thanks.

That's what I'm wondering with respect to DG's suggestion... dove-tailing keyswitches just might be the solution to the gnarly chase race.

(I started putting keyswitches on different MIDI tracks just to keep things better organized. It makes for more tracks, but it's easier to edit the actual part or the keyswitches when they are not all on one track. This is where DP5's new track folders will come in quite handy.)

Thanks for the tip. I had not looked at the AU-GUI for the purpose of saving matrices. I had only noticed on the standalone the "file" and "options" menu. As to my other issue, I find that I need to save a matrix as a preset if I want to use it in another song file,IF I IMPLEMENTED VELOCITY XF. This info is not saved in the matrix.

As to the legeto keyswitch idea, I agree brilliant. I to have never done this. Setting up a special keyswitch track for this purpose is a perfect idea.

J

@Jay Weigel said:

IF I IMPLEMENTED VELOCITY XF. This info is not saved in the matrix.
J

True. The matrices are loaded with their default settings. I've relied solely on the sequence for contextual settings. It would be helpful if the default settings gave us identical volumes across the board for an easier starting point if, say, all default velocities and controller settings were standardize and rendered the samples at the same volume consistently before editing. The actual numbers just might be standardized (I've not checked), but it does throw one for a loop when a note jumps out or is suddenly inaudible. It's a little too easy to go on a wild witch hunt for wayward controller data in the sequence. For the most part it's okay, but I'm still scratching my head about some of this when it occurs.

Being able to save benchmark controller data with the actual matrix would be great for picking up where one left off. Resetting these with every project can get tedious.

OK, let me explain something in very simple terms. In order for a keyswitch to work the sequencer sends a "note on" signal, which tells the VI to change the matrix or patch. The note off is irrelevant for this discussion. Therefore when a sequencer chases notes it looks for an active note on. If you use a short note then a "note off" will probably have already been sent, so there is no "note on" active at this time. Therefore the matrix/patch played will be the one currently active. However, if your keyswitches are so long that they almost touch then a "note on" is still active no matter where in the MIDI sequence that you start from, so the VI will always know what matrix/patch to play.

DG

That's what I thought you meant. In fact, I've been putting this to good use all evening. Some things are just so obvious that can easily be missed.

Jay,

In order to save a Preset in Logic, use the "small" plugin window that first opens (Not the big VI GUI). Just <save setting> as you normally would do for a plugin in Logic. You can then copy this .aupreset file to the default folder for VI (.fxp and .aupreset files both work on Mac) and your saved presets will appear in the main GUI window.

Regards - Colin

Colin,

Thanks for the clarification.


J

@JWL said:

That's what I thought you meant. In fact, I've been putting this to good use all evening. Some things are just so obvious that can easily be missed.

Well I just hope that I've saved you some time rather than wasted it, as I usually do [:D]

DG

Ya know, DG-- sometimes I'm convinced this forum is our only lifeline to mastering this library. Your suggestions are certainly appreciated and they continue to help. I only hope to do the same.

@dpcon said:

JWL,
Is there a note chase function in DP? I always have to scroll back befor a note on to get a keyswitch to trigger.

Thanks.

Hi,

Note Event Chasing is enabled under the Setup menu in DP.

Best,

Maya

Thanks, Maya. My event chasing feature was active, and some events do indeed chase. It's just that the keyswitches have been doing odd things in spite of the default settings in DP. Dove-tailing the keyswitches helps get around this quirk.