Delay ms glitch (SOLVED)

[SteveRiggs]

@Lindon I was wondering if there was a way to set the amount it starts at when it initializes, but even with that if the values are different for each preset, or if a user saves a preset with a different value for a custom preset then it would still load up wrong?

Really strange why it does it. I remember @ustk saying he had the same problem when I put up my first post about it a few weeks ago here:

Delay glitch

I've noticed a bug in the delay when using the un-synced millisecond mode. (I'm using scriptnode now but this also happened in 1.6.0 and 2.1.0 in both HISE a...

Forum (forum.hise.audio)

[clumsybear]

@SteveRiggs maybe it’s because of the macro. I’ve set the parameters via script, so I haven’t used macros for that stuff

[Fortune]

Yeah I am having the same issue. (with the latest scriptnode branch) It's not about macro.

If you control delay time of the simple gain unit with a knob, on first initialization in Hise - it gives a constant delay value (around 30-50 ms) - even when the knob is set to 500 ms. But only on first initialization in Hise. When you change the presets, the issue is gone.

But it is ok on the compiled plugin, this is another strange thing too :) @SteveRiggs did you check it with the compiled plugin. It doesn't happen for me on compiled plugin, only on Hise - first initialization.

[SteveRiggs]

@Fortune @clumsybear Yeah it's definitely not the macro as I only have that on in this project.

It's happening in compiled plugins for me as well. I have my prototype exported plugin on a track in Ableton with the stereo imager turned on and set to a certain amount where it sounds good (around 20ms) and every time the Ableton project is closed and reopened it changes it to a longer delay time.

I just tested it again in a fresh Ableton project and saved the name of the preset so it would initialize from an actual preset, but when I close and reopen the project it still happens.

It is fine when changing the preset to something else and then back again, but if a user has the preset picked already and has set the parameters how they want, then every time the project will be opened and closed it will happen.

[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