Button Mode
With a Button Mode Block it's possible to change how many steps a button has to take to move from its minimum value to its maximum.
With a Button Mode Block it's possible to change how many steps a button has to take to move from its minimum value to its maximum.
The Color Block changes the color the LED of your choice when this action runs.
Comment blocks are used to create comments in Editor for creating notes and general comments. These comments are saved onto Grid when the configuration is stored.
Element Name Blocks are used to name the Control Element configuration in Grid Editor. These names are stored with the configuration and therefore are saved in both Presets or when Store is pressed.
By default encoders are set to absolute mode. In this mode, encoders act like potentiometers, with a MIDI value range 0-127. With the help of Encoder Mode action, you can change the encoding to relative.
By default endless are set to absolute mode. In this mode, encoders act like potentiometers, with a MIDI value range 0-127. With the help of Encoder Mode action, you can change the encoding to relative.
The For Action can be set with incremental steps in a loop.
The Gamepad Button block allows Grid to send gamepad button press messages to the host computer.
The Gamepad Joystick block allows Grid to send gamepad joystick axis messages to the host computer.
Global Variables Block allows you to define Global Variables in a nice Block format, instead of doing them in the Code Block.
The If Block serves as the most basic logic operator for Grid Editor. When using such a Block you're able to create additional conditions for running actions in case of an Event trigger.
The Intensity Block changes the light intensity the LED of your choice when this action runs.
With the use of a Keyboard Block Grid is able to send keystrokes to the host computer as a physical keyboard would.
Local Variables Block allows you to define Local Variables in a nice Block format, instead of creating them in the Code Block.
Lookup redistributes received values to variables
Actions under each Event in Grid are called the Action Chain.
How many Actions can I add to an Action Chain?
Out-of-the-box MIDI values sent by Grid and why.
A Page is the user facing 'memory slot' of the Grid hardware.
Saving only part of a configuration as a Preset.
Listen to MIDI messages on MIDI Rx and set values on control elements.
Discover Endless possibilities within the new TEK2.
How to create visual feedback for Grid and the how the defaults work.
This Mouse Button Block allows Grid to send mouse click messages to the host computer.
This Mouse Move Block allows Grid to send mouse move messages to the host computer, letting you send even scrollwheel messages.
This Potmeter Mode Block is able to make a potentiometer more sensitive by increasing the value range it's working with or by chaning the bit depth of the values the analog signal is translated to.
Self Variables Block allows you to define Self Variables in a nice Block format, instead of doing them in the Code Block.
The Start Animation Block allows the LED intensity to change over time, making the LED blink in some form or another.
This Block simply stops an already playing animation on an LED layer.
The Timer Event, located under System Events is even more special than their UI Event type counterparts, since it has no Control Element Specific trigger by default. They can still be triggered by any kind of Timer Start Action Block (or the function), from anywhere by calling timer number X, where X is the number of control elements you have on the module.
The Timer Event, is a special event because its trigger is tied to no specific control element.
The Timer Start Block allows you to create a timed trigger for the Timer Event. These Blocks can be used for both the global and the ui versions of the Timer Event.
The Timer Stop Block allows you to end a Timer early, before its clock would run out, triggering a Timer Event earlier.
This event is triggered when the utility button is pressed on the side of the module.