Logic Pro 9 virtual instrument bypass via external controller

Eduà

Logician
Hi all,
is there anyone that could explain me how to assign a bypass function of a virtual instrument in Logic Pro 9 to an external midi controller knob or button? That would help me saving a lot of cpu while playing live, without having to use the trackpad and looking at the computer monitor. As for the inserts of the channel strip I know how to do the thing - using midi learn in Controller Assignments tab - but I can't figure it out if trying to obtain the same thing on the virtual instrument itself.

All the Best,
Eduà

P.S.
One may argue why I am not using MainStage for playing live. The reason is that it crashes too easily. When I buy a new Mac I will try MainStage 3, but as for now I stay with Logic 9.
 

Eduà

Logician
What proposes Ivan is really interesting, but as for now I keep following this tutorial, since we start and have to go through it.
Peter,
on the Nektar p6 I can always decide whether the button should be in toggle mode or not and I see there are buttons, like the nine ones under the nine faders, that light up when active. So, if you think toggle mode should be better it is a way I can handle.
They work fine in momentary mode as well.
The pads does not light up and I noticed that I can only choose Latch mode on/off. If latch mode is on, when I hit a pad a second time its value turn to 0, otherwise, latch mode off keeps remembering the last value and does not return to 0. This if I look at the keyboard screen. The keyboard screen always shows the current value (0-127) of the item used. In the "Switch" layer, the value of the pads in Latch mode off, when released, is 0, so I think it is all fine.
As I told you I would have liked to do this work of CC assignments with the nanoKey, but unfortunately the Korg Kontrol Editor does not allow such an option. With the nanoPad, yes, it is possible. By now I will keep all on the Nektar p6.
Going to the creation of the patch I am encountering some problems in steps 5.1.4 and 5.2.8, so I am blocked at this last point. In the first one I don manage to set the output of the "Panic" button to "Control", it does not pop out. In this last one I face the same issue when trying toast the output to "Sysex". May you know by what is caused?
 
Upvote 0

Peter Ostry

Administrator
Staff member
I guess you are talking about some kind of Logic "Main Stage" emulation
No, rather a simple sound switching tool that uses less CPU than Mainstage.


What I found is the Midi Key Switcher Environment tool (the main part of the Jammier).
I just re-packed a Demo version so you can try it.
Thanks, I tried it. Works good but does not deactivate unused channelstrips and does not allow sound layers of more than one channelstrip by default.

In this thread (following the original question) we simply want to turn channelstrips on and off. Every channelstrip that is "on" should play and everything "off" must be completely dead (no CPU usage). Keyboard split and Pitch/Modulation/Sustain routing are additions that were not requested, I just find that they are a great help for playing multiple synths.
 
Upvote 0

Eduà

Logician
The problem I mentioned is solved. I "˜ll post a message in a few hours to confirm that I went through the end of this part of the tutorial.
 
Upvote 0

Peter Ostry

Administrator
Staff member
on the Nektar p6 I can always decide whether the button should be in toggle mode or not and I see there are buttons, like the nine ones under the nine faders, that light up when active. So, if you think toggle mode should be better it is a way I can handle.
Toggle mode with optical feedback (light) is definitely better. Everything that shows you the actual situation directly where you switch, is better than momentary buttons. As I said before, even mechanical switches would be better.

With this idea you are going to change the whole system. For toggle action we have to modify the patch, even the input section. However, let's do it because toggle is better for your playing and it makes the whole patch less complicated.


The pads does not light up and I noticed that I can only choose Latch mode on/off.
If the pads do not light, forget them for toggling. A toggle button without a light is worse than a momentary button. You always have to check it's state somewhere. The are only useful for clearly audible functions like "boost" or "dim".


As I told you I would have liked to do this work of CC assignments with the nanoKey, but unfortunately the Korg Kontrol Editor does not allow such an option. With the nanoPad, yes, it is possible. By now I will keep all on the Nektar p6.
Ok for the 9 Nektar toggle buttons.

But the pads of the nanoPAD do not light, correct? Consider the nanoKONTROL. You may not use the faders and knobs (you can remove their caps if you want), but the hardware has 18 buttons with lights and they can toggle. The unit has 4 banks as usual in the nano series, with just 2 banks you have what our switching patch supports.


--------------------

