ControllerMate building blocks are triggered by controls on devices or MIDI messages. Each type of building block performs a small task. Building blocks can be combined to perform complex functions.
ControllerMate now includes more than 70 types of building blocks!
Some building blocks respond directly to controls on devices. Others perform logic, math, or timing. Yet other blocks trigger activity on ControllerMate's virtual mouse or keyboard, perform AppleScripts, open files, or launch applications. The possibilities are virtually limitless.
Driver configurations can be used to change the default behavior of a keyboard or mouse that uses ControllerMate's driver.
All buttons on a keyboard have some default function or another. Most are useful, some are not. A driver configuration allows one button on a keyboard act like another, or can turn a button off completely. Buttons that have been turned off can still be used to trigger building blocks.
A driver configuration for a mouse can include a custom acceleration curve. This curve can be one of the standard curves, a standard curve with an adjusted speed or sensitivity, or an entirely custom curve created point by point.
Multiple configurations can be created for the same keyboard or mouse — use building blocks to control when a configuration is active.
MIDI messages can now trigger building blocks just as easily as buttons on a joystick, mouse, or keypad. MIDI notes, controller values, or patch changes can be used.
ControllerMate can also create and send MIDI messages through a virtual MIDI source. This allows generic input devices to be used to control applications that listen to ControllerMate's virtual MIDI source.
ControllerMate can create virtual mouse, tablet, and joystick devices that are controlled by ControllerMate programming. The virtual devices are seen by most other applications just as though they were actual devices.
Every move that a virtual device makes is controlled using ControllerMate's building blocks and driver configurations.
ControllerMate includes a helper application that runs in the background, monitors the attached controllers, and performs the current programming when the ControllerMate application is not running.
After you have finished setting up your building blocks and driver configurations, quit the ControllerMate application and the background application takes over. No graphics, no user interface, no unnecessary processor cycles.
ControllerMate is compatible with many types of devices and can perform a wide variety of tasks. Give ControllerMate a try to find out if it will work for you, risk free, and with no time limit.
When ControllerMate is used without registration there will be a limit of 10 building blocks that generate output (keyboard or mouse activity, MIDI messages, AppleScripts, etc.). Building blocks that respond to controls or MIDI messages, perfom logic, math, or timing can be created in unlimited numbers. This should give you a good opportunity to find out how ControllerMate works and if it will work for you.
ControllerMate v4.10.3 provides more helpful information when its driver is not loaded while running on macOS 10.13 High Sierra. This should help users navigate the new High Sierra system extension approval process more quickly.
ControllerMate v4.10.3 also handles Bluetooth LE devices in the same manner as earlier Bluetooth devices. This should improve compatibility with newer Bluetooth devices.
ControllerMate v4.10.2 improves the compatibility of keyboard-related building blocks (Keystrokes, Single Key, Text) with some applications when running on macOS 10.12 Sierra. Applications that did not respond to keyboard activity that was indicated by the system's Keyboard Viewer should now respond properly.
ControllerMate v4.10.1 improves the compatibility of ControllerMate's background helper with macOS 10.12 Sierra. This update addresses potential differences in behavior that may occur when the helper alone is running (as compared to when the ControllerMate application is running), or differences in behavior of the helper application when it launches automatically compared to when it is stopped and then restarted manually.
Examples of behavior that this update addresses are building blocks that may not respond quickly to buttons, and delays between control activity and the ControllerMate outputs that they trigger.
This update should allow the helper to run with the same priority, and achieve the same performance, as the ControllerMate application.
Copyright © 2005 — 2017 OrderedBytes. All rights reserved.