Mismatched tempo sync values between UI and LFO Mod



  • Hi guys,

    I have a combo box with the list of tempo sync values linked to the frequency of the LFO modulator (the list is in 'items/component specific properties', not coded)

    When you pick a value in the combo box on the UI, it picks the wrong value in the LFO modulator in the back end.

    I've checked and double checked that the list is correct and in the right order, but they are still always mismatched. Any idea whats wrong?

    I'll put a picture of what I mean...

    Screen Shot 2019-11-08 at 15.16.50.png



  • @SteveRiggs combo boxes respond with the position values - so its responding with a position of 1 for your first selection - and the dial starts at zero....so you cant do this other than by using a calllback and subtracting 1 from teh value..



  • What Lindon said

    HiseSnippet 1019.3oc0VstiSaDEdbRLpwsAABd.r1ekUEBw6FBaEBQXS1TE08RTSJsR8GnI1S1LZsmwXOdKQHdF5CWeQ5aP64L9Zf.cIB9QsjGoysY9ly7cNyLMR5xhikQDilyWGxHFem4r0B0pgqnbAYxHhwsMOiFqXQ1opNdcHMNl4QLLp+inBilMH5u+94GS8oBWVoJB4kRtK6Td.WUpc5feh66Ol5wlyCp3cuASbkhgReYBfm5lcIgT2qnWxNmhtUyjXbqS73JYzLEUwhAeNV5sd1J4eHR8+k7X9BeFJ3PlASTpZxvUbeuo460XBwnwzxcd8zc98MOi6wKzWlAti1fcYDUyAF01DRM1.RNeLHMV56gSvGAdFUfWiT3cWyYtQ7PUoEDaeq4DAb3rjBo8pvJ0WRs+xvbnD7Pn5DPuhMNBDJhnc+tcef8i61c+m1xpkEj7iU1WSirOc7EmI8R7ovFyw9Y1ZJQmKYpBss2C7wtzo8RmhVVbgOWvrWlHbUbovFOPCVHOV9FGDHQR+1txfPo.fzCfEyOgseKq21xp4FKZmXl5EJUDeQhh0dSSiiXuNgIbWmE+CcvE+cZ.juYArNLeYZuWAD1aebhy.xPpu+Bfg09CwHNgU1BmKUrKDs225sVMsdmk86aZ4xsZKax7YQa0Lx9i9TA1VjDrfEkmlxcDnDax4t0Miy4llap3nTLQvUWDxxjKYkNagURxRtH+LCgfqJM67NYry7DIg6gjyh7JQuEp1rf7KSFQUz7IClWXsBYQJNtkLFwtF5bjR8aZNhEekRFp8M6TE112vk9MkK6yGrtT3oC3JV.rXKLcdjikyiNXDNf+yggdnTO7GkNBkNB+QIm9izi5ATwg5XO7.8.pnuN798zCyIAT.ElF2S2+6CpsgNL4z6pscv9qYF.dwF02XMrHlqVWMk90uWzsSwqoITQlAxM6C7eCxhp2pWSfWFLo7tjA+4fekdMaoLJHiATD9orKgEppl4LfQ.cnbqpbVfTpVwEWt4UL2evoRY3IBJjF7p5+zUzXrNF5NTEWCShUxfbrnuCZlhEpItF+tY+dcfukeON9CCggCu3KiL48OJqeyNJ2xwWsaHc6d5SxhiL7L8KJiq6VYbasOymEhK3S+O.w20bJW4tZ60z01BdIju53M60OsLOY4RlqpDrMLG+a65Sc9LfxOKSTPc5YT3xdrG44IAyfG.5x.jHDL+XruYMrVLUtKJiYlYLgmV3efuLiNnrQlQmbiP2W2H4qbSuyBKJ9FsF.SB8SKaBuwEjsKtlxzramtj.3Yeux0ESEODv91i4fcHlC2gX5sCw73cHl96PLOYGh4nOYL3KteQBz6MsLATL8jzttFEcuMpS9WrbLdAM
    


  • @d-healey @Lindon Thanks. That should work. I must have missed something cus it's still the same problem after subtracting 1. Can't see what though.

    //Fix for mismatched combo box values between LFO modulator and GUI (Bass Cut)
    const var BassCutLFOModulator = Synth.getModulator("BassCutLFOModulator");
    
    
    inline function onComboBox1Control(component, value)
    {
    	BassCutLFOModulator.setAttribute(BassCutLFOModulator.Frequency, value-1);
    };
    
    Content.getComponent("ComboBox1").setControlCallback(onComboBox1Control);
    

    Screen Shot 2019-11-08 at 16.09.09.png



  • Processor ID or callback function, not both 😉



  • @d-healey Damn, I remember now. Same as yesterday haha. Hopefully, I remember it this time! Thanks, mate. Fixed 🙂


Log in to reply
 

9
Online

550
Users

2.1k
Topics

16.1k
Posts