Going to the creation of the patch I am encountering some problems in steps 5.1.4 and 5.2.8, so I am blocked at this last point. In the first one I don manage to set the output of the "Panic" button to "Control", it does not pop out. In this last one I face the same issue when trying toast the output to "Sysex". May you know by what is caused?
Step 5.1.4 is a Cable Switcher
5.1.4. Create a Cable Switcher "Select Strip"
In the Inspector, set its Input to "Program, Channel 16, Range 0 32".
This means:
Create a Cable Switcher by the menu "New -> Fader -> Specials -> Cable Switcher" and set it's name to "Select Strip".

Inspector settings as shown in this screen shot:

------------------------------

Step 5.2.8 is the SysEx button called "Panic"

Not sure what you mean, the output of the button itself should not be "Control". It should be set to "Sysex...":

Then the Sysex Editor should pop up. If not, doubleclick the word "Sysex..." in the Inspector.

Just to avoid confusion: We don't deal with Sysex (System Exclusive) data. It's just the name of that button function in Logic. It allows to send different data types and just one of them is Sysex.

Inside the button we generate CC data. If you have problems to do it, you may not click in the right order. In a fresh and empty Editor, first activate the button "Create":

Afterwards click on "Controller" to generate one line of data:

The rest is copy/paste in the special manner I described. If you cannot do it exactly the same way, don't worry. As long as you manage to generate a full set of numbers (0-127) with value 0 and for 16 channels, you are ok. There are various ways to get this. The special sort order does not matter, it just helps.

Working with this kind of button (or Fader) is a bit tedious but it is worth the effort. It is one of the most powerful objects of the Environment.

--------------------

Does the above solve your problems or did you mean something else?
 
Upvote 0

Eduà

Logician
All right, I went successfully through the creation of the input section.
Just a thing: you tells that the last line should be:
Last line: 16 1 1 127 P-Press 16 G8 0
but I obtain
Last line: 16 1 1 128 P-Press 16 G8 0
with "128" for every last line of 16 channels. I think that this is correct, since you said that we should obtain 2048 lines. Am I wrong?
When talking of the nanoKey I omitted a detail: it is Korg nanoKey 2. Actually the first model of Korg nanoKey allows to send midi cc, but unfortunately I haven't it with me right now.
So, when talking of the Korg nanoKontrol, I think you mean the first version, not nanoKontrol 2, which I don't know if allows scene (bank) switching, don't you?
As a matter of fact, at the moment I am not living in my country, Italy, but I found myself in Brazil, where prices for musical instruments and computer music are awful, almost the double than in Europe. But I'll check tomorrow.
 
Upvote 0

Peter Ostry

Administrator
Staff member
Just a thing: you tells that the last line should be:
Last line: 16 1 1 127 P-Press 16 G8 0
but I obtain
Last line: 16 1 1 128 P-Press 16 G8 0
That's ok. Mine shows also 128 ;)

And I made a second failure. In the last post I told you to create CCs in the Sysex editor for the Panic button. But we use P-Press and you did it right.

---

We go for toggle buttons now, ok?
I'll modify the input section for that.

---

So, when talking of the Korg nanoKontrol, I think you mean the first version, not nanoKontrol 2, which I don't know if allows scene (bank) switching, don't you?
I have the old one here. Checked the nanoKONTROL 2 in the Korg Website and in my Korg editor and you are right, it does not support banks. But it has 24 buttons in the main area and this is enough. You can have "All Strips Off" and "Panic" on two other buttons, for example in the transport section.
 
Upvote 0

Peter Ostry

Administrator
Staff member
We go for toggle buttons now, ok?
I'll modify the input section for that.
Done. We have to change 2 transformers.

In the first row, where our "switch" messages come in, rename the second transformer to "make Select" and delete the third transformer:


The renamed transformer is basically ok, just change the Mode to "Copy ... (reverse order)" and remove the filter for the value:


Create a new transformer, insert it between the other one and the Cable Switcher, name it "make Fader" and configure it as shown in the screenshot:

No more modifications.

--------------------

On the keyboard:

"All Strips Off" and "Panic" buttons stay in momentary mode and you can leave them on your pads for now.

Configure the first 4 of your 9 buttons to work in toggle mode. They should send CC 85-88, "Off" is 0 and "On" is something greater than 0.

--------------------

Test the modified patch. Your 4 buttons should switch the Cable Switcher to 1, 2, 3, 4 and send their high and low values through it, to the monitor object. MIDI channel is always 16, number is always 1, values come from the buttons:


Everything ok?
Then you are ready and we can start to make the macro for the channelstrips, which does the real job.
 
Upvote 0

Peter Ostry

