AUTOMAT - recall settings by clipnames
automat lets you recall any device settings in your live-set...
- Type
- MIDI Effect
- Author
- bennniii
- Version
- 1.3
- License
- AttributionNonCommercialShareAlike
- Live version
- 9.1.2
- Max version
- 6.1.7
- Downloads
- 4,902
- Updated
- 2014-06-17
Description
automat lets you recall any device settings in your live-set by naming your clip according to its presets.
this can be very much simpler than using envelopes and is often ideal when e.g. switching to a next "part" of a song.
1) map parameters (up to 12)
2) adjust your 12 parameters (on up to 12 presets)
3) recall these presets via clipname (e.g. "1 anyname") and/or map them to your controller
features:
- when first mapped, automat uses your current parameter/pot values.
- works on all mappable parameters throughout your live-set
- values can now be freely copied and pasted
- works! even if you rearrange tracks, devices, etc
check the quick video (of an older version). it's simple & fun! (:
* * * * * * * * * * * * * *
v1.3
- you can now copy & paste anywhere
- added more presets and 2 banks of parameters (press little arrow)
- tricked the live api a little and it's faster now. yes!
- added mappability to presets
v1.1
- fixed automat not saving settings on first layer
Comments (15)
any wishes for a new version, anyone?
if not more!
Thanks for an awesome device!!!!!
will be placing more macros on different "layers" so the interface stays tidy.
I would not mind to have a wide device with 16 x 8 parameters.
Thx!
i've filled your wishlist and added a little more besides that.
- copy paste from anywhere to anywhere,
- 12 parameters for 12 macros (press little arrow)
- speed-enhancement
- made 12 presets mappable to controllers (now you can really do fun stuff!)
tell me if there's more.
Great work!
I was wondering if there is an alternative approach to the "live.remote" object for mapping parameters.
As "live.remote" mapping mechanism locks the parameter (grey out in live), it could not be controlled any longer by other controller devices.
I imagine "live.remote" as a way to control, at audio rate, the value of a device parameter.
On the other hand "live.observer" runs at Max data rate (less than audio rate, so less resource I guess) and could observe and set value of a device parameter.
I thought that would be enough to store (observe) and recall (set value) a list of devices parameters value.
I may have miss something along the way as "live.remote" seems most commonly used.
I am looking to a similar solution as Kapture, with a possibility to store devices parameters value within a clip (same way as you did).
Thanks!