@skyscapeparadise
Yes - the documentation is not amazing. (Sorry to people who worked on it.) Coming from a platform like Native Instruments Kontakt, their KSP guide includes examples and use cases that are decently commented. At least they tell you possible values for function arguments.

So my encouragement is to USE THE FORUM!

I see the source of my confusion.
Using g.setFontWithSpacing(font, size, spacing); results in a length of spacing at the end of the string.

For example, if I write
g.getStringWidth("TEXT");
I expect TEXT's width and spacing (shown with underscores) to be calculated as T_E_X_T.
Instead, it is calculated as T_E_X_T_.

So using
g.drawAlignedText("TEXT", [0, 0, this.getWidth(), this.getHeight()], "centred"); doesn't actually center the text due to that kerning offset.

@d-healey Never mind. Something went wrong when I compiled HISE. I suspected it was a permissions issue since HISE normally asks for permission to access folders on my desktop on first startup, but this version did not.

I deleted HISE, recompiled a fresh version from github, and now everything works as expected.

@Soundavid

That was indeed the issue! Thanks for nudging me in the right direction.

For anyone else who comes across this issue and wants to follow along, I just decided to hard-code the output routing in the script for testing. I am still learning HISE, so I do not claim this is the best way forward!

1. Right click on your master container > Create Typed routing matrix script reference
2. Paste the reference into your Interface script onInit.
3. I added a simple for loop for 12 outputs.

// Typed routing matrix script reference:
const var Container = Synth.getRoutingMatrix("masterContainer");

// change 13 below to your number of channels + 1
for(i=1; i < 13; i++){
	Container.addConnection(i,i); // 1 to 1 channel routing
	Console.print(i); //check for correct channel numbers
}

@ulrik That's an interesting solution! I came up with something a little different. Any XY cursor and pad shape I use is likely going to be symmetrical, so I have the XY cursor area bounds set to a smaller version of the XY pad shape. When the mouse cursor moves outside of the XY pad bounds, the XY cursor locks to the smaller XY pad shape path. Not perfect for all shapes, but maybe close enough for my needs.

That's probably difficult to read. lol. Snippet below.

