Ableton Forum

A new Max update (5.1.3) is available at the Cycling site: http://cycling74.com/downloads/

With this update installed, data should be recalled properly when you load a set. No need to open the editor or do a special action.

I'll try to have a video ready by the weekend along with a 1.0 version after some more testing.

- Bjorn

Good news!! Bjorn, saw your twit.

Do you think any bugfixes are necessary on 0.9.3? Playing live on Saturday and really want to use it in my set

hoffman2k wrote:A new Max update (5.1.3) is available at the Cycling site: http://cycling74.com/downloads/

With this update installed, data should be recalled properly when you load a set. No need to open the editor or do a special action.

I'll try to have a video ready by the weekend along with a 1.0 version after some more testing.

- Bjorn

Bring it on,.... looking forwards to this, need to get my head out of my own tinkering for a while!!

Cheers
D

concrete_cow wrote:Good news!! Bjorn, saw your twit.

Do you think any bugfixes are necessary on 0.9.3? Playing live on Saturday and really want to use it in my set

Though question. With Live being the way it is these days, I hope my patch will be the least of your worries.

The fixes that are coming are proper sorting of automap parameters (again) and some sort of autosave feature. Nothing crucial, just making it more user-friendly.

Haven't found any other bugs yet, but I'm still amazed everything worked in the end

Though question. With Live being the way it is these days, I hope my patch will be the least of your worries.

Tell me about it... having to keep my set pretty basic to be honest and have avoided integrating complex M4L patches to avoid CPU spikes and crashes. Really want to integrate yours and Darren Cowley's patches, but i'm riding around 50-60% CPU at peak, which is far enough from my confort zone as it is! Hopefully, Ableton/C74 will sort their acts out soon so that we can enjoy patches like yours as they were designed

Will have a quick play tonight to see if my set can cope!

Just need a way to map Clip Mapper knobs to sends/non rack devices now Will have a look around and might see if I can adapt your patch

Cheers mate!
Sunil

concrete_cow wrote:

Though question. With Live being the way it is these days, I hope my patch will be the least of your worries.

Tell me about it... having to keep my set pretty basic to be honest and have avoided integrating complex M4L patches to avoid CPU spikes and crashes. Really want to integrate yours and Darren Cowley's patches, but i'm riding around 50-60% CPU at peak, which is far enough from my confort zone as it is! Hopefully, Ableton/C74 will sort their acts out soon so that we can enjoy patches like yours as they were designed

Will have a quick play tonight to see if my set can cope!

Just need a way to map Clip Mapper knobs to sends/non rack devices now Will have a look around and might see if I can adapt your patch

Cheers mate!
Sunil

Actually I already have a solution that doesn't require any hacking to the Clip Mapper.
You just need a device that controls things like Sends or anything else the API can control. The parameters exposed from that device will be available in Clip Mapper. So for example you could have a device that controls the tempo over the API with a live.dial, the dial will be available in the Clip Mapper. I haven't gotten around to such a thing yet, but with the paths being absolute it shouldn't be that hard for anybody to whip up.

New version (0.9.4) up: http://covops.dreamhosters.com/uploads/ ... 4.amxd.zip

- Fixed Automap order of parameters.

- Added Autosave feature. This just means that no special actions are required to store data into the device to be recalled on set load. The device will save its state after you added a Clip or when you stop the transport. If you move devices around, just start and stop the transport before you save the set.

- Clips can only be stored while in Learn Mode. It makes sense and just works more reliably once you get used to it.

Its still working lovely over here. Unless anybody has any issues to report, this might be 1.0.

FANTASTIC! Was just testing v0.93 and you drop this All seems to work as described and the CPU seems to be far better now... Good stuff!

Cheers
Sunil

Maybe i'm not supposed to do what i'm doing - 2 of the clips I map to contain common mappings. I.e. clip A contains beat repeat for channel 1, and clip 2 contains the same 2 knobs but from channel 1/2/3/4... does that make sense? Thus, can the clips contain references to the same controls without causing any issues or must the same controls never be mapped across different clips?

Also, after saving the buggy set, it didn't recall my old mappings... any idea Bjorn?

Thanks
Sunil

I just tested without having overlapping knob mappings across clips but its still not saving when I re-open the set for some reason

concrete_cow wrote:Maybe i'm not supposed to do what i'm doing - 2 of the clips I map to contain common mappings. I.e. clip A contains beat repeat for channel 1, and clip 2 contains the same 2 knobs but from channel 1/2/3/4... does that make sense? Thus, can the clips contain references to the same controls without causing any issues or must the same controls never be mapped across different clips?

It should work. You could have 1 clip with 16 parameters and another with 4 parameters. If you trigger the second clip after the first, you'll have a mixed preset with 12 parameters of the first clip and 4 of the second. Mapping to the same thing multiple times from different presets shouldn't be an issue.

concrete_cow wrote:Also, after saving the buggy set, it didn't recall my old mappings... any idea Bjorn?

Thanks
Sunil

You have updated to 5.1.3, right?

I'm not sure how well you know Max, but you could send the message "storagewindow" to pattrstorage to see which contents should be stored.
I've also found, if you loaded a few sets containing this data and nothing is loaded - it loads properly if you restart Live.

Just had a thought... rather nubishly, when I first began creating a DJ template, I created a 'Sets' folder under the live documents folder, i.e. '/Users/XXX/Ableton Live 8/Sets'... And I noticed that the Ableton directory is displayed in finder like a Project folder would be, but it hasn't caused problems in the past so I've left it as it is... Assuming the different versions of the DJ Template Sets i'm saving are under the same Project folder, would they all share the same Clip Mapper settings, and thus confuse Clip Mapper?

concrete_cow wrote:Just had a thought... rather nubishly, when I first began creating a DJ template, I created a 'Sets' folder under the live documents folder, i.e. '/Users/XXX/Ableton Live 8/Sets'... And I noticed that the Ableton directory is displayed in finder like a Project folder would be, but it hasn't caused problems in the past so I've left it as it is... Assuming the different versions of the DJ Template Sets i'm saving are under the same Project folder, would they all share the same Clip Mapper settings, and thus confuse Clip Mapper?

Since the data is stored with the .als file itself, I can't see how it could cause conflicts.
However, loading various sets after each other without restarting Live might cause some problems.
I have no technical explanation for it, but I assume M4L doesn't like the same instance of pattrstorage over various sets and the memory needs to be cleansed by restarting (Max for) Live.

Ahhh, i see... afaik i don't think the max has been opening a separate process outside of live if I open up the patch editor. My set has a tendancy to crash on occasion when opening a new set or closing an open one, so i've gotten into the habit of restarting live anyway. I'll have another play on Sunday and see if i can strip right back and do some more testing...

cheers,
Sunil

New Update (0.9.5): http://covops.dreamhosters.com/uploads/ ... 5.amxd.zip

- Fixed bug where the last 6 buttons aren't recalled properly after reloading a set.

While working on the video I uncovered this that requires an update. Regarding the video, sorry about the delay. I forgot it was Carnival and its pretty much the only day its socially acceptable to wander around town drunk, dressed as a giant mouse.
I'm working on it today.

- Bjorn