Hi I have a few workarounds that might help you.

======================================================================================================================
Method 1 (This method will allow you to assign each of up to 23 buttons on your control surface to a matrix cell.)
======================================================================================================================

1 Create a 12 X 12 matrix. Assign both X & Y to the same controller (a controller you won't be using for anything else.)
2 Arrange all Matrix control bars for the X axis to fit into the left half of the X-axis grid.
3 Arrange all Matrix control bars for the y axis to fit into the right half of the Y-axis grid.
4 Be sure the right most control bar in the X axis is to the left of the left most control bar in the y axis.

5.Place the articulations you want to use in the top row and in the last column of the matrix. Now simply assign each button on your midi control surface to send a controller value using the controller you assigned in step 1.

The approximate values will be something like the ones below. The values will vary slightly depending on the spacing of the matrix control bars.

Button 1 on your control surface = Send CCx value of 0 (Selects Matrix cell A1)
Button 2 on your control surface = Send CCx value of 3 (Selects Matrix cell A2)
Button 3 on your control surface = Send CCx value of 7(Selects Matrix cell A3)
Button 4 on your control surface = Send CCx value of 13(Selects Matrix cell A4)
Button 5 on your control surface = Send CCx value of 22(Selects Matrix cell A5)
Button 6 on your control surface = Send CCx value of 26(Selects Matrix cell A6)
Button 7 on your control surface = Send CCx value of 36(Selects Matrix cell A7)
etc...
Button 11 on your control surface = Send CCx value of 57(Selects Matrix cell A11)
Button 12 on your control surface = Send CCx value of 62(Selects Matrix cell A12)

At this point, you will be at the end of the right edge of the matrix and the
numeric values will start moving through the Y axis so the direction is down
the control.
Button 13 on your control surface = Send CCx value of 70(Selects Matrix cell B12)
Button 14 on your control surface = Send CCx value of 82(Selects Matrix cell C12)
etc

How it works...
When you press buttons that send lower numeric values, the y axis remain static at 0
so as you increment numerically the cells move left to right in the same row,
because of the arrangement of the matrix control bars.

When you reach the middle numeric values, those values effect the y axis while X axis remain static at a
value of about 62... again this because of how the matrix control bars are arranged.

This method will waste most of the matrix cells, but who cares. You will be able to select one articulation per button.
...up to 23

I've been using this method for some time. Once it is setup it's seamless.

I worked this out so I could play with my right hand and change articulation easily and intuitively with my left hand.

If this is confusing, I could insert a screen shot of the matrix X/Y axis grid, if someone would kindly tell how to insert a graphic image.

==================================================================================
Method 2 - This will allow you use up to 128 buttons to select 128 articulations
=================================================================================
Simply add up to 128 matrices to a preset.
Make each matrix consist of only one cell.
Assign each button on your midi controller to send a program change.


Button 1 send prog change 1 to select matrix 1.
Button 2 send prog change 2 to select matrix 2.
Button 3 send prog change 3 to select matrix 3.
etc

I would be interested to hear feedback on these methods. Are they flawed in some way that I have overlooked?

Maybe VI pro 2 will make it easier

[quote=Andrew Nerness]I agree - it would be cool to be able to use a controller like the Akai apc40, ableton novation launchpad, or Livid Ohm64 and assign a cell to each pad. But I have not found a way to link each pad to each cell in VI Pro. Does anyone else know how?

I use a Lemur to do this.  And the advantage of a Lemur vs other controllers of this type, is that you can label each button with the corresponding articulation.

D Dunn

The best solution would be the ability to assign a program change number to each matrix cell, since nearly all control surface buttons can send program change commands.I am hoping this will be implemented at some point in VI Pro.

@Composer321 said:

The best solution would be the ability to assign a program change number to each matrix cell, since nearly all control surface buttons can send program change commands.I am hoping this will be implemented at some point in VI Pro.

 

That's only a good solution if you use program changes (which I don't), and as VST3 doesn't support program changes it is also a short term solution for many users.

DG

Thanks for pointing out that VST3 will not support program changes.

Will VI Pro 2 have a way to implement changing matrix cells with a button press from a controller or do you have any suggestions on how to do this more elegantly than my crude workarounds? Thank you

[quote=Composer321]Thanks for pointing out that VST3 will not support program changes.

You can do this already with VI Pro.  You can choose to have matrixes respond to program change.  Or any cc.  (I believe that's correct)

But I am currently using prg change.

D Dunn

@ddunn said:

[quote=Composer321]Thanks for pointing out that VST3 will not support program changes.

You can do this already with VI Pro.  You can choose to have matrixes respond to program change.  Or any cc.  (I believe that's correct)

But I am currently using prg change.

D Dunn

 

 Yes, but as I mentioned, if you happen to host VI Pro in VE Pro, then Program Changes won't work in the VST3 version.

What we really need is for VSL, NI and all the other sample developers to get on with the whole VST3 thing, so that us poor users can find out what the change from Program Change to Program List actually means. [:P]

DG

@ddunn said:

[quote=Composer321]Thanks for pointing out that VST3 will not support program changes.

You can do this already with VI Pro.  You can choose to have matrixes respond to program change.  Or any cc.  (I believe that's correct)

But I am currently using prg change.

D Dunn

Hi DDunn

Thanks for responding. I am aware that matrices can be changed with a Program change command. That's not what I want to do. I'm sorry if I wasn't clear.

I want to change cells within a matrix, not entire matrices and be able to do it with a single button press on my Zero SL control surface.