HiseSnippet 1395.3ocsW0saaaCElJIpcVaEaEXO.D8lo.n4ZmD2Mffh0DmjAiszZT2UzBCiBFIZahHSJHQmDg0bydr1U6QZuAamCorMUiaVQvpgUh44O9wye7n94pXdQgJm303UkYbh2W4OnTpm1cJSHI8Nh38k9GmlJxJ3u4sjCKyXEE7Dhm2l+LJfWisHlO+8OcHKkIi4qHQHuVIh4+pXlPuhZ+m8KhzzSXI7WIl4H8dOqWrR1UkplCfYS+VjLV74rI7myPw1vm3cuiSDZU9.MSyKHdacnJobvT0kRq7uVTHNKkiKZSF.FxR9DUZBhXjJo6TQZR+EG5BBXk9qbAaZcAeq+ohDwR5qbEeigAckFt9CuMpCuMqAu1tvqkC7VCj7bfzVVH8P+Aw4hL8JN1PSOolmOlAtcWnXkkrwede+tJPBot4L147SxgEK0H7IsZEQg+r89AAO9wz9LIOM.hAEZ5ErbZlL8Muk9T5BKLgq6plkojvhvGY39HP0akcyBjpTmqR6xRSOChngJogYE4pMuaNG7ZTXCyXIQTPV0k7DJCHCqjIz344vo1AdWU1mom5fuXiIPhgfQWIXks9Dk1tOeTAQrdUoAW.R0SqAnCPpOkNbmNQv2NcZgOi1OvB0lrjjpJoPqrKN61szZNyuQQeIOVyjSR4gCAy0JZuVQsaMBw55DADnCvGjZzZNNU.qRSHRcnZtLoHrcyVaafvAN96O7bU4+Vb31qSD7sCrWvyn.Guq6AzQopS4op4Eb5THVlJjSBL4.X5gg9xjiwykwZgRFxu.b9aG76AMDio1UMSxYSnu+8T6p3TQ747jsCZ.BYjxEK.90PYaQ3PqzWEY+e4nsAMLpzPOUTzLgoYMEE8jEhDNb.04y4.hqw9JfdkY1uNmxkbJ2uAv5Z3gmVvu0sXLCjvXH7A7MiEPFtdJmJvhyBtwEPyTvR5Yb8kbtjFyQdT03ZEGlZiYFWaUEBXQLpUyRO0sH.i+8b3FNzIXMbmQOdmHWB6BDFEcCuXjwQs8xSQcmk6tODKAtgSqlDsMRbM50MRECoIS3IPAGX6qoAWWkCcTN6RzcmWpqkC0Ghz5WplCT4qRgl.oOf9XEFKMddJ1fAcWEPSZtwcacYeWgouipPXbVAF+GdJbOSeuSojwIsuUtxZxUVWtcMxEzXRywvcdPQVn89shlSx4knyy.uD7Xg3YQmE3j.EIbTQSCTTmkpdVJTnf5NAKHtrdKkH5tnuplUMkx4fKZQNyRyCRU2HNA9n12De11yKyzVO5rYE1irosoU7ngWEUFUyIFUyUgMtVDneIOCColMMCuWhBAlX6MFABIhd5h3Ls9EJgwKtEJBZegnAahrjXybqowl4WuefiQdtRyegLzHdv0AzOj03wqkW01lxyWKabHm7aSwP47YmwycAKJHbye8wI7+3iS3NsSr8ZKGAUxdRg9EYb4GaFHR0ccvu9sdGA4w3LHUz.4x34ZABAui3W.CzYmHog+Q7hy0pLirUdWhWf1v8AKlWACdDALUx88MQIxUtCHV5t3RQhd5RB+0e7robwjoZWJl7yEWV.H5q8ghJ5JBmMYw.jMt2+.eP0DZ9rai5NtjI2bzKXnOUB18n9jf33uULf3YswuvtqPudco63w+uMd3mJDeneegNd55w3FqAiPT+yAFqFp9A9GOdLzueE.2x+j274YBZh8tfImxz4BHgy+4ymM.B0wbX2kPFIVO4sAl4aW2BWidfAbYhYAlPTwrMt1qhY6ELIyXw4p2U0TBGa+KLT.LIMuwRC+Sw0z1DSksqedF7VDuKNttotgh6bWUb26ph6cWUrycUwmbWU7GtqJ9i+2Jhuj2Ay0pY1xFB4z9GaZK54crjAYflrUx+xLqGow

@d-healey said in Why Doesn't This Choke Script Work?:

@ericchesek

@ericchesek said in Why Doesn't This Choke Script Work?:

The loop is just so the same RR value never appears twice in a row.

The loop is not needed - https://youtu.be/8NtZJonqXLo

@ericchesek said in Why Doesn't This Choke Script Work?:

Thanks for the note about local vs. var! I'm still trying to figure out the appropriate uses for these data types.

Use const in on init/namespaces for fixes values, arrays, or objects. Use reg in on init/namespaces for values that will be changed. Use local in the default callbacks and within inline function. Use var within paint routines and anywhere that won't let you use local.

See here - https://docs.hise.audio/scripting/scripting-in-hise/hise-script-coding-standards.html#variables

@ericchesek said in Why Doesn't This Choke Script Work?:

I capture an eventID when a PlayNote function is triggered.

When you play a note you create a brand new note with a brand new ID.

@ericchesek said in Why Doesn't This Choke Script Work?:

I attributed it to the MIDI list storing values from -127 to 128 using the setValue function

A MIDI list is a kind of array with 128 elements. It can only store integers.

I love you, David. Seriously, thank you for your willingness to help.
I'll be back with a solution or more problems!

