Now that you all have finally installed clyphX
I want to introduce you to one of its most amazing functions:
The ClyphX Snap action:
What it does is, it records all the parameter settings in your devices, the track mixer controls or the play state upon triggering, and writes them into the name of the clip the Snap action was triggered from. When you re-trigger this clip it will always set the parameters/states back to where they were, when you recorded them.
As with most clyphX actions it can be directed to act only upon the things you want it to act upon.
So in essence it stores a preset within Live that spans, if you desire, multiple devices over multiple tracks along with the Volume and Send parameters.
Upon re-triggering this clip, this exact state will be recalled. No matter what you did in the mean time.
Because the preset (or Snap in clyphX lingo) is written into the clip name and is recalled from there, this function can only be used with x-clips, housed within your set. You can have as many different Snaps in your set as you want to house the Snap clips for.
To try it out, go ahead and name a clip in your set:
When you trigger this clip it will record the parameters of all devices ("Devall") on Track 1 ("1/" ) and the values of its mixer parameters ("Mix").
Within the brackets you can write the name that you want to give to your preset. As mentioned the brackets themselves are important, as they are what tells clyphX that this is a x-clip, instead of a regular clip without clyphX actions.
When you trigger the x-clip the first time, the name of the clip will change to something like:
Code: Select all
[PresetName] || {u'1-Drum Rack Push': [[0.85000....... <-- Followed by a very long list of values.
Now do some changes on your devices on Track 1 and its Mixer settings and then re-trigger this clip.
You will see that all your parameters snap back to the values you had set when you first recorded that Snap.
You can also use different modifiers to store different things:
The clyphX manual states:
DEV: Store the settings of the first Device on the Track.
DEVx: Store the settings of the Device where x is the number of the Device.
Example: SNAP DEV2, SNAP DEV3
DEVx-y: Store the settings of the Devices in the specified range where x is the Device number to start with and y is the Device number to end with. To operate on all Devices, specify ALL.
Example: SNAP DEV1-4, SNAP DEV2-5, SNAP DEVALL
MIX: Store the Volume, Pan and Sends settings of the Track.
MIX+: Store the Volume, Pan, Sends, Mute, Solo and Crossfade settings of the Track.
MIX-: Store the Volume, Pan, Mute, Solo and Crossfade settings of the Track.
PLAY: Store the playing status of the Track. This does not apply to Group Tracks, Return Tracks or the Master Track.
The Snap Action can store all parameters that are accessible to Lives API. That generally means, device parameters that can also be Midi assigned (Light up blue when you hit the Midi button in Lives upper right corner).
Changes to parameters that are not, like for example Samplers Loop parameters, will not be recalled.
When you use plug-ins, then only parameters that are configured will be stored/recalled. At the maximum 128 parameters.
I found it useful to make the change to the Options.txt that makes Live automatically configure all vst parameters upon loading it. (-_PluginAutoPopulateThreshold=-1)
How to change/make an Options.txt is described elsewhere.
In the next installment I will show you how to transition smoothly between your different Snaps, taking as much time for this, as you specify. Even in beats, synced to Lives tempo, if you so desire.
I will also show you how you can use a Midi controller to morph between two presets in your own time.
If you don't want to wait that long, all of this is described very well in the clyphx manual, go and give it a thorough read.
Have fun