Clip Mapper is a M4L Device that allows the user to assign 16 parameters to a clip and recall those parameters when an assigned clip is triggered.
The 8 knobs and 8 buttons on this device can be controlled using MIDI Learn or Automap. The knobs and buttons can be assigned to any device on any track. You could for example have all your bass control parameters assigned to Clip 2 on Track 2 and all your beat control parameters assigned to Clip 1 on Track 1. By triggering either of those clips, the chosen parameters will be available to control with the Clip Mapper Device.
This allows you to free up many knobs and buttons on your physical controllers. And you don't need to memorize how to recall the correct controller presets during a live situation.
The device is free and may be edited, shared, improved, dismantled or destroyed.
You are not allowed to re-sell the device or re-release it under an identical name. Linking must be done to this page and not to the files, as the files and this page will be updated for each new version. Currently it comes as 2 versions. One for MIDI Tracks and one for audio tracks.
- The device only works with 64 Tracks and 1000 scenes. This isn't a fixed limit, expanding the Track limit involves nothing more than a bit of copying and pasting and changing some numbers.
- Moving the Clip Mapper after mapping clips to it may not work properly. If you lose your data, place it back where it originally was or reload the set.
This hopefully solves one of my main problems related to mapping all 16 knobs on my APC using a single button press. Can you confirm if this is possible - i.e. i want to be able to press the pan button on the APC and have that automatically map all 16 knobs on my controller. It looks like your patch supports only 8 rotary controls per instance, or can it support 16 knobs? If not, can I use two of these things in parrallel?
It is possible to use multiple of these devices in a Live set to support more knobs and buttons.
I'm not sure what the pan button on the APC this, but this device is designed to work with clips. Its contents can be modified to do other things though.
this looks great but the select device dropbox is dead for me,i cant choose anything here.an example.i have operator in my set but select device wont open up to show this.
The clips don't store the data automatically.
With the version you currently have, you have to create an external text file. And once created, you can read its contents and check if it updates when you add clips and parameters.
Yeah, I realized some issues might pop up and that change will be made. So I refrained from making a video that in the end will cause more confusion than it clears things up.
For example, the next version will not need these text files. That being said, it should work with the provided instructions. But I understand the written form doesn't work for everybody. I have a whole section on this site devoted to that fact.
I'm a little swamped this week, but as soon as the new year hits I'll have the time to polish this thing up.
A lot of the work I did for this will be useful for other similar types of devices. Like storing value snapshots and stuff like that. So you'll definitely hear a lot more from this project in the near future.
I'm looking for a way to send increments of 1 bpm to change the clip tempo. any advice?
I was thinking the process would be
- warp
- consolidate
- set first warp marker
- map parameter to the warp marker bpm
Here's my dilemma:
'm looking for a more elegant way to switch up the tempo on a clip playing through Ms. Pinky. The problem is when I adjust the pitch on the turntable to beatmatch to some live audio, and then switch from vinyl control to the original clip the tempo doesn't follow the pitch on the table.
Or maybe have the clip tempo just follow the main tempo.
How Can I map with APC40 + clip mapper VST instruments? I want to play with APC clips - clips in Groove agent and Darbuka. When I want to select VST, only options is clip mapper 0.8.?? I`m new-green with APC.
The save function does not work for me...i have Win 7 64-bit, Live 8.1.1, Max 5.1.3 and this amazing Clip Mapper 0.9.6, every time i load a saved project Live got crashed??
I have tryed in Windows XP and same results...every time i load my saved project...Live got crashed.
Only thing is that i have Max 5.1.3 demo/trial version...could that be the problem?
About that Max demo/trial...
Now i have full version of Max for Live 5.1.3 and latest Live beta.
I have lot of other patches from web that are working great! Even the save function is working in each one of them! The only problem is Clip Mapper, it always crash my Live when i try to Save or Load project or Save Max/Clip Mapper?? I have tried every version of Clip Mapper and even on other PC's. But it allways finished crashed??
Regardless to that Clip Mapper is one of the best patches and really great idea!
I'm not sure if I can help you here. Live crashing is definitely Ableton's department. I'd help if I could, but as this is the first I hear of it. I'm not sure what exactly the problem is and if my patch has anything to do with it.
Please send your crash packs to beta@ableton.com , they will hopefully make sure it won't crash in the future.
Is wanted to use at in audio effect chain.
is it possible to get acces of the parameters of the devices in the chain? i mean not only the eight macro controls? that would be great for my setup
Unfortunately this is currently not possible.
Its a limitation in the Live API. We can't access devices inside racks.
But as soon as that is possible, this device will be updated for it.
I like it really useful and solves many problems, I'm guessing select mode only works if your wanting to go to a clip in the same track as the device, in your vid for example if you wanted to change the parameters in ABL with out triggering it if you go across with the mouse of cursor keys it selects the track and shows you the devices etc.... so you would have to wait till the end of the loop and re-trigger it in the devices normal mode, not really a problem and a small price to pay for a top device.
Also when I put it into learn mode it erases any previous stored parameters for that clip, is that right?
Live 8.1.1, Max 5.1.3, OSX
The selection mode becomes useful if you use the Up/Down arrows + Track selection to select clips. For example Faderfox controllers are designed to work like that. You could select clips with the knob and trigger them with the buttons.
Enabling Learn mode does clear the display of all parameters, but whatever is assigned to a clip stays assigned. If you want to add/change parameters of a clip, trigger it while in Learn mode.
Lastly, if clicking on a clip doesn't seem to do anything. Trigger another clip first. The device is designed to not to call the parameters if the same clip is triggered twice.
I've got it all working fine, I've got all the various parameters stored for each clip etc... when I launch a clip it recalls the various parameter states but titles don't change.
Say I have 2 tracks track 1 has delay track 2 has flanger. Map and store the delay to clip, map and store flanger to clip, when I launch either clip the dials and values change fine relevant to the plugin state but the titles, dry/wet etc never change.
Yes, that is a feature. It allows you to have clips with like only 4 parameters assigned to blend in with controls of a previous clip.
Its designed so you can mix things without having to add more buttons and dials.
Yeah it makes sense when you think about it, I might have a think about a way to implement some sort of colour coding so you could see at a glance where the parameters split between clips, probably not necessary though.
I will check this out, but other than reporting it if I can reproduce it, there is not much I can do about Live crashing. Ableton is currently heavily busy trying to make Live more stable though.
I love your clip mapper, thanks for the great idea.
Unfortunately, it is not working in my setup.
I did it a hundred times, with different plugins, different versions of clip mapper (latest is 1.0), in different sequence, but get very arbitrary results.
In 90% of the cases, the parameters are not saved, in 10% they are, but in a rather random fashion. I could not find out any regularities on when they are saved.
Anyone with the same issues have it solved somehow?
I tried all varieties of start and stop, before and after save. To be honest, I think there is a bug in my system. Do you have skype, paypal and half an hour? This is very important for me, so i need to get it solved.
Can you reproduce this problem in a small set? Or does it only happen in a big project?
If it occurs in a small set, please send it to b at thecovertoperators.org and provide any steps needed to reproduce. I'll check it out and see if I can spot the bug.
thanks a lot for your help on how to set up clip mapper. As we found out, I was expecting clip mapper to do something it does not (yet).
I was looking for a device which would save not only the selection of parameters, but also the VALUE of those parameters directly to the clip.
This would vastly increase the useability of the clip mapper.
I started modifying your patches, combining clip mapper and Pattrstorage, but got stuck because i could just map one parameter at a time, and multiple tracks need some work anyway.
Would you be interested in working on such a device?
This looks great, I have a couple questions:
1. Are the clip mappings tied to the audio that's in the slot, or are they like dummy clips and you can switch different audio files in the session slots and they parameters will be mapped?
2. Will this allow me to mess with the parameters and then get back to the default settings easily?
Pardon if these have already been answered I read the Ableton thread a few weeks ago. thanks
