@tonewolf Ah yeah, that's confusing and wrong :)

@d-healey Thanks! Everything's working as expected now!

@d-healey could be mislabeling - I think it just pulls the same property that you get in LAF (obj.valueNormalized) which has the sole purpose of letting you draw a slider value position without worrying about skew.

@jeffd
drawing the whole box out is working nicely

@d-healey awesome! thank you.

@treynterrio your onNote callback fires every time a key is pressed..

@CyberGen A list of License Manager API endpoints. Might be useful for those using the License Manager API.

Base Endpoint:
/wclm/v3
Methods: GET
Description: Base route for the wclm/v3 namespace.
Verify License:
/wclm/v3/verify
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for verifying a license.
Activate License:
/wclm/v3/activate
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for activating a license.
Deactivate License:
/wclm/v3/deactivate
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for deactivating a license.
Get License Details:
/wclm/v3/get-license-details
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for retrieving the details of a license.
Get Product API Meta:
/wclm/v3/get-product-api-meta
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for retrieving product API metadata.
Get License Status:
/wclm/v3/get-license-status
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for retrieving the status of a license.
Get Current User Licenses:
/wclm/v3/get-current-user-licenses
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for retrieving licenses associated with the current user.
Register License Key:
/wclm/v3/register-license-key
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for registering a new license key.
Set License Status:
/wclm/v3/set-license-status
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for setting the status of a license.
Create License Key:
/wclm/v3/create-license-key
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for creating a new license key.
Update License Key:
/wclm/v3/update-license-key
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for updating an existing license key.
Delete License Key:
/wclm/v3/delete-license-key
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for deleting a license key.
Add License Key Meta:
/wclm/v3/add-license-key-meta
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for adding metadata to a license key.
Update License Key Meta:
/wclm/v3/update-license-key-meta
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for updating metadata associated with a license key.
Delete License Key Meta:
/wclm/v3/delete-license-key-meta
Methods: GET, POST, PUT, PATCH, DELETE
Description: Endpoint for deleting metadata associated with a license key.

@d-healey ahh Legend! Thanks!

@Onik-Sisodiya Just got it figured out!! Thanks again

@d-healey I see! Thanks for your help!

@Casmat You can call the timer with framerates with 1000/fps.

If you have longer animations and find them stuttery (because the UI timer isn't accurate), you can be calculating timing differences between frames and compensating in the alpha increase. This should only be noticeable on very slow machines, for which you should have an option to disable animation anyway (although 4 timer ticks is nothing).

Then, there are the easings and the standard finterpTo interpolation that you can add.

The rabbit hole is very deep with animation.

@bendurso said in Choose Specific LFO Shapes via Knob or Button:

@DabDab This is what David said turned into a snippet :)

HiseSnippet 1053.3oc0V8taaaCDmx1pn16OHEqO.B4SNXdA1MooqHXXtwIdvXwIFSdcCHnnfl5rMQjHUknRiwPeF1aydL1yxdC1NJIaQ03kjZj8g4OXHd+g2Od79cGGEIYPbrLhXUe7hPfX841tKDp48lS4BxfiIVeo8PZrBhbxDczhPZbL3Qrrp9CZAV0qQR+8We+QTepfAEhHjWK4L3Td.WUHcT2ej662m5Ai4AFVue2ALonmzWlf3opcaRHkcIcFbFUaVEah0iNwiqjQtJpBhIV0NR5svct78hL6eMOlOwGzK5PbwMJSbeoumFw5uI8ly88Fs7bGSvcYTQVnZVV3o1C4d7UxKxFakpvovCy7gUkxvqZI30wDdsMf2ZfjkAjpkAomX6xh3gpBMZ77Y1CD3kyTJl1MgRlsjJurhcOIZgPsa.8RneDtXkGMOnc6VN3e6bXiFXpOV4bEEunkASjGIutiy24rz4YfBEGJE3hlauxhsWimCDdv0nqWzokyyZ4rWKm8a47h2bngcm1+7gRuDeJlrzQIsjSGiURatMZiSgQoAhK74BvYZhfo3RgitXIGHZbFI8axVBxVXf7SfcZ7aMpWJb6FCpWoTQ7IIJnYYU+B8JnuLJPmwaYbZtHcub9FmNuAwwGPnbm4EcXxAUOpu+DrRt4Mw6NGZbXNSpfyEMSgbiOzv4iUMc5Z0kuU9PzZUq4XQ2liMEIASfHyDl1Prvqb07i92qlMIarrLiggRw.AWcdHjutfN1YM09j7TqlEjiPzTUJGXqbNvxzHg6oo.qxpjzifYKIxOO3Xphtbyv8EiUHDo35ij0wvUX+oLBVc6ig3KUxvTayuSwi88LzWSrrs9SLnKze7G3GbEDfAww1EqZaLNhSEy7gFtz22v8cIzH7SEDFSBno9Zm1a7F7driyxBTy1P5du4JvayRbeM+VDyUKLSDebuoZ2uay6n0oYepsxvqsMxoxAYYN7cCx9Qv6R.AyP3i6pGTLnXNS2euqllNMmlZ59ovLLPlRFC38H1cgYNSxMPJUy4hYkG+7ztmJkgmHnXZvybSFMmFqYeHitz1fa6XY1vwd9R1klJGLSHifLFso7dIwJYvxCP5PMcQPZMp0E1Gr+t3uoes9+W1C+auyeXVS9DlM041mMU4dVi9UoW+qtm0EBOnkosWaY5Zao7Ig3UEg+O.wOwdDWwlu9FAUVCdIj+ywa9Sn9B6SlNEXpBvVyt+udquW5gAJ+jLQgj6gTbFutw5YIAt3KJY.hDg.7i0Maqn4hYqaqWmRnAgW5h+F+kqridsUtxNKUhsrYQx2xxFOoIEONUBhIQ5aUqiOZFW6biIRDR.99w2xXk2pa33y1TG2aScb+M0wmuoNdvl53K1TG+161Q8y6eUB1iNiNQHCGcRV2YqUiFrpR9G.Ii9IR

Thank you so much. I understood the array portion but couldn't figure out how to arrange or rather index Sine, saw etc. Your snippet helped a lot. Now it's clear with [1, 2, 3, 4, 7]

It turns out very well. Thank you. Cheers !!

@Christoph-Hart ah, right, forgot that you can draw out of bounds.

thanks.

@Christoph-Hart said in setMultiGroupIndex vs. discrete Samplers:

Yeah one sampler is probably the way I would go here.

Nope.

For release samples you definitely want to use a separate sampler.

Yup.

The rule of thumb is: Use a dedicated sampler as soon as you would start treating groups with a different logic. If the hammer releases should behave differently than the normal ones (eg. the normal ones need to adjust their gain depending on how long the note was played, while the hammer sounds are always at the same volume), then these things should go into a dedicated sampler.

8 Samplers is absolutely no problem and if you follow the advice of @aaronventure and set the voice limit of every instance to the absolute minimum that you can tolerate, then there is almost no overhead in memory footprint as compared to using one sampler.

Thanks for the input Chris. Your rule of thumb is where I was intuitively heading, so good to have it endorsed.

@Orvillain Wow Thank you very much for this detailed explanation! I am grateful to you :folded_hands:

@meto396 post a snippet.

@Christoph-Hart darn. okay, thanks for the reply. :)

@aaronventure yes sensible request, the function even already has a bool parameter to align this to the component or not, but I'm not using it in the broadcaster's context menu yet (the panel's context menus can do this though).