Integer knob value doesn't sets the effect but decimal value does?

  • @d-healey said in Integer knob value doesn't sets the effect but decimal value does?:

    You're writing crazy code again 😛

    Why do you want -5 - +5 = -29dB - +22.08dB?

    Ehehehe 🙂 It's just an example equation, never mind that point 🙂 I think the issue is not about that right? 🙂

    I didn't used .changed() since that can cause cyclic reference because of The link button, right?

  • @orange I think there is a built in thing to prevent cyclic reference when using .changed();


  • @d-healey Yes cyclic reference tool doesn't detect that also, but as far as I know, it crashes in DAW.

    Is ther another way or is it a nested loop thing?
    If the .changed() is the only way, How can I use it?

  • @orange What are you trying to do?

  • @d-healey EQ - Comp - Preamp combination with Left - Right channels Link/Unlink processing.
    This snippet is the simplest prototype that has the core issue.

    When the user enters negative integer value to the knob, as you see it doesn't update the effect parameter (Simple Gain effect is the example here).
    But negative decimal value updates the effect.

  • Well you're playing with the knob ranges so it's probably not going to do what you want.

    This is a simple way to control two simple gains and have a link button, maybe it'll point you in the right direction.

    HiseSnippet 1184.3oc6X8taaaCDmxNLH1aoncXO.D4SxHsoxY8OaKanowIYvXMIFycYcHnHiVhJlKTjFRTYwqHOHYeZuF6a4QYOB6MXijhJRN0y0w.qaYH5KVGu6386ti7tStSrvmjjHhAN0d4vADfyGB6NjK62pOlxAs2D3bG3N3DIIFkszFCGfSRHA.GmpekdAmZyALO+wy1.yvbeRwR.v9BpO4EzHprX0Nq+0TFaab.4kznRR+n0a6K3sDLQpBOUgdfAX+iwGQ1EqEqBD3L+VAToHtqDKII.m41PDLraewOwyjeeZBsGinIZB5p1nrk2VvBzHVuJnUeJKnStem.T6RmhnP0rnvGC2gFPub8hnwcMLPEZTNd3TYRvq46FddiCdNkf2bYv6dvt9wzAxBNZr8Av1bUhJDqRAkgUlrfJGVE1RnjfKWIBeLY6XEwkZ39DOu6idrmWi0Vr9h0UIhDIJgFMfQzoYzWhN30FNghXjKUQ6sFhh9BzppeVd4FKVGodJTXkAoI8cMmkV4HhbqvPhuzcotFAPZIVBsrdiVF0rQiLi9vGhNl2SyKG.Vxov5uIC.VExrdt2preKQz.AWQ3tjUDs4oFCWRuCnudkDszbYrf0ByX8TGAcEbKeKCsVmko3h0obFkSPgobeIUvQWUXW+baeezIXVJo.sLgOlgn7.xoJWJG6F58BKzKGjWMFefQRChetTFS6kJItuMa864ldjchFhb6I4ufxOVGi1WKgaCapzBwxAmlOnvfYBOxlNVQ86i4GQBbarlQlyzwMSl1Z37LskTEFFeVyxeoFqUJPuqPR1i61n9apWq9Y0QWkUX3X4YSLLR7XYqqJEOIEc4oQ8Hw4wzbAUWOG89+7S28e+LGtjfBdaNUt2.hkdxEv.1HlpVQUKBUuIMUJtisRQWFMfDCnpMoNzlj7.F7aK.+qme9Su.bczu40P+MRkRA2neMnMWNh5YOea6MwRrtnm0mT94.RrjpCmNaRNQ0MIqDXM3ljjikhAFm1dLQUCbZb6SKr4ms9PfCz4yUuFIBr6qOsGgAhJ2b66uHBeZYnpZINnK8mMv+WNW+7aOKIMLjpjBBQAanzOHfQ5HRn5SOZ4bLZt5ERxoJnt.zTZSmQuV3uYI7+6+3+53e0QvObJR6E33GvZ3mSbz5Ya77PiXf2tump6qHHkgki1RViCKCMRK26S2eiq7fgkmS4Zzm1apGiXZg68fcnR+9iGuUFCdU2F9mFu1odVDl0lt.ryA29UuGFwoRIrrvkygdYiL6bnklcn4e2bnWnqBsIggGI.9cz.Y+RWFVeLSp1lehpPSGACGe0ve0Q84pSmO+NlzbxmQLWstwbl9iflP9MI.aNRbyAv2E1A+egCDeiHUR4GsCVMtotSwtoQcUetlOQAUNmvRzcipnmIIi1SSqATWBOvP7mpGKylZZGKyl4LAW2hAqdawfaKFbawf+eVL38gMhv9whC8y9zE8UyELqn7at4edpFbGMM5xO3AB8VwSOfL8Pee8TROPEeFuNqNC57IyfNOZFz4wyfNOYFz4oyfNe5D0Q+mv87ToHJ67uZgNaY9xQGms3X0IYyUAveE5zb9H

  • @d-healey Could it about the logic of the "loop"? Because I only used < and >. Not >= or <=.

  • @orange I don't see why the loop would affect it, I still don't understand what you're trying to do though. The simplest solution is to use the knob ranges and to control them like in my snippet.

  • @d-healey

    Yeah that's a good way too, but I will have to rewrite the code. There should be shorter Solution. Maybe If loop

    if ((arrayed_Knob[i].getValue()) > arrayed_Knob_values[j] && (arrayed_Knob[i].getValue()) < arrayed_Knob_values[j+1])

  • @orange Ok I figured it out. there should be >=. Thank you @d-healey for your help and advises

    if ((arrayed_Knob[i].getValue()) >= arrayed_Knob_values[j] && (arrayed_Knob[i].getValue()) < arrayed_Knob_values[j+1])

  • @orange you need a >= instead of just > otherwise you miss values in the array

  • @ustk Yes, definately 👍

Log in to reply