Rme multiface 2 as main and running a focusrite saffire pro with wordclock sync. next to it.

One condition that can make the transport non-responsive is if the audio interface, for whatever reason, is not making render requests. I've seen this happen (rarely) with my RME UCX. If it happens again, check that there isn't a clocking issue or something like that.

One condition that can make the transport non-responsive is if the audio interface, for whatever reason, is not making render requests. I've seen this happen (rarely) with my RME UCX. If it happens again, check that there isn't a clocking issue or something like that.

This is a new controller type that combines sequence programming from a MIDI keyboard, and general purpose remote control, from a "Knobs & Buttons" MIDI controller. This combination allows you to configure a flexible, performance-friendly controller setup whereby you use the keyboard for entering and modifying sequences, and the knobs-n-buttons controller for navigation, setting record modes, and adjusting other parameters. You can use two separate MIDI controllers -- say a Launch Control and a MIDI keyboard, or a single keyboard controller provided that it has some assignable knobs and buttons. The controller config also allows you to setup MIDI Messages to turn controller LEDs on and off for additional feeedback when using controllers with illuminated buttons.

The Performance Controller setup uses a "stack at a time" editing style, unlike, say, the Mixer Ctlr which uses a "bank of stacks at a time" approach. Navigation from the controller is by simple next and previous stack buttons. The Numerology UI will follow as you navigate between stacks, and the controller will follow as you bring up different stacks in the UI. Controller actions related to sequencer recording and ops are automatically directed to the first NoteSequencer in each stack that you navigate to.

[NOTE: This is an intentional limitation in the initial implementation: Only the first NoteSequencer in each
stack can be edited.]

INPUT MODES:

Up to 5 buttons can be mapped to control how MIDI from the attached MIDI keyboard is handled:
- Off : No activity
- Step Record : The sequencer runs while you program notes in step record mode.
- Realtime Record : The sequencer runs in realtime record mode.
- Transpose : The sequence is transposed as you play the keyboard.
- Thru : Notes you play on the keyboard are added to the MIDI output of the sequencer.

These modes are mutually exclusive (a.k.a. 'radio buttons'), so as you select one, any other mode is deactivated. If you select one of these modes a 2nd time, it self-deactivates. This means that when using a controller that has illuminated buttons, you can reliably not map the "Off" mode and just map and of the 4 other modes that you need.

SEQUENCER OPS:

You can map buttons on the controller to any of the following operations:

Clear Sequence : zeroes out the entire sequence at once
Erase : erases parts of a sequence as it plays
Invert : invert the current sequence
Mute : mute the current sequence
Double : double the length of the current pattern.
Shift Left : shift all steps left by one
Shift Right : shift all steps right by one
Generate : generate a new pattern
EvolveX, Y, Z : evolve the current pattern
Prev & Next Preset : move to the previous or next preset
Dup Preset : duplicate the current preset

STACK AND GLOBAL CONTROLS:

You can setup up to 16 Stack-level knobs and buttons that you can assign to parameters on a per-stack basis. These mappings are made using the usual "MIDI learn" approach: control-click on a param, pick "Learn MIDI CC", then twist the knob or press the button you want to map. A big difference from traditional MIDI learn in Numerology is that these "stack level" mappings can change as you navigate through the stacks your project.

For instance, you can assign Knob 1 to sequencer rate for a MonoNote in Stack 1, sequencer rate (or length, or direction etc) for a PolyNote in Stack 2, and so on.

You can also setup another 16 knobs and buttons as "Global". These controls work just like the traditional method: Their mapping stays the same regardless of which stack you are looking. at.

SETTING UP A PERFORMANCE CONTROLLER

- First bring up the Controller Setup dialog (in the Numerology app menu), and use the action menu (lower-left corner) to create a new Performance Controller.

- If you are using separate keyboard and "knobs-&-buttons" controllers, pick the knobs-&-buttons MIDI ports for input and output for "Ctls", and pick the Keyboard MIDI input and Output for "Keys". You only need to select the MIDI Output ports for these controllers if it has some sort of MIDI feedback dispay -- like the button LEDs on the Launch Control.

- If you are using a controller that has both a keyboard and some knobs and buttons, pick that controller for both Ctls and Keys.