@WepaAudio Here is the snippet

HiseSnippet 1272.3oc6Y0saZbDEdWfMxPZqZpRT6kihpTsUnFuKzzJE0ZrMXWTCAjwwN2EMd2AXpWlY0ryRLpp22Gu9HzGA+FzdlcAyr1DfPRZTZAYYw428aNybNyGPaA2kDFxEFl4OYT.wv7Sr5LhI6ePeLkYznlg4mY0DGJIBThp8GEfCCIdFllYORovLeNi3WWs69XeLykLUkgwobpK4ozAT4Tssq9KTe+CwdjSnCz7tR0Ftb1AbedDfmrV6XDfcu.2i7LrxsLVFl2otGUxEcjXIIzvL29buQc5yeEKw+Sogzy8IJAaiNPhRT2ZHQLjRd0gbeOExUVMNnO02q8j0enAj71SqFYSpF22pI0ids9oUkOO1.ZZD50EyLogY1Tvz90AyY.ISMHkKAR2ypiqfFHmZQgm6Z0fAaRcwP4WGJI9Zj4OxZc.G7fI2d.9BxgBP35H17w6rSQD7usdRgBvVPnDMDKPI66wqYzOhhOVrcOh7Xdjjx50DKEzK27g5mNdnJAkJgNCOjzkKFfNhvHBLTJrQzPj.hj3gjbjdPH6G4flcTNyIpxOpRgBZPbarmGrDYDWIky1ztn8VOAAYUAWRp0BnHHRhrUoLvOpmlp4jPmhNKHgN2NgNyIgkKVdAIr7sSX44jvJEqrfDV41IrR7F1Qbkk5WFvERz29SSdGND0.NMHhF.GbT90bDhDaB1PNsyIk164TTWpOIDQXPqEJJ.AoV4Ib77WAbEVpFYXo8oLrfRBKseDbBOrTSraqNunz4JoRwdCHQ1mGRTgOB5+Q016ruIbBV6pZbEgEAeHLjOG6k3zXyvefAUHpUAzxI2taDKtnf3rmwkjVrM2pvuUHegeu.5ll51cl1TsKBtuOQLSypQWh4E3lrnAmSDEgVI+Hx0NB8woGNbmka3faR2qlibVCFU1JfLVd9S2LF29Cu64MpgkX0zkw5.+BHBIUAGSX+BFYmLqIuUMR3ERd.Lz9VChfQfbuHeUep9bQ0kBiM.0iTCiTCbXgT4H8KMt4vxbu95wNZ0iErZWR3dOq1Toa+Yi2Ly.uPU68MdGe0ymZUuaWnCZJXyYc3Kl68LuygxCRfxcsTiliu.HFHOvZFC3mCyf+bYYFDrzLCZ4JAHbh.yBCfwF15Y9F1bzsUiHiXocOQUJuTKuCgkms9A0IJ07bipswrTICjSkolzK0EqyvvFRGBrZ7ZE5BKVUsS+ozNxOjbF0S1WKu+klZGc0+LV3A6KtoNflM8oBqka.S59VM++Pyd5e0ABu8yuxtbvcAj8xOAicnCB7I0YCI9vP5XL9EvT4t3He4Dso68ZxY7f9bFM0ohiI.csd8HoNrMyEzdRIP6dpl6W8XhOAGp0O90UeJkQvBnNQVwZwaNw2Yte8UVIvEoFXf9uw8NY+e+8NyuCElo9wyN8WZAy4cPwa2nO762o9vavcCOKZPG3RUWBfX3CR3qtuvLihtXh7NJYEb5.D7iE9a30Xi1JYywFsmXbEIP37w.Ahq1ckIPrQ0YPfv3Mi.wU6tl.wZBDu6IP3rl.wZBDqIPrl.w6IBDYlGAhr2h.wMdF4m4yH2aEIkwFclHqL5bCik0Mdsfw.rqf+R2jukO0nlMh0.ULV7uSQdqlJYjsQ727m9Vx.3RqW55lNU2JPmUMvxqZfUV0.+tUMvGupA98qZf+vhCTwoXuHIePRGFP9pc83upTSyDdWwMaF+iGdZVZ

