@Christoph-Hart I just went back and double checked. It is in fact in vertical mode.

Screenshot 2025-06-21 at 2.02.57 AM.png

get value part

var y = a[3] - a[3] * obj.valueNormalized - (h + 4) + (h + 6) * obj.valueNormalized;

@Christoph-Hart Thank you for the clarification! 🙏

https://docs.hise.dev/glossary/css.html#font-handling

@d-healey I imagine that works as well!

@Yinxi There are several ways you can approach modulation routings, but sticking with cables here's one approach:

HiseSnippet 2493.3oc6as7aijTFuZ6TNwIyNCK6vCgXk7AjHKZVutSbxLQfTbd3Laf7vJNDsqDhrU5tbbozcWs5tcRLK6MNvEX45da4+.zb.I3Bi3HhCH1iqVDh+BFIDWYndzsc2taa21wNyL.YjV4t9pGe02yeeecu0bnZXWWpCPY9iaaiAJ2AVuskWysZhHVfc2FnbW39HWOrSA4Pa11F45h0AJJYeLe.k7y.D+8r02DYfrzvcGB.NgRzv6QLIdcGsVke.wvXGjN9XhYnYWtxtZTqsnFzVL9IKrDvFocA5b7AH9zx.AuKxsIP46.WYok0Jq+P8kVZk0VUCsJdsFnFMTWVub4UezZpKuFp7iVEWZEfRtp5DOpScOjG1EnLylT810aRuxRd.mPbImYf4OnBpyNY4v6PMz4WQ9nfsZRLzqEHnbArMsVWwVVoX69v8I5jNi2U78kDDJzcEgEfJYhxdYivdpgYuRgXuDXIkPrzLRV50g00bH1dcov4mEf6ZwzlMPL8TXVQNWfxSgaQYSvxqnI5B7NNrG5rfEWsToGTf8edquaiVVZdDpUAp0ATO7gVK9Vy+gyme9OZ9B8RpQiDowOFGpgA1IQxbSCmAsvEsZYdF14AEtDYzB2YhrqeTYJr+xzvpbM4sNzDoV6ZQ7NzFa0OCAfunh8qe3tai7PbEg+Xr4Yic7HbVPYa7kL2.oZIObar6EdTaliPLcFyZgp2x.4E0Dh6n4SfIChn23JGKWhW6vNh8ZWMS5rqFrYeZY2WGVi3o0LY9MSB7KSpMs4WeuzWCVsQCrlWWlcF3Nu2zwkL7w+FAG+FszIz8nbSCwwee4HE3CUnlApM1Qc.gX+KoMDqcpCwxh1qwTU3vlOB82wNrfuDqyCeTb1rpEhc+0CO7QTpG2UObH95HSaCLSJ53w19HyFeI1wM5NrCwvOJ+2F9g0N5vue0sN9zcNbusqdzGYRb0dG9I69NtD9lV7Jzk.StbApvWrI5Z9O+E2aAfAaZhyLflgfi0CnqjM0FZiP9fYlV4CtU8ampgYRVZlXprLg327A7acglup0kXClyife+xr.oMPsL7BFMpmy9TKpcSpEQKpwmmC47ywNguGId41vyi4.zcj6W4HrAF4FxJ+aUYOhEF4zq+yHDCQcjSqmnt6qCkraAt6dgWpRU.kr82zGMBmAOA4PPVdctGhqP9.yugyyAXU9Gvt3Brcv1HG7wTdTzEcEQeNhckdPA4ucqgc1zfpcQbHE1RlUPcwyZwxP3zWvLSbbNCCMCbBYJEBqxAXuqnNWHru7+MPY1n5fMLLnWsE0zl3aHwzEhwpQMZG3VojUNCLyPzxBargIskkHzaF1wv.qeLhXvS5WukKCFk9gV0YSVj9RI6Irj.hMdVXohr+wb7OP3GM6NHM1MtcMjWSNZBNxLFWgcJp0wdOYiEYFjtz36WPtNY5.F+ZxEB7hI3RwZHG1ZXva4nzxnjMDpMoyG+IlsWF9gdG3ttmvopgL.mv0S7EINE9zyJY+bxhlN2fdFx3TMdxRPjazWE5Pa4wxrVLxbheQ5YSBeaxm6cexu748diFJ+yrArvBKu.9OObucN7zCawrK5F03Xjy4XOWezrAqPpe1kmKEZah.cjc7glEJ2PPHIJmCBdhMi8IVAGZmvw6ittmwXd2dX65jeRj4U+B7URgXj31a28fisM9IGhMNHjZRdQhncdMg8FyirHmTbkhbIC1xJpdXjDrHc8zHXyFRvN2spfE.RVvB.azxiZxhRIf4CFLC9r+vMmAmGtOiMH1FsSuxeT3wIgPDB2foP6rIybxce6m7E+s0SmHLhgJ2vHhg57P1LaVjOdRVo7wGhUZlHVo80w8kb6KIjwPwY3adNQN.vjmy6rz+zut5u8e9ledeszB6gORQRklLfduQKvg84mfcx6O0Yo+nO9O9uV76MEtVg7VAaRoWXhDHPlpMNYfchH6+yzIhjphXde33ryT5ubLqrnDaH3OOUfrOiCdlaqMD30ZRjhtiCT3bSJnvGIwesOhUKHu0AGzxrNKHoV.NV2.Hr9OWJH7YcFHVwCOm8mOQU9yJ9DUCHlJ31KvhRwqoPiU5ZLv0hqTuXjSBV9M.Cd.j6bo.xcXlsqcBWBKS4Dl9vfGE.YVITJtYgt1FDOPeYEI4345BV3HgIKfCxDhClCJtsKAFhzHNKzYkiBOLh0WDIiGHhfSxVolq6pyxCqZcovyOsZr4Bcv4fmyz3QO26A0aagLIZtEEDiKq7W0PNvYFSDz43.eVpOPn4dJF3qCR3rMgY3fZuonhe2Xiv0JV53qCboqxhJoyhxKVdfadDXHvAWty6+z3IoYgMhlj9S+jO42sdrjzO87eyWohzF43lNX2lMYIb.w1+9AcBLx0gUgVIUL1GT9W84qKcd7aXVJwysakaAlJOLnmcSJt5YqGWGVIcb0m9Y+6+pOx2i31xiPIqidYzfJwA+8r06OZ7Ef0I5XYjhTiHGDIXfvwa3knzM5iXIpCuJk9UXBrqn.xyOFRL.gprmCWlQz6fb98TQQu4G7uYK.cMoTul7WMSOw5znN3hATSHV27cV5ncKyjrBu2a4bvkJUhOTWc88YSQsj7O0xqURUcU0HX94SXokUW9gOZI0kV4gppkKqJDT2CVWvqLfQh2YTTA1rPUwI0wF34O+qkC7AuWD+kToPtKLxN2YCqrxO92u6O8uudRJp9paxAcXo.hpVVPZ0IHjT5GAgISowy9RRowgEI4glT8SIVWFUpbWoTIfVRsMMf1+8JaxAswnK50bQ3EKHjbTJAoggWI8PT5ostSFnJJ9PUlA91p8.Ure9N2ndT2U9LvtTe8Sd7DpK0MnBbpfoS1.0XYCRPe1CnaFvBmnRs6H8wjTRRVErpamTdQl3vCq1WilzVnRzM3lta23lDcaTkenFqLmjA9FvGKbG51Npf5vD5l2zmbgNzKzYB2xe4Guh8sPLQ9PbFT2BeiXpF2Q+0mOYZRWtT9Nyg72d2vYxMI1TCjS3t58+e04S3WcNDZzf9h70lmld3IYxjdcQ7wmhMu5V9kiO4gcLJcfhk3yNJrtbhdi9J1KG2+hjDXYAgDqshSXJ0Zu6EQiq9BpGeYGfVSz2m3cs5iSW+g5n0tCjEvkP0EIvCsWE+r+7OqckjUcu+XzNsQ1bZA3dc99JSe8WS+Wkru60X9U.DxjuWSrwKzTu6xKfObmWVda9i7WhAm2eE50COQ.k9h3iS+1n3naiyvDo4PO0+S1R7BpDivt2V9c0Ze9yETAW1qQuIq1iS0zhtUwV3Ri6BWdbWX4wcgqLtKb0wcgObbW3iF9B4kF5Gjf6ZxBRUqpLsrRm+WPPIK3+vb.qnG

