@ustk Awesome, that looks like it'll work great, though I'm getting slight flashbacks to similar control-layering jankyness in Kontakt.

For anyone reading this later, the solution is to script a panel to have mouse interaction slider behavior, or to use an invisible slider for mouse interaction and the panel only for drawing.

You can change which image is loaded using ScriptPanel.loadImage, and update the drawing of the panel with Graphics.drawImage.

David's tutorial covers a lot of relevant stuff here

I don't know what the situation is with IPP now in HISE, but the old dropbox link expired so here's an internetarchive link just in case: https://archive.org/details/intel-ipp

Making a value persistent can still be very tricky to figure out in HISE as compared to Kontakt.

For integers or booleans, you can use a knob or button, which have saveInPreset enabled by default, and use the setValue() and getValue() methods to store and retrieve the value.

In some cases though you inevitably need to store text or an object.

The trick is to create a panel, set storeInPreset to true, then store your object to the panel using setValue(), not panel.data. Only the former is persistent.

Here is a stripped down snippet with a simple example:

HiseSnippet 1233.3ocsVs0aiTCE1SaGXSfshUhmQVyKjVhZSBYaK6BhcaZKa.ZaDoag2V43wSGSmXOx1oYip5+Y9G.GamIYRZJKphcdHJ9b86bwmi6ojTlVKUnfpWLImgB97v9SDlzNoDt.08HTvlgmRzFlB6Ic3jbhVyhQAAq+SVBAU1.499qe7PRFQPYyIgPWJ4T1uxGxMyo16U+BOK6DRL6B9vRR29UcoRQGYlbDfm0CafxIzqIWwNiXEasPzaH5TTv1gwMa2L4.JYuCZ1tEk15f8a8c6SYjjD1dMe99sOHocBg1nEJ3SNNlajp9FhgoQAabnLdR+T4Xg2AWx07AYL6gln9fm8jOQlEaCQKUTmTdVbuhDkFAVo27z159z1WFdJOlOi97z2W3XfmqQ4DXvZKBu0W.dMKCuFkf2JfTPIHsgGROKrOUwyMy4XwymE1U.USH8vV.JdYQqsYXXGIHgvryPx0rSTvgYZTqUiF0wMazXqWVEjRKyX6PyXDUMf.T6zFbNQvxv+.tvHj33dVR0hbbhpiAKzXl3CFYLRwhxeniVsHOun5MpumUgpNCrilYpEoI2v5J5oXvon5F0HFHfW9UIPBISCRf2c2KRYE9jRxxF.MXXcpbTVLVJxlfS3JFdbJCXmwoWyhqVUwtBmyTZt1BvKIJ.sQQVi86fnDgAaR4Z7MDEm.EKrQhGvJoQ0R.yFkJYVmottlmy4hozgffKx3BFNYjfZ3.JWRhZT4vbo.LacviYPbea0JPXwduABHgPZrNWC8TrXKRbxTGqkXt4q03wJRdNvgKvDAVN3OYTS0J.v5UJ.AMpcqAr3KhdCKKSBwGCxJtef.UKGxvwDCI5N.u2U8dPdElaJTgbFXQH0LSXK3O2l3Akr9wCXrLwcvWwwuF.w34DlW4f.btd9z+NUqLqOorueYAcZJQbEKtlqcnCYjloe.Sa6Erw2L6sb0ywnbwa2cOjQslDWt+ykzrvDxjJa0XlSrdPCMd3LIIFz9LoA5eRI9PZIw1lj.WC2FDuqfCk+wobZJdHiHzKjAvWwLfQugoFq3FnFf4I3IxQfymTjw3FaKf2R2q9sXXsxNtkuO3X.o3hgB4Jt.tEZY5X8BbD9a..Xmgrfta4agl4aovlCNWTaqpfa.V3kYkjrRdSQaFSsR11MMp+MEqIFMb.SUDiEBBSSWbDc3COht7FDpebVIA8I6yyYhGZuBZ5LP637onBD03Fl+zhg41ZChCir+zPWcB4vKJ3qB+49me1sQ16sQP59Lo6Np6VazcHza6dDbrvzfW.OCUBC2FTAGwtA1S62aTI7Hl9ZiLGV41on1CA9GBHuGjIvtGeRweJeIvRyQ79lbyolzO22YymD5m6sjQ+9UXT+SJt21OXuqLdTFwr3xX6SVlx.J+KrAztkSn4lIkeRy+aan+uBwmE1ianoqFiqsBLBkzOFXb56ZdZ3wvipnl4.bivS9iONOhA8axQFt3pSIFE2V3Oazv9vaAoLv6BnEyd8KXMaOj+bih5eelH1c3uguoLaVzwYY1rfIZHgpjui5udYe4zSbT.LIbuxrB7bW3LtYwEq444gvC4dGktnotmhsdrJ9sOVEa+XU74OVE26wp39OVEO3Cqn8c1udjQNzesAgNs2wtYdAAGKrKFccqn+gNTucw

