Delay ms glitch (SOLVED)

[Christoph Hart]

I think I've fixed it. The problem was that there is an internal fade between delay times to remove clicks if you change the value, however this lead to the issue at initialisation (it was "ignoring" the requested value change because it started a fade already).

[SteveRiggs]

@Christoph-Hart Thanks man! This is awesome news. I’ll rebuild and test it out as soon as I get on the mac. I’ll let you know my findings. Fingers crossed!

[SteveRiggs]

@Christoph-Hart Sorry to be a pain dude. It's still not fixed though in the 22nd Oct build. It's still exactly the same as it was :(

[d.healey]

@SteveRiggs Scriptnode was updated about 1 hour ago ;)

Edit: actually I don't see any changed there relating to this issue.

[SteveRiggs]

@d-healey Jeez. After spending all day trying to get that one working lol It did say on the notes for the 22nd Oct one that it was fixed there though so I'm not sure if this new one from 2 hours ago will be any different?

[Christoph Hart]

Lol you must have thrown the computer out of the window.

Can you make a example snippet that demonstrate your issue? I've just fixed the bug that doesn't restore the initial delay time.

[Fortune]

@SteveRiggs Yeah the latest update solved the issue. It's fixed now, thanks a lot @Christoph-Hart

[SteveRiggs]

@Christoph-Hart said in Delay ms glitch (still not fixed):

Lol you must have thrown the computer out of the window.

Lol it almost did!

All seems to be fixed now though after building the commit from yesterday. Much more stable as well!! No crashes on the exported plugin now on first scan in Ableton. Worked first time. You must have worked some extra magic. Thanks dude.

[Christoph Hart]

I just removed the line

if(isAbleton())
{
    crashOnFirstLaunch();
}

:)

[SteveRiggs]

@Christoph-Hart Haha good call