MeldaProduction

nbyte · Post by **nbyte** » Thu Jan 11, 2018 2:29 pm

I have reported this too on the ableton 10 beta forum.
One Ableton person wrote:

We have not received any word from melda on this, and what there is to fix on our side.
We can however say that all other plugins work as expected doing this. (..)

Feel free to submit a bug report with the information from melda or have them contact me directly.

It would be great to solve this annoying problem....

mcbpete · Post by **mcbpete** » Thu Jan 11, 2018 2:50 pm

MeldaProduction wrote:I asked Live AGAIN for support...

nbyte wrote:One Ableton person wrote:
We have not received any word from melda on this.

Hmmmm well something has gone wrong somewhere in the communication chain !

MeldaProduction wrote: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

I wonder if this is someone related to the Max For Live integration when you have to 'Freeze' the device when editing (and thus potentially changing parameter names) then 'Unfreeze' an .amxd to use it again. Maybe (and completely guessing here) unfreezing the device calls another function to re-allow automation for that device.

Soarer · Post by **Soarer** » Thu Jan 11, 2018 3:42 pm

nbyte wrote:I have reported this too on the ableton 10 beta forum.
One Ableton person wrote:
We have not received any word from melda on this, and what there is to fix on our side.
We can however say that all other plugins work as expected doing this. (..)

Feel free to submit a bug report with the information from melda or have them contact me directly.
It would be great to solve this annoying problem....

Well clearly Ableton are listening now so Vojtech please write to them again. I did provide a clear screen video of the problem when I submitted my report. Yes we really need to have this fixed now.

jmg8 · Post by **jmg8** » Thu Jan 11, 2018 3:51 pm

I am on the Ableton Crashologists team. I personally linked Vojtech and Torsten together to resolve this issue. Ableton have publicly written that the issue is known but they are not ready to fix it yet. So it blows my mind when I hear they have said they have not heard about it yet! It's not just Melda either there are some iZotope and Native Instruments affected too.

jmg8 · Post by **jmg8** » Thu Jan 11, 2018 4:04 pm

Word from one of the Ableton team:

[mal]
20 Minutes ago

For anyone with a KVR account, please relay this to the thread.
These are the official developer ticket systems we have up where developer can add tickets for us to analyse.

Access Link https://ableton.centercode.com/key/developer_tickets
Short Link https://goo.gl/AmmSYR

Soarer · Post by **Soarer** » Fri Jan 12, 2018 6:31 pm

Thanks for the info jmg8 but what did your last message mean? Is that link for the developer (Vojtech)?

@nbyte maybe you could write back to that person from Ableton to let them know of what jmg8 said?

jmg8 · Post by **jmg8** » Fri Jan 12, 2018 6:54 pm

That link is for Vojtech, yes.

MeldaProduction · Post by **MeldaProduction** » Wed Jan 24, 2018 12:13 am

I'll be honest here, I don't have time to register on some site of their's... I'm quite tired of writing them gazillion times about the problem and either being ignored and getting a polite "we don't care"... I already told them several times the reason for the problem over the email, so it's their responsibility to care about their product... I'm probably going to try to hack it somehow on my side later, from my experience they won't fix it anyways... (sorry for being grumpy, but I'm tired of this...)

Soarer · Post by **Soarer** » Wed Jan 24, 2018 3:44 pm

I understand. But if you just register once and report this problem then it's done. Then you don't have to write them a gazillion times again... This is a quite serious problem that affect many of us. I'd be happy to register for you if you send me all details.
I'll also let them know about this from time to time.

MeldaProduction · Post by **MeldaProduction** » Sun Feb 04, 2018 12:47 am

Good news is I managed to hack it on our side, it may take a little more CPU here and there, but it should work. Hence I won't bother with their forms and stuff, after all I told them everything I know several times and they would ignore the problem anyways... better things to do. Anyways please just wait for the major update

.

Soarer · Post by **Soarer** » Sun Feb 04, 2018 10:32 am

Thanks Vojtech. I really have this problem ATM since I automated MFilter and MTurboReverb and therefore cannot render my track so I had to delete MFilter and use another filter plugin.
I commented on my bug report on centercode and will continue to do that unless your hack works fine of course.

kabelton · Post by **kabelton** » Mon Feb 05, 2018 9:14 am

Mapping the plug in automation to a macro is a easy work around. But of course, i would like to see that fixed.

Soarer · Post by **Soarer** » Mon Feb 05, 2018 9:59 am

All automation happens through macros now unless you have "Automation compatibility for V10" on. With macro I guess you mean multiparameters on the easy screen. Doesn't help.

kabelton · Post by **kabelton** » Mon Feb 05, 2018 10:42 am

I map the melda parameter to one of the eight ableton macro, then everything is ok.

Soarer · Post by **Soarer** » Mon Feb 05, 2018 10:45 am

Oh, ok. I'll have to try that. Thanks!

MeldaProduction

KVR Audio

Re-Enable Automation Problem (ABLETON)