@ulrik said in scroll event for script panel mouse callback:

Would it be possible to add

event.scroll and event.scrollValue

to the Script Panels MouseCallback?

@Christoph-Hart apologies since it looks like it's T-Shirt season for me--do you think this is a feature you can look at integrating? I am trying to add a Zoom/Scrolling feature to my panels and this is just what I need...

@d-healey just here to bump this. Have been reading in to this and it would be really interesting to have some of the features.

@Christoph-Hart I'll try it again but last time I tried it failed to compile. The recorder node is more or less what I am after though. There's a number of features my node possesses that aren't featured here like playback speed, reversing, etc. But I should study this node and see if I can't replicate it.

@daniloprates said in [Feature Request] Quickly open files:

hi_scripting/scripting/components/ScriptingCodeEditorHelpers.cpp:117

Ops, line 717, not 117

@d-healey Yes that is what I showed in the video, that it is possible

@d-healey I appreciate you looking into this, I'm learning quite a bit from your work here as well!

+1, I thought this was already possible

@Christoph-Hart would this be a nightmare to implement? it's a pretty critical feature for any sort of guitar amp software (most guitarists don't want to wait for a DAW to load lol)

@Orvillain haha one more lane, bro! I haven't tested 8 pages but I can imagine that it runs against the same node dimension limitation as the parameters before.

@Christoph-Hart

Gotcha. Maybe I'm thinking about this all the wrong way, and the best approach for me is to use the classic method of handling all my RR logic inside a midi processor script.

I haven't got to implementing any of this yet. I'm still just thinking about it. But as I see it, and from experience, a hihat needs the following:

Ability to trigger multiple articulations, with round robin functionality. Ability to fade out or "choke" earlier voices when a new voice of a different articulation is triggered (Open to closed) Ability to crossfade from one articulation to another, based on incoming midi CC (usually CC4) Some way to trigger the 'tail' of a 'more open' articulation when going quickly from closed to open. Instantly choke all voices when a pedal articulation is triggered.

I was hoping the complex group functionality would do a good chunk of this. But I suppose it is the wrong tool?

@Lindon make a normalised parameter in a network, apply a converter, send it to a global cable, grab the cable in UI script, in the cable callback, set the attribute... easy, straight, no math... oh wait, cables are normalised! So ask @Christoph-Hart to make non-normalised cables... ahahah...

0b2a1652422e5076d5c76780f91339b9.jpg

so:

the function is indeed called when loading a samplemap and

volume pan pitch

is correctly applied to the buffers, I haven't tested the range properties but they should work too if the other ones are processed.

Are you sure that this is not something else on your side?

@ulrik Nice ! thankyou.
I have found out the reason. Once you disable 079ee8c3-1545-4bef-8a34-81910dad4b19-image.png it Tooltip will not be shown.

HiseSnippet 833.3ocsU0saRDDEdFfwTn1Fahd+5cslFCPoHDuPr7iRrzRDrQupYX1A1Ic2YH6NzVzXhOZ9.3CiuA3L6tzcVKUMDKWrgy24b14a+N+L88EDZPfvG.KLb9TJ.9Pzf4boSSGLiC51B.2F0CGHo9VQPGMeJNHfZCfvruQC.ymCD96mu5HrKlSnIP.vYBFgdLyiISP623cLW2NXa5PlmQzUZzkH3MEthYJ9jEUDLESt.OgdBVGVFD3s3.G.7YnhjQUn13pzZkOXjc8J10o3pkqb3nCqWmPHkqRJYWsDsL.9f11LovefDKoA.XtiD1yG3HthGc.mwBXiboZiRfApSNBtiv0V+IpQAMcXt18WJTA.0aoehrkMR1dLpGylcCdh78nPGVIYXJfvLooW1TzqjI8JZPuUPInAkxEQocPCH9roxDOZ9rIpKWUMGiU0ISpDEK.9cTSgJ.t74d3Knc7UF2jvtUKVbeK0i8d43YbhjI3VB9IBI8T9t6U3KExW3qEr9cWiGuRe5iwW35R8Woacqg+eJwc4y7FQ8225Rr6L5MAp97Sqon6VSMK4jnuZi.E7tbl7zoT9c0H.hkJ0+9P2VXIVWHhwTwMk5KYZJ.aQuTMFDUVxiZQCtPJlp5naJ7lJ352.bCYn2shKZGiGQcALa87mARIv0lSWyMMthYKcR.9TCGJahizDQJDtRl5jeJZnCKvR5PshwrFK7U1JP2vilpDQbnNAyBL34lx398HV0wUfkL9jgLUnZ59jU3vj0e6rFyMMRy5Fe9VrtUiXEMR91FMLhv8wbEMGMY49h7OnVsZKzYvjTuDzEKVbPZzxZ3kpljdsLUv+HZG0sFmTCxB6YtXY5oa8NvXGp1yTiT54Fd.SN2bG4+sQ9+UJtCpOSRbVMGyrBNpZhuO3X7hxsPsGOlRjIDLGpyGue1JBduXltGrGV5yTsfnSl4MPUoIT0oyUsO50CvL5A4H6hZasBLfxsCMTMDKhcVRaCicVZoSfGl3KNmDsTRuJdiPDEm3gWakWc+ox1pDHbQkoN6otY3bBI8q5VIVdcS7f0MwJqahGttIVccS7Eqah096Ipu390yjBunwF.nW+1ga4gv1b8twvtUvu.jfqElA

@Orvillain
There is an audio render snippet in the snippet browser. Maybe you can build your own exporter based on that?

@Rognvald

To answer my own question.. :)

To add another Lottie animation in a HISE project, you'll need to first create a new Lottie panel on the UI and then assign a different JSON or B64 string to this new panel using the set animation function. This is done by adding a second animation element and using a distinct variable to hold its data, as HISE's set animation command expects to be assigned a unique animation element.

// Example for assigning the new animation to the panel
const secondAnimationData = "PASTE_YOUR_NEW_B64_STRING_OR_JSON_HERE"; // Replace with your actual data
const myLottiePanel2 = Content.getComponent("MyNewLottiePanel"); // Assuming your new panel is named "MyNewLottiePanel"
myLottiePanel2.set animation(secondAnimationData);