Administrator
Staff member
Good. Don't install the Control Surface software for the device in Logic. This would turn your nanoKONTROL into a fully featured DAW controller ;) but unable to do what you plan.

You may of course try the control surface mode and if you like it we can easily use the original CCs of the nanoKONTROL. You would then switch between the two modes using the global function "Bypass all Control Surfaces". And if you don't like the control surface at all, just remove it from the setup window and from the Logic application folder or wherever it got installed.
 
Upvote 0

Eduà

Logician
i downloaded the Control Surface software but I won't install it the for now, just to avoid confusion; thank you for the suggestion.
As for now the nanoKontrol is working fine: I have assigned CC 85-86-87-88 to the first four Solo buttons, in toggle mode.
 
Upvote 0

Peter Ostry

Administrator
Staff member
Here we go ...

Since you work now with a dedicated controller, it would not be necessary to choose MIDI numbers as carefully as I have done it for your keyboard, but I suggest to leave them as they are. You can change the numbers and associated filters in the input section later if you want.

----------

Very first action:

On the "Click & Ports" layer we connected your incoming keyboard to our patch. Check this connection, Logic may have lost or changed it after you added your new nanoKONTROL.

Connect both, the Keyboard and the Controller, to our patch. Both must go the same way. Just cable both ports to the Cable Switcher.

Remember to check this layer whenever you want to play. Best is to always connect both devices before you start Logic. Then the proper connections should remain. Hopefully.

----------

Small modification to the input section:

The button and function "All Strips Off" were thought for a system with momentary buttons and are no longer necessary. The opposite is true, if you press this button, the controller will not automatically turn all lights off. You have to turn every lighting button off yourself to set controller and Logic to the same state. We do not want this, therefore we remove it from our input section. I have already removed this function from the macro we are going to build afterwards.

First, grab the cable that goes to the transformer "ex CC 119 ..." and drag it directly to the transformer "ex CC 120 ...". Then delete the two orphan transformers in the second row.

This will give you something like in the screenshot below.

Done.
 
Upvote 0

Peter Ostry

Administrator
Staff member
Now we are going to make the macro which we have to put in front of each channelstrip. Later you will just duplicate it as often as you need it, up to the max. 32 channelstrips the patch supports at the moment.

6. Interface for strip activity, key split and channel split

Strip activity:
This is just a button that shows you if a strip is on or off. You can also click on it to switch the strip.

Key split:
Two numerical faders let you define a keyboard range by setting the lowest and the highest note that should go to a certain channelstrip. This way you can play multiple instruments in multiple and even overlapping keyboard ranges. But you cannot route ModWheel, PitchWheel and Sustain differently to the individual ranges because the key pitch is not a valid criteria to route these controller events.

Channel split:
For channel splits you configure your keyboard to send notes on different channels. The interface part consists of a numerical fader to set the allowed MIDI channel and 3 buttons to route ModWheel, PitchWheel and Sustain to the instrument or not. Very handy for example to play a pad and solo notes, where you want to forbid modulation and pitchbend for the range of the pad.

Please note:
After building this whole patch you may be able to combine key- and channelsplits yourself, just in Logic. At the input you can set certain note ranges to certain MIDI channels and voilà, best of both worlds, without configuring the keyboard.

6.1 Building the interface

Create 4 buttons and 3 faders of type "Numerical 3". The first button is rather wide, that's the activity display and can also switch the channelstrip. Next row are 2 number boxes to set the low and high notes for the accepted key range. The third row has a numberbox to choose teh MIDI channel and 3 small buttons to route ModWheel, PitchWheel and Sustain.

My arrangement is a suggestion, the colors are not for beauty but rather to see the cabling better.



6.2 Configuring the interface


6.2.1 Button "Strip on/off"
The button reacts only to a certain input message.


6.2.2 Numberbox "Lo Key"
We would rather like to display key names instead of key numbers, but Logic does not support this and the workaround - many text boxes with 128 key names each - use too much memory.

The output Meta 125 sets the lower range condition of a following transformer.

6.2.3 Numberbox "Hi Key"
The output Meta 124 sets the upper range condition of a following transformer.


6.2.4 Numberbox "CH"


6.2.5 Buttons "MW, PW, SU"
They route ModWheel, PitchWheel and Sustain. All 3 buttons have the same output setting and range.

I've set the style "As Button 3" for those. Ugly, but the state is easy to see. We don't have good looking interface elements in the Environment, almost all are from the very first Logic versions where the whole program was built with them.

----------

Three hints for working in the Environment:

