Device Details
Overview
| Name | Version: | REACT - remote access tool 1.0.1 |
| Author: | NoraPatches |
| Device Type: | Audio Effect |
| Description: | REACT is a Max 4 Live utility device that allows not only mapping to certain parameters, but also features two mapping modes; remote and macro. In remote mode the mapping to the parameter is exclusive and after the mapping, nothing else is able to adjust the mapped parameter other than the Macro dial. In macro mode the mapping to the parameter is non-exclusive and after the mapping the original parameter is still adjustable on its own – these changes are reflected on the Macro dial. The plugin comes in three instances; REACT8, REACT16t and REACT16w. What's new? ('23.08.29.) v1.0.0 - fixed issue with device not saving mapping targets after closing/reopening Live Set Main features 2 Mapping modes; remote (exclusive) and macro (non-exclusive) Target adjustable range in remote mode 8/16 dials 3 variations, tray and window GUI available How to use: Place REACT8/16w/16t on any Track in Ableton Live. Map to any mappable parameter you like. Control mapped parameters with Macro Dials. |
Details
| Live Version Used: | 11.2.7 |
| Max Version Used: | 8.5.5 |
| Date Added: | Aug 27 2023 00:07:09 |
| Date Last Updated: | Aug 29 2023 18:14:01 |
| Downloads: | 0 |
| Website: | https://norapatches.com/devices/react/ |
| ⓘ License: | Commercial |
Average Rating
Log in to rate this device |
-n/a- |
Comments
I should add... Ableton Live 11.3.10, Max 8.5.5, MacBook Pro 2013 running Mojave 10.14.6
Posted on April 02 2024 by RoamingProfile |
Report Issue
Login to comment on this device.
Browse the full library
Mapping seems to work OK for stock Ableton devices, eg Operator. But if I try and map to a M4L device, eg Auxture's Filter 1 cutoff, the mapping either adheres to the selection (rarely) or a different, nearby knob is mapped instead. Very frustrating!
I've then tried mapping using a different device, eg LFO or MAP8 from Max For Live Essentials pack, and mapping functions as designed. So there's definitely something not quite right in the mapping functionality of your REACT_ (and npLFOseq) devices.