@WepaAudio Sure, give me a little time. I'm not sure I fully understand your problem. Just so you know, multi-output only works properly after compiling your instrument to VST3/AUi/whatever. It will not work in the standalone or plugin version of HISE.

You can also select lblSearch and enable "updateEachKey" for a search that doesn't require you to hit enter after typing. ;)

@ulrik That's an interesting solution! I came up with something a little different. Any XY cursor and pad shape I use is likely going to be symmetrical, so I have the XY cursor area bounds set to a smaller version of the XY pad shape. When the mouse cursor moves outside of the XY pad bounds, the XY cursor locks to the smaller XY pad shape path. Not perfect for all shapes, but maybe close enough for my needs.

That's probably difficult to read. lol. Snippet below.

HiseSnippet 1395.3ocsW0saaaCElJIpcVaEaEXO.D8lo.n4ZmD2Mffh0DmjAiszZT2UzBCiBFIZahHSJHQmDg0bydr1U6QZuAamCorMUiaVQvpgUh44O9wye7n94pXdQgJm303UkYbh2W4OnTpm1cJSHI8Nh38k9GmlJxJ3u4sjCKyXEE7Dhm2l+LJfWisHlO+8OcHKkIi4qHQHuVIh4+pXlPuhZ+m8KhzzSXI7WIl4H8dOqWrR1UkplCfYS+VjLV74rI7myPw1vm3cuiSDZU9.MSyKHdacnJobvT0kRq7uVTHNKkiKZSF.FxR9DUZBhXjJo6TQZR+EG5BBXk9qbAaZcAeq+ohDwR5qbEeigAckFt9CuMpCuMqAu1tvqkC7VCj7bfzVVH8P+Aw4hL8JN1PSOolmOlAtcWnXkkrwede+tJPBot4L147SxgEK0H7IsZEQg+r89AAO9wz9LIOM.hAEZ5ErbZlL8Muk9T5BKLgq6plkojvhvGY39HP0akcyBjpTmqR6xRSOChngJogYE4pMuaNG7ZTXCyXIQTPV0k7DJCHCqjIz344vo1AdWU1mom5fuXiIPhgfQWIXks9Dk1tOeTAQrdUoAW.R0SqAnCPpOkNbmNQv2NcZgOi1OvB0lrjjpJoPqrKN61szZNyuQQeIOVyjSR4gCAy0JZuVQsaMBw55DADnCvGjZzZNNU.qRSHRcnZtLoHrcyVaafvAN96O7bU4+Vb31qSD7sCrWvyn.Guq6AzQopS4op4Eb5THVlJjSBL4.X5gg9xjiwykwZgRFxu.b9aG76AMDio1UMSxYSnu+8T6p3TQ747jsCZ.BYjxEK.90PYaQ3PqzWEY+e4nsAMLpzPOUTzLgoYMEE8jEhDNb.04y4.hqw9JfdkY1uNmxkbJ2uAv5Z3gmVvu0sXLCjvXH7A7MiEPFtdJmJvhyBtwEPyTvR5Yb8kbtjFyQdT03ZEGlZiYFWaUEBXQLpUyRO0sH.i+8b3FNzIXMbmQOdmHWB6BDFEcCuXjwQs8xSQcmk6tODKAtgSqlDsMRbM50MRECoIS3IPAGX6qoAWWkCcTN6RzcmWpqkC0Ghz5WplCT4qRgl.oOf9XEFKMddJ1fAcWEPSZtwcacYeWgouipPXbVAF+GdJbOSeuSojwIsuUtxZxUVWtcMxEzXRywvcdPQVn89shlSx4knyy.uD7Xg3YQmE3j.EIbTQSCTTmkpdVJTnf5NAKHtrdKkH5tnuplUMkx4fKZQNyRyCRU2HNA9n12De11yKyzVO5rYE1irosoU7ngWEUFUyIFUyUgMtVDneIOCColMMCuWhBAlX6MFABIhd5h3Ls9EJgwKtEJBZegnAahrjXybqowl4WuefiQdtRyegLzHdv0AzOj03wqkW01lxyWKabHm7aSwP47YmwycAKJHbye8wI7+3iS3NsSr8ZKGAUxdRg9EYb4GaFHR0ccvu9sdGA4w3LHUz.4x34ZABAui3W.CzYmHog+Q7hy0pLirUdWhWf1v8AKlWACdDALUx88MQIxUtCHV5t3RQhd5RB+0e7robwjoZWJl7yEWV.H5q8ghJ5JBmMYw.jMt2+.eP0DZ9rai5NtjI2bzKXnOUB18n9jf33uULf3YswuvtqPudco63w+uMd3mJDeneegNd55w3FqAiPT+yAFqFp9A9GOdLzueE.2x+j274YBZh8tfImxz4BHgy+4ymM.B0wbX2kPFIVO4sAl4aW2BWidfAbYhYAlPTwrMt1qhY6ELIyXw4p2U0TBGa+KLT.LIMuwRC+Sw0z1DSksqedF7VDuKNttotgh6bWUb26ph6cWUrycUwmbWU7GtqJ9i+2Jhuj2Ay0pY1xFB4z9GaZK54crjAYflrUx+xLqGow