ALSO: if the data you're trying to store contains any undefined values, it will appear to work correctly, but will restore to a value of 0.0.

This should eventually be added to the documentation. Just need to find a place to put it.

I started the slider as LaF but moved to a panel when I couldn't figure out an elegant way to do the animation, interesting that that's the one part not achievable with LaF.

Coming from Kontakt, the ability to have smooth transitions and (gasp) actual hover states for all controls is a huge win. The average user probably can't articulate the difference, but I think in testing a UI with smoothed hover states would get more positive feedback. When trying to sell something new to a group of people who have been used to Kontakt for potentially decades, I'm convinced this kind of UI polish can help make a HISE library stand out as better in every way than what people have been used to.

I believe I used a separate label so the text wouldn't be part of the hover target.

In context:

Easy to customize!

HiseSnippet 1890.3ocsXs0aaajEdnSTPk1Tfs.6S8oI5gcohYzMaqj.2z1DeYqQiSDhRylEKJJFSNRbfImgfbjsUKxh9ea+2rOs+C5dNyPJRJK4jZrqfgk3bt8clykYNbbpxmmkoRINsd6hDNw49MlrPpCOHjIjjSNj37YMFmxy3ZxKVjvxx3ADGm67WQpNMuKw74+7MufEwj97xkHj2oD97WJhE5xUG+seuHJ5XV.+sh3Jbu62dhuRdfJRMGPxcZzmjv7OmMi+JFx1VMHeGKKj37vF82aDm+3clFDv1YmfQiF8zm7zce5.1z96xNavnmt6vce7vm73oDm6cTfPqRmnYZdFnzWnBVLITcozZf2IxDmEwwGFPl.V1tL4fPQTv3hskLBw4tiK2jticS5O03TQfX45kaV+QCAZoDU2zb15lfzfeGPxoBjtqEReQiI9ohDcIEDO+gFmH07zoLH1TEJVdIa8uueiCT.GRc2X147iSgGVJg6t866QGrW+N62pkPFIjb5z4ResPIoAb+HVJeRjHfm5Jg3j2UdK7NWpNah3m4c9kVMiT9rHZlgC5ynEFhEDLlI4Q4BQeDsPHuEfkZZEna.Sy5VPADu3mqvAhp2FJ7OWBdMv1f8o85AAD4LN0fX8Rhg7T9RggLZ21gbwrPc6knl9P5P51T2Ma.fgNcPS774ZULSK.WLZAEzFMAcJpUk0MCWxf3JlY7RNKU11SmNmWwUMLkwtfehzVqsdN.Kot7.3+mAEGYs8ZePD.qLO52ot.1g+yzCSYylIjyZWWxSUyy3Exk6auVZVsNiigzX8aTy0fK6VDocm0g9KVdLzgm2+C0kCKlSulALqtZ.MDg5ykhXHT0Gnkx0ySk4II625CWOQqtoWlVsZbGByYqIfseA+XH9Mr.w75LWIqpjuimGEsj2JBtMc85FW8uIBzgEpdFWad1sCjc6NDxZpqVSFjUB0TPDNk4qmmqI5kveLolpUzfT1ksZVEauGrQceeaJTIFm39nUfNjGW.l2whlyAv7PpaIVA5qHgI4tiWeukL0olO92y2NJEYeDbyvb.ay6kVzs8YyrK0tCpjd8fjyKoQ7oZipZ0TL0Z+2S+5U2cZ0DzI55uDSDqSzytK3YATsuVtkzw.qd8dCVJZ2SgrH32PkJ.PoDpVzPKBCbphjsWM7+UOqL3tFXgRrL7lCdu0jBrpKTG686tmEw1cZdTjHIi+B0bY.l.9OrNbMOzqZZID1V84erbK2TwQmBm6VORY+Jq6kBc3oyizhjHAO34QIgrJQQglGa4bX6BWqdgrI7NqKZfirH2slGTDLLfAS0yoto7lRKVj477f.JC1rz5HNVTT1QGd.O1hJftu7TedBVDAAYnwrenwXgpTwOCG7jmA2JOBtVjtRVDrONn6PnTcyckx6h5xu.NXC6MgoRlG55i8l4A3h4w0KvhPHdlyPLJ4gvg+um1iV59WhIMVOuoY0rhxWaUtQKd8612aP29UXy2bjWfKtBf2JHA72YaFFW8+dqSw.do8sIfO3Yql7.GqTHd4h.vpH090XfAYa3IjpYo487gCIKQplkZOIxcvHSC1Aihyn+S5n9SSxJ3JkmfmjbRbLOP.WCKZQ9N1MDisJsH7dM.C24Xsth4Ttsgi45N.OoacBaX4qAE.alnFJ7DURtMQ49.Bulaz382rweDZ7c16lL9Wgr7IX7aXyaM6bUSVhERuX1UkmbC02IPv6TlNrKPrfMfkx6CXIxtxEYFUg0N858Rt9ujUb4SJSFPgpHSkN1Xe1CZAyQjoowKlTbsy5WTssMn11au9l+.8VvqsajTmphVdWlBZuVlSAuJbUApbNm2xNpgPOLSFHdPwJrWo81RAf7YtzHv2Ccw2n.CqXBnossUcwJo7.6IIF8XtQ30iKWycb8UwIJITv4YaLzoEDm.hYpHd2jT7RWseaHu3V7WpROO6Az1v4dGIgqZxw1F+PhFRXbw1AeX+k1RIekRyesz0nRH5QWkzzoqkVNzhvTv0PNO4byB5JmGeFOspCgLBSJUe7q68oM9kucrkJLpjmHE5Wmvye9XUT.NVE96qOrFIetGbrsbDBrpMCs84ECsgiNPDA3z11cZhA73Dx6X97u9FxObxgPsagZ.MBVAN0SKPmw4P9Ev711YAa13Pd14Pgrg27.LLL3G0nWQbZ37H.yKveLD9gcbFPk2694y0uxvLHiNvxUGeoXs5CrPb9xFaZhERQUDZoeC9fVpLyGWk7qjUVcHZGB429Ux0GGFFDWELOhoqOcN9dKxI.4L0FIFG6UlIzKp9dM9cLxd+abj8OUH9EMFKf6trdLt0ZvHjO7+CLl+hN97FGMcJ2WWBv61332eaeqFeDyam7bFz6OUfYhuZd7DHL6yww4gb0LLduEVQYetuM9SHS3x.yCXlSNwAEIgHwAEDIwL+T0O4aqCwWkxmYVAvjz7plZ13T7Y5fxBvh84XHk+m78qqpqI3vaqf6baEb2aqf6caEbzsUvGeaE7IebAwNREuTFnrgPNc7QlFlNNGYZYYxVI+WP3nMW1