Fine tune the width of elements similarly as you do it with Arrange regions, by the key command "Nudge Event/Event length ... by Nudge Value".

To set an element to the same size as another one, copy the original, activate the target element and use right-click (ctrl+click), then select "Apply buffer template to -> Size" from the contextual menu.

ctrl+C is the default key command to hide/show the cables and element outlets.
 
Upvote 0

Peter Ostry

Administrator
Staff member
7. The macro patch

This is going a bit tough now. I am not keen of making too many screenshots and document everything step by step, so I'll just give you the configuration data for each element. We can of course talk about parts if you run into problems.

If I supply only a few parameters for an object, other parameters are left at their default values.

For transformers, "Mode" is the menu at the top of the editor, "Conditions" are the upper row and "Operations" are the lower row. I will always supply the whole rows, regardless how many values are set.

If I write for example:
Mode: Top cable
Conditions: = Fader, = Channel, All, >= 1
Operations: Fix Meta, Fix 1, Fix 125, Thru

I mean this:

Try to make the object arrangement close to mine. It may look weird but it will allow you to understand the cabling even months later.

Important points:

The key- and channel-split-interface we built before must be at the top and the leftmost element because this is what we want to display in the final macro.

Since the objects are unordered from the view of Logic, we have to use dedicated input and output objects. The type of such objects does not matter (I like to use the "Ornament" object) but the names do matter:
Macro-In
Macro-Out
The names are case-sensitive, if you write them in another way the macro does not work.

The whole macro patch:



7.1 Cable Switchers "Pitch", "Mod" and "Sust"
Input: Program
Channel: 16
Range: 0 1


7.2 Transformer "prepare Ch"
Operations: Fix Meta, Fix 1, Fix 125, Sub 1

7.3 Transformer "allow Ch"
Mode: Apply operation and filter
Conditions: All,
= 16, All, All

7.4 Transformer "PitchWheel"
Mode: Top cable
Conditions: = Pitchbend, All, All, All

7.5 Transformer "ModWheel"
Mode: Top cable
Conditions: = Control, All, = 1, All

7.6 Transformer "Sustain"
Mode: Top cable
Conditions: = Control, All, = 64, All

7.7 Transformer "ex notes off"
Mode: Top cable
Conditions: = P-Press, All, All, All

7.8 Transformer "ex Notes"
Mode: Top cable
Conditions: = P-Press, All, All, All

7.9 Transformer "Notes inside"
Mode: Apply operation and filter
Conditions: All, All, Inside, All
(The two inside values do not matter because they get set by the two numberboxes of the key-split interface.)

7.10 Transformer "is ON"
Mode: Top cable
Conditions: = All, All, All, >= 1
Operations: Fix Meta, Fix 1, Fix 99, Fix 0

7.11 Transformer "is OFF"
Operations: Fix Meta, Fix 1, Fix 99, Fix 0

7.12 Sysex button "strip on"

7.13 Sysex button "strip off"

Duplicate your "Panic" button from the input section and add some lines at the top:


Then add a single line at the end, after the last P-Press:

It is important to have this line at the end because it contains the command to deactivate the software instrument. The instrument must receive all note-offs before we switch it off.

7.14 Transformer "CC -> Fader"
Mode: Top cable
Conditions: = Control, All, All, All
Operations: Fix Fader, Thru, Thru, Thru

7.15 Transformer "P-Press -> Notes"
Mode: Apply operation and filter
Conditions: = P-Press, All, All, All
Operations: Fix Note, Thru, Thru, Thru

7.16 Transformer "switch"
Mode: Top cable
Conditions: = Fader, = 16, = 1, All

7.17 Quick first test
Cable a monitor to the "Macro-Out" object. Hold the alt key down and click+hold at the outlet of the monitor. This opens a selction menu where you select "Mixer -> Instrument 1" to route the monitor to your first instrument channelstrip. Alternatively you can drag a cable across Environment windows but the alt+click+hold method is better.

Now click on the green button "Strip on/off" in the key- and channel-split-interface. When the button goes on, the outgoing monitor should show a couple of Fader events. When the button goes off, the monitor shows the last note-offs and a single Fader event.

Ok?

Then look at your first channelstrip where you linked the monitor to. It should also go and off. All plugins, the instrument and the mute button.

If this does not happen, you got to find the bug ...

