@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).

@kekient I recommend playing around with broadcasters. They're meant for exactly this sort of situation - controlling multiple things at once from a callback function.

This is currently my area of exploration too, and making good progress with it.

@d-healey said in Change Key Width using code:

Link Preview Image Updating FloatingTile Content Data

Here's an example that sets the lowest key of the keyboard floating tile. First we get the Data property, which is a string. We convert this to an object usi...

favicon

Forum (forum.hise.audio)

Cheers man! Bit of hunting for that trace(data) technique, but that has helped!

Thank you all for your quick responses! I have been on the move lately so not much opportunity to reply.

@Christoph-Hart thank you, I think this is the exact solution I am looking for. I haven't explored the macro control system to date so this looks like the proper time. Thank you for providing the snippet.

@d-healey I am not on my main system but here is 2 screen recordings of what I am talking about. It may be a DAW/Plugin dependent request, but the first recording is an Arturia plugin, the second is one made in HISE:

@Lindon you are correct, I think it is true with most DAWs. My hope was (and the macro control system seems to be the solution) is to set all parameters which exposed to the DAW, but only have visible/assignable the ones the user selects (so maximum 64 in the macro control scenario).

Screen Recording 2024-08-06 at 12.07.20 PM (1).gif

Screen Recording 2024-08-06 at 12.09.17 PM (1).gif

@ThomAce Cheers and best of luck on the plugin - seems like you're well-equipped.

@aulicon said in Polyphony in the age of timers:

@d-healey Sounds genius but I'm having difficulty following the sub-dividing the timer part.
Could you please show a snippet of the code where you do so?

so lets say you have two things you want to happen.. one every 200 milliseconds, one every 150 milliseconds...

so you run a timer at 50 milliseconds and each time it executes you add 1 to a counter...

when the counter modulo 4 = 0 (if counter % 4 == 0) do the first thing, when the counter modulo 3 = 0 do the second thing...

This is exactly how we used to do it in Kontakt...

@Giuseppe said in User defined Component properties via JSON:

"continue" command to keep track of which button triggered the callback

continue is used in loops to skip the current cycle.

@ulrik @aaronventure @d-healey
After trimming with timers in different setups I found that "CallAfterDelay()" was the best solution!
Thanks to you all!

@d-healey thx

@d-healey
Perfect, thank you !

@treynterrio other way around maxValue - value