MeldaProduction

ofersmi · Post by **ofersmi** » Mon Nov 06, 2017 2:10 pm

I have the same issue, only with melda plugins, live 9, windows 10.
Any news about this? is it melda or live?

Ofer

peejay123 · Post by **peejay123** » Mon Nov 06, 2017 6:29 pm

Check this thread for a solution:

viewtopic.php?p=6828485

You basically group the plugin into a rack and then map the automation to a macro.

If you copy the automation before mapping it to the macro, you can paste it into the macro automation lane, but once mapped you won't be able to copy it.

This is quite a quick and easy workaround.

Good luck!

jmg8 · Post by **jmg8** » Mon Nov 06, 2017 7:59 pm

peejay123 wrote:Check this thread for a solution:

viewtopic.php?p=6828485

You basically group the plugin into a rack and then map the automation to a macro.

If you copy the automation before mapping it to the macro, you can paste it into the macro automation lane, but once mapped you won't be able to copy it.

This is quite a quick and easy workaround.

Good luck!

Can't believe I didn't figure this work around out.
You have saved my life, thanks!

For the record Ableton know about it and are working on a fix, albeit very slowly. The bug is still present in Live 10.

peejay123 · Post by **peejay123** » Thu Nov 09, 2017 11:21 pm

Glad to hear that

I hope ableton fix it!

MeldaProduction · Post by **MeldaProduction** » Fri Nov 17, 2017 4:09 pm

Found the problem - for some reason Ableton Live disables automation when updateDisplay() is called, which is a call that lets the host know that the parameter names might have changed, so pretty much something unrelated to processing and if it was, it's no excuse to disable the automation. I asked Live AGAIN for support... but this is just sad, period... I mean they are postponing this for like a year? Or is it 2?

mabxit · Post by **mabxit** » Wed Dec 20, 2017 10:04 pm

This issue has been a pain for some time... I just posted in the Ableton forum about it:

https://forum.ableton.com/viewtopic.php?f=1&t=228612

Would love to have this fixed.

MeldaProduction · Post by **MeldaProduction** » Sat Dec 23, 2017 9:01 pm

Me too, but I'm afraid there's no point posting it here, it's in Live, it has always been. Try pressuring them a bit, for some reason they don't care despite this should be really easy to fix (probably, one never knows).

DPhil · Post by **DPhil** » Sat Dec 23, 2017 9:12 pm

MeldaProduction wrote:Me too, but I'm afraid there's no point posting it here, it's in Live, it has always been. Try pressuring them a bit, for some reason they don't care despite this should be really easy to fix (probably, one never knows).

Maybe because your plugins are the only ones failing on this. So I just think they say it's the other way around. And the probability for this is reasonable ^^

And I don't wanna know how you "asked" them for fixing it

MeldaProduction · Post by **MeldaProduction** » Sat Dec 23, 2017 9:21 pm

MeldaProduction wrote:Found the problem - for some reason Ableton Live disables automation when updateDisplay() is called, which is a call that lets the host know that the parameter names might have changed, so pretty much something unrelated to processing and if it was, it's no excuse to disable the automation. I asked Live AGAIN for support... but this is just sad, period... I mean they are postponing this for like a year? Or is it 2?

DPhil, perhaps try first reading and then comment on stuff, assuming you know what you are talking about. Here you don't I'm afraid. And for the record, it's not just our plugins. Btw. how many plugins you know can change parameter names?...

DPhil · Post by **DPhil** » Sat Dec 23, 2017 9:36 pm

MeldaProduction wrote:
MeldaProduction wrote:Found the problem - for some reason Ableton Live disables automation when updateDisplay() is called, which is a call that lets the host know that the parameter names might have changed, so pretty much something unrelated to processing and if it was, it's no excuse to disable the automation. I asked Live AGAIN for support... but this is just sad, period... I mean they are postponing this for like a year? Or is it 2?
DPhil, perhaps try first reading and then comment on stuff, assuming you know what you are talking about. Here you don't I'm afraid. And for the record, it's not just our plugins. Btw. how many plugins you know can change parameter names?...

HOFA system for example - and it works like a charm

MeldaProduction · Post by **MeldaProduction** » Sun Dec 24, 2017 12:33 am

You realize that's absolutely irrelevant right?

(not that I would check that one out or even know what that is)

DPhil · Post by **DPhil** » Sun Dec 24, 2017 1:21 am

MeldaProduction wrote:You realize that's absolutely irrelevant right? (not that I would check that one out or even know what that is)

Yeah you asked for it...

Since I still think you're a smart guy I however assumed you knew that modular fx since it came up in comparison with mxxx and other plugins in threads on different forums

Anyways it's ok to not read everything that has been written about your own products XD It's all repetitive in the end.

Soarer · Post by **Soarer** » Sun Dec 24, 2017 1:20 pm

I just tried this in Live 10 beta and it's still an issue. Vojtech which other plugins have this problem? I would like to report this as a bug on Ableton Centercode.

And Merry Christmaaaas everyone!

jmg8 · Post by **jmg8** » Sun Dec 24, 2017 6:04 pm

I have already reported it in centercode when Live 10 was in Alpha. It is known by Ableton, they are in no rush to fix it. The other plugins are some by Native Instruments and iZotope.

Soarer · Post by **Soarer** » Sun Jan 07, 2018 9:21 pm

I've reported this as well now. The more people complain about this the more serious I think they will treat it.

MeldaProduction

KVR Audio

Re-Enable Automation Problem (ABLETON)