7.17 Test the macro patch with the input section
Connect the two last monitors of your input section to the "Macro-In" object like shown the screenshot below:




  1. Try the 4 buttons on your controller, which you have set to toggle action. All 4 buttons should switch your first channelstrip on and off.
  2. Set the key-split interface to Lo Key 0 and Hi Key 127.
  3. Set the channel numberbox to the channel of your keyboard and make sure that the 3 small buttons are off.
  4. Play on the keyboard, the notes should appear in the last monitor and you should hear your instrument.
  5. Play on the keyboard and move the ModWheel and the PitchWheel and try your sustain pedal. Everything should work.
  6. Move some faders and knobs on the keyboard and on the nanoKONTROL. You should see them in the outgoing monitor.
  7. Set the Hi Key number to 59 and play on the keyboard. Notes below C3 should sound, higher notes not. Then the key split works.
  8. In the channel-split interface, switch the 3 small buttons on. You can still play, but Modwheel, Pitchwheel and Sustain stop to work.
  9. Set the channel numberbox to something else and you should hear beautiful silence because the MIDI channel of the keyboard is no longer accepted by the patch.
  10. Finally, set the split interface back to default. Lo Key 0, Hi Key 127, Channel to your keyboard channel, 3 small buttons off.
If not everything of the above works, you got to find the bug ;)

If everythings works, I can only say "Great!" :thmbup:. We can make the macro and the cabling for the first 4 channelstrips. Peanuts.
 
Upvote 0

Peter Ostry

Administrator
Staff member
8. Macros and cabling

8.1 Making the macro

  1. Remove the last monitor and the two cables that are connected to "Macro-In".
  2. Activate all of the now isolated macro patch, choose "New Macro" from the menu.
  3. When you see the macro, go to the inspector and disable all checkboxes.
  4. Make the macro as small as possible, just to let you configure the split interface.
  5. Name the macro "Strip 1"
Now it looks like this:


8.2 Assigning macros to channelstrips

alt+drag the macro to make 3 more copies in a row. Activate all four and click on "Multiple Selection" in the Inspector. You see the name "Strip 1". Just hit Enter and let Logic renumber your macros. This happens automatically if the last character of a name is a number. You have now 4 macros, named Strip 1 to Strip 4.

alt+click+hold on each macro's outlet and select the appropriate instrument channelstrip from the contextual menu.


8.3 Connecting the input section


Remove the last two monitors from the input section. Now the Cable Switcher "Select Strip" shows only one free outlet. Cable it to your first macro. Cable the emerging next outlet to the next macro and so on, until all 4 macros have their connections.



Do the same with the Ornament object "to all strips" at the end of the input section. The name says it all - cable it to every macro.

Your whole patch looks like this:



Just make sure that all macro interfaces are properly set to the full key range and your keyboard channel (not like in my screenshots).

If all the tests before were ok, this last step should work instantly and you can freeely play with 4 instruments, switch them and play sound layers with and without keyboard splits.

--------------------

9 Expanding to more channelstrips

I guess you can imagine how to involve more than 4 channelstrips?

  1. Configure more buttons in the range CC 85-116 for toggle action on your controller.
  2. Duplicate the macros as often as you want, up to 32.
  3. Assign the new macros to their channelstrips.
  4. Cable the next outlets of the Cable Switcher "Select Strips" to the new macros.
  5. Cable the Ornament at the end of the input sections to all new macros.
  6. That's it, nothing more to do.
Below is the version for 24 channelstrips, which utilizes all three button rows of your nanoKONTROL.



--------------------

10. Other input CCs

In case you want to change the CC numbers accepted by the patch: All input processing is done in the input section. The macros don't care about numbers. But you have to manage the correct order of numbers. In other words, the Cable Switcher must switch from 1 to {x} to switch the correct channelstrips.

If you want to change the Panic CC only, just set the conditions (and the name) of the transformer "ex 120 ..." to some other cool number and you are ok.
 
Upvote 0

Eduà

Logician
I began now to build the macro, but I stopped at point 7.13.
The images show values from

101 1 1 1 P-press 1 C-2 0

to

116 1 1 128 P-press 16 G8 0

whereas the original Panic Button features values from

1 1 1 1 P-press 1 C-2 0

to

16 1 1 1 P-press 1 C-2 0

Please, could you give some explanations?

One more thing.
At 7.10 you wrote:
"Conditions: = All, All, All, >= 1"

In this case the "=" is something I don't have to care about, right?
 
Upvote 0

Peter Ostry

Administrator
Staff member
I began now to build the macro, but I stopped at point 7.13.
The images show values from
101 1 1 1 P-press 1 C-2 0
to
116 1 1 128 P-press 16 G8 0

