Ableton Forum

Yeah, with live.remote taking over the parameters, the automation won't work.

You could replace the Live.remote's with live.objects. But that'll make a lot of undo history and may be slower than live.remote. However, I haven't tested the speeds yet, so I'm just repeating what I heard.
This device is designed for performance. If you want to use it for creation you'll need to tweak it a little. I'll whip you up a live.object version this weekend if I don't forget. Its just changing 1 bpatcher that needs to happen.

Your turning out to be quite the miracle worker!

Didn't think it was possible. I read a thread about this without a solution on cycling forums, so assumed it wouldnt work!!!

Thanks!

concrete_cow wrote:Your turning out to be quite the miracle worker!

Didn't think it was possible. I read a thread about this without a solution on cycling forums, so assumed it wouldnt work!!!

Thanks!

Actually I have to test if the modulation is recorded. I know it doesn't disable the modulation lane..
Hold on, the buttons are live.object based.

Yeah it works. The only downside is that the Clip Mapper records automation of itself too, so it needs to be deleted afterwards. I can't disable that because disabling modulation would also disable MIDI Learn.

OMG !!!

I wouldn't worry about knocking up the live.object version it simply won't respond fast enough to be satisfactory....

Finally got back online so off to download the latest and report back!!

Cheers
D

S4racen wrote:I wouldn't worry about knocking up the live.object version it simply won't respond fast enough to be satisfactory....

Finally got back online so off to download the latest and report back!!

Cheers
D

Even if live.object useage is laggy I think it's potentially still very useful. I think update speed, etc. are not as important during the creative as when performing live. What do you think?

Looking forward to your feedback, hope it works as well for you as it has here!

Btw.. gonna put the new BYU mix online tonight hopefully now it's close to finish. Could you check it out D and let me know what you think? Bit of a mixed bag of hiphop/funk/disco/techhouse/pop!

Ok i see your point, i suppose my challenge was when i had lots of live objects pointing at the same thing at the same time so i got really bad feedback with early incarnations of Isotonik.....

Just finishing patching the clip mapper into it...

Can i ask bjorn how you solved the problem as i have the same thing with one of my rack devices and value bleed (although mine happens everytime without fail taking the old values into the new device!)

Will definitely download.... And congrats on the marlena shaw gig!

Cheers
D

S4racen wrote:
Can i ask bjorn how you solved the problem as i have the same thing with one of my rack devices and value bleed (although mine happens everytime without fail taking the old values into the new device!)

Will definitely download.... And congrats on the marlena shaw gig!

Cheers
D

In my case I was actually transmitting the called value to live.remote, which caused the bleeding through.
I had to rewire the bpatcher of the knobs so that didn't happen anymore.

It's perfect! I love it......

Mad props..... Now i've got close to my perfect set up for the APC40!!

Cheers
D

concrete_cow wrote:Your turning out to be quite the miracle worker!

Didn't think it was possible. I read a thread about this without a solution on cycling forums, so assumed it wouldnt work!!!

Thanks!

Give this one a go: http://covops.dreamhosters.com/uploads/ ... d.amxd.zip

This version uses the objects instead of the remotes. Let us know how performance works out

You are a legend! Thanks so much

Can it just be hot swapped in?

I'll let you know how it works out later tonight...

concrete_cow wrote:You are a legend! Thanks so much

Can it just be hot swapped in?

I'll let you know how it works out later tonight...

Yep, totally hot-swappable.

Hi Bjorn,

Just finished testing it with a fresh build of my template. Think Darren may unfortunately be right about the object update rate. It seems that clip mapper knob controls behave normally if the knob is turned slowly, but move it quickly and control becomes completely unpredictable and jumps to seemingly random values. Furthermore the midi controller become out of sync with the actual values. I guess it's not useable for recording a live set, but I'm sure it would be handy in some scenarios. Thanks for trying!

Any idea if the undo history can be turned off somehow? Wondering if this would have a positive impact on the performance using objects?

Cheers
Sunil

concrete_cow wrote:Hi Bjorn,

Just finished testing it with a fresh build of my template. Think Darren may unfortunately be right about the object update rate. It seems that clip mapper knob controls behave normally if the knob is turned slowly, but move it quickly and control becomes completely unpredictable and jumps to seemingly random values. Furthermore the midi controller become out of sync with the actual values. I guess it's not useable for recording a live set, but I'm sure it would be handy in some scenarios. Thanks for trying!

Any idea if the undo history can be turned off somehow? Wondering if this would have a positive impact on the performance using objects?

Cheers
Sunil

No problem. Now we know for sure that remote is the way to go. You can't turn off the undo history, but thats not the problem I think. live.dial movements go into undo history too.