@Morphoice The solution I used was to keep track of all note on events, then if you ever receive two note ons in a row on the same note you know you've received some illegal MIDI.

It's pretty easy if on noteOn you check and store the event ID to an array (or MIDIlist I suppose) like

onNoteOn {
	if (events[Message.getNoteNumber()]){
		Console.print(You've just received some illegal MIDI!);
	} else {
		events[Message.getNoteNumber()] = Message.getEventId();
	}
}

onRelease {
	events[Message.getNoteNumber()] = undefined;
}

How you handle the lawbreakers is up to you, but at a minimum it's best to stop everything on that note, as this situation breaks the assumption that every note on will have a corresponding note off.

In my case I'm using artificial events, so stopping them all is easy. I don't actually know how you'd go about stopping the normal events.

Give Synth.allNotesOff() a try, I know that doesn't affect notes with a timestamp in the future but I assume it works on stuck regular events.

It would be nice if we got this built in similar to setfixnoteonafternoteoff

I'll add to the documentation eventually, but this might help anybody trying to set this up.

HISE and Juce will segfault without an X11 server running, so just calling them from the command line over ssh will probably look like things are broken. You should run {HISE_BINARY} --help to check if things are working.

This is my build.sh script, which I put in a Packaging folder in the HISE project directory:

#!/bin/bash
parent_path=$( cd "$(dirname "${BASH_SOURCE[0]}")" ; pwd -P ) #Makes it so you can call the script from anywhere
cd "$parent_path"
{HISE Binary} export ../XmlPresetBackups/ProjectName.xml -t:'instrument' -p:'VST' -a:'x64'
cd "../Binaries"
source ./batchCompileLinux.sh
scp -r "$parent_path/../Binaries/Builds/LinuxMakefile/build/ProjectName.vst3/" simon@{laptop_ip}:/home/simon/.vst3/ #Copies the vst to my laptop

Question can't be empty.

@Chazrox I use image magic in the terminal. With imagemagic installed, I just

cd /path/to/folder/with/frames
convert -append *.png spriteSheet.png

@Robert-Puza Any time you are compiling something on Linux and you get a "package not found" error or something of that sort, the first thing to do is check if your distro has a slightly different name for the package and install it. Some distros include "lib" at the start of library packages, some don't, sometimes there's a - in one distro but not in another. This is why instructions don't always include one line you can copy paste to install dependencies: each distro needs a slightly different list.

As you're on Mint, you use apt. I would type "apt search webkit2gtk" and see what comes up. I believe Mint does have the package, but the correct name is actually "libwebkit2gtk-4.0-dev", which is why it didn't get installed when you copied the line from the readme.

Either way, using David's fork is a good idea.

@x_Luv2xcreate Snippets contain more than just the script, but also modules, effects, that kind of thing. They're more useful than sharing just code, since all the stuff the code relies on is also transmitted, and make discussing issues on the forum much easier.

You can find snippets in the HISE snippets browser, on the forum, on github. You can load a snippet with ctrl + shift + v.

HISE | Docs

(docs.hise.dev)

@Elezeid HISE projects, including sample maps, are trackable in git. It's well worth using and has saved me repeating work several times.

@d-healey Nope, it's the only namespace in the project and it was just to have some nice prefixes on the constants. It feels like something with variable hoisting but I'll check properly later.

@d-healey The constants were the only thing in the namespace, vowel.aa, vowel.ee, vowel.uu, etc.

@d-healey Of course, later, was just putting it here so I remember to come back and investigate :)