Modulators (global, or otherwise) don't process, or pass through audio signals. In your screenshot, the ramp is modulating the gain of its own signal and would have no effect on the gain of the loop player.

Ok well I can see this turning into the cluster f*** it usually is so here's how to code sign and notarize and staple your plugin - note this is for distributing plugins - not for distributing installers (like .pkg and .dmg files), also note you will need your apple ID, your team Id and to have made (and kept) a password for your notary tool all in the apple dev web site...you will also need the relevant certificates(A developer ID Installer certificate) in your Keychain Access

build/compile your plugin. copy your plugin to the desktop open a terminal window move to the desktop with this command:
cd desktop
5.codesign your plugin with this command:

codesign --deep --force --options runtime --sign "Developer ID Application: your dev name ( your dev id)" "/Users/your username/Desktop/your plugin name.vst3"

zip up your plugin into yourpluginname.zip and leave it on the desktop Notarize your pluginzip with this command:

xcrun notarytool submit --apple-id "your apple id (an email addess is likely)" --password "your notray tool password" --team-id "your team id" "yourpluginname.zip" --wait

wait... it will tell you Processing.... and eventually tell you Accepted (if it works) Staple your plugin on the desktop --- no thats not the zip you just sent to Apple, its the plugin from step 2.... use this command:

xcrun stapler staple "/Users/your user name/Desktop/your plugin name.vst3"

if this is successful (it will tell you) ... you re done...and you can zip up and ship your plugin....

I think using Engine.setLatency dynamically can be problematic.

Instead, after the maximum delay value caused by pitchshift is set in Engine.setLatency, the difference can be balanced dynamically with a delay node according to the parameter values ​​that give less delay.

@lijas90 You need to add a generic script reference for the EQ then bypass it in the button callback

const var ParametriqEQ1 = Synth.getEffect("Parametriq EQ1"); const var Button1 = Content.getComponent("Button1"); inline function onButton1Control(component, value) { ParametriqEQ1.setBypassed(value); }; Content.getComponent("Button1").setControlCallback(onButton1Control);

@ryan_nfa Nice :)

@d-healey Ahaha, that's it😹

@Zazzi post a snippet.

@Lindon
Ah, I didn't see that. Thanks to you. :-)

@d-healey ok thanks I will go watch the video.

@Lurch still seems to be trying to build clouds (clouds.h)....

@Mighty23 said in fix_block - I can't understand it:

Can I have some concrete examples?

For example, if you have a very fast LFO, using a frame_block is probably more interesting than a fix8_block to achieve more precise and smoother modulation.

@pcs800 If my memory serves me correct I believe this HISE tutorial shows you how to display compression amount:

https://github.com/christophhart/hise_tutorial/tree/master/DynamicsFX

SOLVED

I just opened an older version of Hise. My fault. I am so sorry 😊

@JulesV I seem to remember getting that too but everything worked fine, the project would compile and export. @Lindon's explanation seems plausible.

@d-healey lol !!

ok so you have to see this then....

its on a different thread....
https://forum.hise.audio/topic/12880/chord-player-inversions-help-with-indexing