You can can also just setup a knobs-n-buttons controller without a keyboard, but then you will not have access to sequence programming.

Now setup the mappings for your knobs-n-buttons controller. They fall into 7 groups, as listed below. Other than the Stack and Global Knob groups, all of these should map to buttons that are setup to transmit either MIDI CCs or Notes. Unless you have a really big controller, you will probably map only a subset of these controls -- perhaps just navigation, some input modes, and a few stack knobs and buttons.

- Navigation: Prev Stack, Next Stack. There is always a 'current stack' for the Perf Ctlr. These buttons allow you to change stacks, and will wrap around when you read the last (or first) stack in your project.

- Ops: Clear, Erase, Invert and Mute. Each will trigger the matching operation.

- Stack Knobs 1-16 : map to knobs where you will want the mapping to change as you navigate from one stack to another.

- Stack Buttons 1-16 : as above, but for buttons.

- Global Knobs 1-16 : map to knobs where you do *not* want the mapping to change per-stack.

- Global Buttons 1-16 : as above, but for buttons.

Controller Feedback

All of the 'button-y' controls you can map have a pair of text fields where you can enter short MIDI messages that are sent to the controller when that button is triggered 'on' or 'off'. For instance, with Novation's Launch Control, you can set up these fields to light up the LEDs for each button
on the controller.

To use this feature, you will need to know a bit about MIDI, as well as how your controller responds to MIDI messages. The format for the fields is two-digit hexadecimal with spaces inbetween, like this: 80 33 7F

Hi Jim,

Let say I have setup all the parameters in the performance controller.
Then, I have saved it .
If I clic on the minus, I am loosing all my work right ?
I am concern about being able to save only the controllers parameters.
Do you see my point ?

Let say I have setup all the parameters in the performance controller.
Then, I have saved it .
If I clic on the minus, I am loosing all my work right ?
I am concern about being able to save only the controllers parameters.
Do you see my point ?

I was thinking the same thing. In my quest to get the performance controller to stop double repeating steps I've been trying various combos of controllers/keys but it's laborious to have to delete the controller to just reassign it again if I decide to use it later. It would be great to be able to save user made presets of specific controllers to be recalled and chosen depending on your current configuration.

Also, my issue with the launchpad spitting out midi on the scene buttons now is making my project too unpredictable. Would I run into any problems if I reinstalled the previous build?

This is a new controller type that combines sequence programming from a MIDI keyboard, and general purpose remote control, from a "Knobs & Buttons" MIDI controller. This combination allows you to configure a flexible, performance-friendly controller setup whereby you use the keyboard for entering and modifying sequences, and the knobs-n-buttons controller for navigation, setting record modes, and adjusting other parameters. You can use two separate MIDI controllers -- say a Launch Control and a MIDI keyboard, or a single keyboard controller provided that it has some assignable knobs and buttons. The controller config also allows you to setup MIDI Messages to turn controller LEDs on and off for additional feeedback when using controllers with illuminated buttons.

The Performance Controller setup uses a "stack at a time" editing style, unlike, say, the Mixer Ctlr which uses a "bank of stacks at a time" approach. Navigation from the controller is by simple next and previous stack buttons. The Numerology UI will follow as you navigate between stacks, and the controller will follow as you bring up different stacks in the UI. Controller actions related to sequencer recording and ops are automatically directed to the first NoteSequencer in each stack that you navigate to.

[NOTE: This is an intentional limitation in the initial implementation: Only the first NoteSequencer in each
stack can be edited.]

INPUT MODES:

Up to 5 buttons can be mapped to control how MIDI from the attached MIDI keyboard is handled:
- Off : No activity
- Step Record : The sequencer runs while you program notes in step record mode.
- Realtime Record : The sequencer runs in realtime record mode.
- Transpose : The sequence is transposed as you play the keyboard.
- Thru : Notes you play on the keyboard are added to the MIDI output of the sequencer.

These modes are mutually exclusive (a.k.a. 'radio buttons'), so as you select one, any other mode is deactivated. If you select one of these modes a 2nd time, it self-deactivates. This means that when using a controller that has illuminated buttons, you can reliably not map the "Off" mode and just map and of the 4 other modes that you need.

SEQUENCER OPS:

You can map buttons on the controller to any of the following operations:

Clear Sequence : zeroes out the entire sequence at once
Erase : erases parts of a sequence as it plays
Invert : invert the current sequence
Mute : mute the current sequence
Double : double the length of the current pattern.
Shift Left : shift all steps left by one
Shift Right : shift all steps right by one
Generate : generate a new pattern
EvolveX, Y, Z : evolve the current pattern
Prev & Next Preset : move to the previous or next preset
Dup Preset : duplicate the current preset

STACK AND GLOBAL CONTROLS:

You can setup up to 16 Stack-level knobs and buttons that you can assign to parameters on a per-stack basis. These mappings are made using the usual "MIDI learn" approach: control-click on a param, pick "Learn MIDI CC", then twist the knob or press the button you want to map. A big difference from traditional MIDI learn in Numerology is that these "stack level" mappings can change as you navigate through the stacks your project.

For instance, you can assign Knob 1 to sequencer rate for a MonoNote in Stack 1, sequencer rate (or length, or direction etc) for a PolyNote in Stack 2, and so on.

You can also setup another 16 knobs and buttons as "Global". These controls work just like the traditional method: Their mapping stays the same regardless of which stack you are looking. at.

SETTING UP A PERFORMANCE CONTROLLER

- First bring up the Controller Setup dialog (in the Numerology app menu), and use the action menu (lower-left corner) to create a new Performance Controller.

- If you are using separate keyboard and "knobs-&-buttons" controllers, pick the knobs-&-buttons MIDI ports for input and output for "Ctls", and pick the Keyboard MIDI input and Output for "Keys". You only need to select the MIDI Output ports for these controllers if it has some sort of MIDI feedback dispay -- like the button LEDs on the Launch Control.

- If you are using a controller that has both a keyboard and some knobs and buttons, pick that controller for both Ctls and Keys.

You can can also just setup a knobs-n-buttons controller without a keyboard, but then you will not have access to sequence programming.

Now setup the mappings for your knobs-n-buttons controller. They fall into 7 groups, as listed below. Other than the Stack and Global Knob groups, all of these should map to buttons that are setup to transmit either MIDI CCs or Notes. Unless you have a really big controller, you will probably map only a subset of these controls -- perhaps just navigation, some input modes, and a few stack knobs and buttons.

- Navigation: Prev Stack, Next Stack. There is always a 'current stack' for the Perf Ctlr. These buttons allow you to change stacks, and will wrap around when you read the last (or first) stack in your project.

- Ops: Clear, Erase, Invert and Mute. Each will trigger the matching operation.

- Stack Knobs 1-16 : map to knobs where you will want the mapping to change as you navigate from one stack to another.

- Stack Buttons 1-16 : as above, but for buttons.

- Global Knobs 1-16 : map to knobs where you do *not* want the mapping to change per-stack.

- Global Buttons 1-16 : as above, but for buttons.

Controller Feedback

All of the 'button-y' controls you can map have a pair of text fields where you can enter short MIDI messages that are sent to the controller when that button is triggered 'on' or 'off'. For instance, with Novation's Launch Control, you can set up these fields to light up the LEDs for each button
on the controller.

To use this feature, you will need to know a bit about MIDI, as well as how your controller responds to MIDI messages. The format for the fields is two-digit hexadecimal with spaces inbetween, like this: 80 33 7F

Again, this performance controller is awesome. I was dreaming of building my own controller on my iPad for Numerology and my synths. I am building it with TouchOsc the way I want . It will be much more easy to push on buttons that using the mouse all the time.
I am thrilled and happy
Thanks Jim

Hi Jim,
Let say I have setup all the parameters in the performance controller.
Then, I have saved it .
If I clic on the minus, I am loosing all my work right ?

Yes, If you click minus and confirm you want to delete that setup,
the settings for it are deleted -- more on how they are stored below.

Quote:

Originally Posted by Aramis

I am concern about being able to save only the controllers parameters.
Do you see my point ?

The settings for all controller setups are stored in individual files in
<your home dir>/Music/Five12/Controller Setups

Numerology will read those files on startup, and then write them as they are created or changed. So if you want, you can move files in and out of that directory to add/remove setups for various controllers as you see fit.