I have some constants declared in a namespace, which are in a file that gets included at the top of my script.

For some reason these constants are not available in one particular function.

If I declare these constants in the exact same place, but without the namespace, they are available and it works fine.

I'll investigate more later!

Just the inner shadows:

No blendlayer:

"Darken":

"Normal":

Other blend modes seem fine. Anyone know what's going on?

@ustk You can't store strings to value. I believe the example was assuming that when retrieving the value, you'd go

this.data.values = ["First Item", "Second Item", "Third Item"];
this.data.setValue(0);

var gimmeTheValue = this.data.values[this.data.getValue()];

More generally I think Christoph was getting at the idea of only storing integers to value whenever possible, and using a lookup table if you need something more complex.

That said I've been using a panel to store a big ol object with nested objects and arrays, and haven't noticed anything suspicious, so I'm not sure if he knows something we don't or if it's just cleaner that way.

I tried to provide some clarity to the docs here, feel free to contribute: https://github.com/christophhart/hise_documentation/pull/48

@Morphoice The solution I used was to keep track of all note on events, then if you ever receive two note ons in a row on the same note you know you've received some illegal MIDI.

It's pretty easy if on noteOn you check and store the event ID to an array (or MIDIlist I suppose) like

onNoteOn {
	if (events[Message.getNoteNumber()]){
		Console.print(You've just received some illegal MIDI!);
	} else {
		events[Message.getNoteNumber()] = Message.getEventId();
	}
}

onRelease {
	events[Message.getNoteNumber()] = undefined;
}

How you handle the lawbreakers is up to you, but at a minimum it's best to stop everything on that note, as this situation breaks the assumption that every note on will have a corresponding note off.

In my case I'm using artificial events, so stopping them all is easy. I don't actually know how you'd go about stopping the normal events.

Give Synth.allNotesOff() a try, I know that doesn't affect notes with a timestamp in the future but I assume it works on stuck regular events.

It would be nice if we got this built in similar to setfixnoteonafternoteoff

The root cause of this was actually this bug: https://forum.hise.audio/topic/12055/control-callback-does-not-fire-in-non-ui-script-when-value-is-updated-from-onnote?_=1740472879585