whereas the original Panic Button features values from
1 1 1 1 P-press 1 C-2 0
to
16 1 1 1 P-press 1 C-2 0

Please, could you give some explanations?
7.13 Sysex button "strip off"
Maybe I copied the renumbered data from the new button to the existing Panic Button.

Please: In the new button, with only the "panic" data inside, select all and scroll the first column up with your mouse until the first line shows 101 in the first column. The position area is used for the sort order. If the "panic events" start with 101 in this button, you can easily add some lines before them.


whereas the original Panic Button features values from
1 1 1 1 P-press 1 C-2 0
to
16 1 1 1 P-press 1 C-2 0
I think you mean
1 1 1 1 P-press 1 C-2 0
to
16 1 1 128 P-press 1 G-8 0

If this is the case, your Panic Button is ok and you can leave it as it is.

In the Panic Button the sort order has no functional meaning because there are no other events. The order made it just easier to generate all these data.


One more thing.
At 7.10 you wrote:
"Conditions: = All, All, All, >= 1"
In this case the "=" is something I don't have to care about, right?
Right.
"Conditions: All, All, All, >= 1"
 
Upvote 0

Eduà

Logician
Yes, it was
16 1 1 128 P-press 1 G-8 0

I just copied it without thinking.
All I mentioned above is now ok, thank you.
Another thing:
In the image above point 7.1, next to cable switchers "Pitch", "Mod" and "Sust" there are three objects: are they Ornament objects?
I will be back on "the thing" in a few hours and tell you if did everything right.
 
Upvote 0

Peter Ostry

Administrator
Staff member
In the image above point 7.1, next to cable switchers "Pitch", "Mod" and "Sust" there are three objects: are they Ornament objects?
Yes. I use Ornament objects to collect or distribute MIDI events, or - in this case - only to make the cabling better visible.

Hint:
If you want an ornament object without a visible name, type a couple of spaces. Makes it easier to grab the object with the mouse.
 
Upvote 0

Eduà

Logician
Step 7.17
I did not cable the four instruments yet because yesterday, when testing the macro patch with the input section I noticed as following:
The modulation wheel of the Panorama p6 is not always working with all the virtual instruments, but I think it is a (new) problem of the keyboard with Logic. With Kontakt standalone it works fine and if in Logic I set the p6 mod wheel CC value to 11, for example, it works. I thought it was a problem of coexistence with the other controller, the nanoKontrol, where CC 2 works good, but it seems not to be the case. I see that the outgoing monitor is not showing any mod wheel message from the p6, even in other Logic projects, if CC number is set to 1, whereas CC1 activity from nanoKontrol is showed. The p6 mod wheel on CC1 is not working with Logic instruments (even if some days ago it was) but is working with NI BII4 and others. That to say that it seem not to be a consequence of the work we are doing in the environment. I don't know, it may be start to work again normally in the next days.
So, going ahead with the test:
Korg nanoKontrol is working. I had to change the CC number of the eighth fader from 7 to 15, because it moved the Cable Shifter in "Click & Ports" to 2 and both the hardwares lost the control of the project.
Panorama p6 is working, with that exception I pointed out. Faders activity is not shown in the outgoing monitor but, since the p6 memorized the settings of a previous project, the first 4 faders are already linked to the first 4 Logic tracks, controlling the volume with CC numbers 40, 41, 42, 43. If I set the value to 11, then activity messages are shown in the monitor. Value 7 activity is never shown.

I do not manage to let the modifications on Hi Key (and Lo Key) get results, the keyboard is still playing all the notes from C-2 to G8.
Same for Ch, keyboard is still playing and for PW, MW and Su.
This is a screenshot of the "Click & Ports" section, if it maybe useful for you to check.

Click & Ports.jpg

The "Switch" Section. As you may see cables colors overlap in different way than in your example.

Switch.jpg

Checking all we did until step 7.17, I saw that for step 5.2.8 in Sysex window you tell to create a Poly Pressure event but, when I mentioned that I faced an issue in step 5.2.8, while re-explaining the thing you tell to create a Controller event. I kept Poly Pressure, but which one is correct?
In these screenshots:
The "Panic" button settings and the final part of "Panic" Sysex events.

Panic Settings.png

I corrected now the input from "Control" to "Program".

Panic Sysex.png

I know that may be some mistake in an object setting, as for now I checked and all seems to be ok, as you instructed.
I'll check the forum later or tomorrow, then until sunday night or monday I won't be able to work on it.

Best Regards
 
Upvote 0
Top