@skyscapeparadise
Yes - the documentation is not amazing. (Sorry to people who worked on it.) Coming from a platform like Native Instruments Kontakt, their KSP guide includes examples and use cases that are decently commented. At least they tell you possible values for function arguments.

So my encouragement is to USE THE FORUM!

@Lindon Sure, I can do that, but it doesn't address the points in my original post about script working for arbitrary path shapes or the quick mouse movements.

If it has to be done with trig, so be it!

Is there an easy way to detect if two paths intersect? I want to make a circular XY pad, but I want the outer perimeter of the draggable XY cursor (tiny circle) to stop at the pad's boundaries (larger circle). Ideally, the script would work for arbitrary path shapes.

I can check if the pad's boundaries contains my mouse cursor position while clicking or dragging, but that does not account for the shape of the draggable XY cursor. It also leads to a case where the draggable XY cursor stops in an odd position if I drag my mouse quickly outside of the pad's boundaries.

See the snippet for what I've done so far.

HiseSnippet 1359.3ocsW02SaaDF+LfaW7V2Vk1GfS8eVPxMDfR2jPSsk.LEsRaTSWEUHT0E6KNmv4NK6y.Vq7O6S19HsuAaOO2YmbYjzMgVQQDtmW+cOucOLHWEwKJT4DuVusJiS79J+gUR8jdSXBIo+gDuuz+nzTQVA+z2SNnJiUTviIddq+yn.ds1fX94Oe1ArTlLhOmDg7NkHh+RwTgdN0AO+WDooGyh4uUL0Q5m779QJYOUppD.y59cIYrnKXI7WwPwVym3cuihEZU9PMSyKHdabfJtZ3D0URq7uSTHFkxwCaSFBFxR9XUZLhXjJo2DQZ7flKcAArxf4gf0sgfuy+DQrXF84ghu0vfNWC23g2ZKBu0W.da6ButNvaIPxyARaXgzC8GFkKxzy4XSM8kZd9XFD1cghUVxZe8886o.Ij5NSYWvONGNLSi1Osa2PJ7qM2OHXqsnCXRdZ.jCJzzKY4zLY5oum9SzFKjv08TSyTR3P6GY39HP0OI6NEHUoNWk1iklNBxnsURCyZx0NuWNGhZTvgYrXJSFSiJygqoCd.8UWwiGvzSbPUjQQjXavTykNVoWoTf+NPjPiD4Qobvg5I21Mu.z.LvY6rWH7AhROdut0ec99ANXoCKNttAositV27RgVCtX4dBfXiW5F1MbW7CXafrqMqkpNNchprfSm.AnTgLIvDIwfrg9rP73RYjVnjs4WB29MC9sfVhwT6oNw4rD5G+H0dJJUDcAOdyfVfPsfOfSzSDETv9bZLWyizEzoF2loJDnYoWI.Qjfb7lvk4tERGUpoPEu0LwJZeJV2QEZ5Up7KnrB2rXGHTngVqh1LYEXbgTSExnzRncE9CL9rI8YfsP7zIloYcDE8kEhXNDyVpgNydotNz9c04PXq4VojoUvE4RtA2XTHgMBSNlBsUcm.cwP2sg.DwLgLGzcM.qZ.r+hbplwoB4biETF9QPxLgGC0k.oanA2TmoOLmcEpSdkdgL8.3hpeipDnxmmnSfjLnO1IwRiJSwlIrKp.FHUegU5uuvzf0jECZgUgHncuBOtot7rcNeqcfi6ruUvpEDrxQvcmIXPqjNigw6uHMsscTdQmjbdElFLnSWlaiw0c5pb712jCfxNgM+tXJXkY.LAjXGxfNalOsl0j7s.xz56TxDtP8CL65.UoLtn81c5tIp1MM.NFSCN.tdrzR85nzRiOcbIDhBO65vpv4A0v4gsy27Vto4hyvICPVFaCWk2fVcq6PsWxLnP5t.+lBp2vyvRGiWxvY8PGAMxNENPHM86M0SzEGR2NpYxdHL4Buk3HkYD6jaMMNaEBbNF4UJM+0x1FwCtIf9OYMd7R4U61Td9RYiKNj+oTrsrb5HdtKXQAgWSW7IZ+U+Ds6FDQ1WQbDTI6KE5WmwkqZuBR8SOve8q8ODJaw20qoAxkwy0BDBdGxuDVRx9JeK+C4EWnUYFYqitDu.sg6CZ1A.SdDA7R+88MYIx0tKcU4d3JQrdxLB+wu+7IbQxDsKESASySG.h9Fen6kNmvnjlkxZcu+B9AUSn4S+TT2wkL41qy.KRohwoTKtcEtRYMCHetvJM3ZKPWutxcky+2V45+JDen+.gNZxxw3ZKAiPV+yAFqWT8A9GMdL7.8b.tg+wm94YqTh8MmjSX5bATv4+pxoCgTcDG7tDpHw9Iu0vJe64t3YLBLjKiMGvBhZlaim8pYtcCSxTVTt5C0CkvUg+BCE.SRy+EPK+SvyzsIlNa237TXy7ODEsnotkh6bWUb26phO4tp3d2UEe5cUwe3tp3O9uqH9ON8hRsZpssgPNYvQlwhddGIw8vLUqj+FPM8iEX

@d-healey Hmm this might work for monospace fonts, but I get different results based on getting the string width of a space or any character. I don't see why the kerning adds a space at the end of a string. I don't think this is common.

Maybe Christoph can provide some insight? @Christoph-Hart

Might anyone know how to calculate that extra bit of kerning so I can account for it?

I see the source of my confusion.
Using g.setFontWithSpacing(font, size, spacing); results in a length of spacing at the end of the string.

For example, if I write
g.getStringWidth("TEXT");
I expect TEXT's width and spacing (shown with underscores) to be calculated as T_E_X_T.
Instead, it is calculated as T_E_X_T_.

So using
g.drawAlignedText("TEXT", [0, 0, this.getWidth(), this.getHeight()], "centred"); doesn't actually center the text due to that kerning offset.