@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

I would really just prefer a way to use an external editor. After several weeks of intense scripting work using only the HISE editor, the low contrast color scheme, lack of syntax highlighting, lack of keyboard shortcuts, slower response time, and many other quirks make me far prefer the (sadly proprietary) Sublime text.

I don't doubt that it will eventually be on par, but for the sake of getting work done I really need to be in Sublime at the moment. If the fastest way to reload the script is to load the xml I'll just keep doing that.

@Robert-Puza You don't have to re-compile, you can just copy the "HISE Standalone" executable. You only need the source when exporting a plugin or compiling HISE itself.

@Robert-Puza I don't know of any third party software that works with ncw. You'll need to load the library in Kontakt, and go file > save as and uncheck "Compress Samples". The good news is Kontakt works well with WINE.

Mostly I find the script editors are a little slow. It's difficult to quantify but typing, navigating, and selecting text definitely feels less responsive than in a typical text editor. When typing, some characters appear with a microdelay.

If the ScriptWatchTable is onscreen, general performance gets worse.

Resizing panels is verrry slow, but I think that's been the case forever.

Dragging in the mapping editor is usually quite slow, the selection refreshes maybe three times a second. Releasing the mouse during a selection sometimes causes HISE to freeze. The number of samples mapped doesn't really seem to have an effect. -- I just noticed this appears to be affected by the area of the mapping window.

For me, with OpenGL enabled the application is next to unusable, all clicks take seconds to register if they do at all.

So, how's performance for you all?

Fedora 41, Wayland session, i7 4790k, RX 6600 XT. Build is from Master, built in a Debian 11 VM.

Ah it's a permissions thing. If you go into settings and allow full disk access to either Xcode or Projucer (I just enabled both), it builds and opens properly.

Thank you David. Providing a snippet is above and beyond, as usual.

@Lindon In Kontakt, a velocity curve does not work well if you go to extremes like I described. There is no way that I am aware of to decouple the velocity that is sent to the sample map from the velocity sent to the vel > volume modulator.

Imagine this were a user-drawn velocity curve taking the lowest dynamic layer and spreading it across the full velocity range of the keyboard:

In a situation like this, your input with 127 values gets quantized to something like 10-20 values.

With the HISE global modulator, the velocity sent to the sample map is different from the velocity sent to the volume modulator, which is exactly what I was after.

Hi there. I have a more conceptual question this time.

I'm trying to build a basic keyboard instrument with a sensitivity slider that does more than act as a LUT for incoming MIDI.

Imagine a soft/hard knob on an instrument with six dynamic layers. All the way soft would heavily weight incoming MIDI towards the lowest dynamic levels, and velocity 127 would trigger only dynamic level 3, with the highest two dynamic levels omitted entirely.

Same vice versa. With the knob all the way at "hard", incoming MIDI is weighted towards higher dynamics, and a note with velocity of 1 would trigger dynamic level 3, the quietest two dynamic levels being omitted entirely.

With the knob in the middle, you'd get a normal linear response.

If this were Kontakt, I would put each dynamic layer in a separate group and do the "which group to play from" decision making and velocity scaling in scripting. Each group would have a velocity>volume modulator with an upwards slanting curve such that each dynamic layer, when played with a velocity of 1, approximately matches the dynamic layer below it.

The idea is to be able to select one or multiple dynamic layers and map them across the velocity range without running into quantization like you'd get with a simple MIDI input LUT.

In HISE I'm guessing I could use separate samplers or rr groups to select which dynamic layer to play. Or maybe the velocity mapping secretly uses floats and there's a way to play with fractional velocities?

I'm asking now before exploring options thoroughly in case there's a very clever solution right off the bat. It's difficult to think outside the box when you've been stuck in Kontakt for years.

Huge thank you to @DanH for having the foresight to save the old IPP installers (I was kicking myself for not doing the same). I can confirm that using IPP from the link in his post here works fine.

Here is the direct link to the correct IPP version.

Here is a backup link in case the Dropbox one stops working for whatever reason.

This kind of nonsense in software development drives me nuts. If Intel had just kept the old links up we could have avoided wasting our collective time.

@Christoph-Hart Ahaaaahhh that's the step I was missing, thanks very much!

@d-healey They'll be shipped with the plugin, with no option to let the user add more.

@Christoph-Hart I did!

const ConvolutionReverb = Synth.getAudioSampleProcessor("Convolution Reverb");
const reverbSelector = Content.addComboBox("reverbSelctor", 10, 150);
reverbSelector.set("items","");

Engine.loadAudioFilesIntoPool();
	
const impulseFolder = FileSystem.getFolder(FileSystem.AudioFiles);
const impulses = FileSystem.findFiles(impulseFolder, "*" , false);
for(ir in impulses){
	reverbSelector.addItem(ir.toString(ir.Filename).replace(".wav",""));
}

inline function onreverbSelectorControl(component, value)
{
	local impulse = impulses[value - 1].toString(impulses[value - 1].Filename);
	ConvolutionReverb.setFile("{PROJECT_FOLDER}" + impulse);
};

reverbSelector.setControlCallback(onreverbSelectorControl);

I'm still missing something in doing a basic IR loader.

I'm getting the list of audio files with getFolder(FileSystem.AudioFiles) as suggested in this thread, and loading the IRs with setFile("{PROJECT_FOLDER}" + impulseName). However in the exported plugin they don't show up in the combobox, I'm guessing because I'm supposed to use {PROJECT_FOLDER} instead as FileSystem.AudioFiles doesn't resolve.

I think I should get a file object for {PROJECT_FOLDER} so I can list the files with findFiles, but I couldn't find a function to do that in the API.

HiseSnippet 2059.3ocuXszaibbDdFIMFVz4wZi8GPCdvfxQQfCeSXDDI9RRYEkXDo0tNAFKZMSSx1ZltI5oGsKggO3a4TNleO4+PNj+F4dNjT87dFNd8tBNgGHl96qqpqtppq9wLA2h34wEZ5UVrcCQS+WXLeKStd3ZLkoc4HM8ekwTrmjHPgPC1tA64Qr0z02+bEf9gGnE76e86GfcvLKRJjl1cbpE4JpKUlhN6zWPcblfsIKntY5cqSuzhyFxc39f8ruQcsMXqGvqHWiUcaOCsKvdq0z+Bi5s6PHcatz1F2rocmNc52qeq9l3k0agu2rS+VMZ0sQutK0z+nw1TIWLWhkDOPoC31amul+FV3.bG0iduCQ0vTaNLxgvZCWScrmE6b7zzzOXVpqZ+PW0yMlRsoI3otrmEPfRkHqSSeu2kIY9AXR5YLoCBMoO0XtkftQlxnrmOw3RFDAWhgXSVSIruZ68C6aLjC8fIOwE+.Yh.ZjHQsN0qeLB96nurREH93IQPmej63Kob1sjGIh6Q+NTPVyIqHxy7so74X2MNjDqnV0LhfBkoJnuP0IBZOm3Pr.+BnqXiAaaOj6dOe.+s0plzKUmpdLxDrJy1JqJu7m3Qj0pRkDWupGWUMJUFyVQYjSb3X6.qaB0g3ASP9LN2oFziCirDp6FeGOxDtiMQYHpNNeKj86plYgv0x.lpsjISjJ7xK8RJyNne0xMDGip9EUQGiVhAHPEKAWEUfnrD0bz2U4vByOvqbInSnimH4ykBJak5ak5YvBkiNQP13nBbUO4M3GC7Afp+9JUnLGvMfV5yrBhCbVdMqb6BvgXwc2vYP.3XziXGexQU.ivgagchMKXxEaf+4ftf9sHyuIi4TBYh8At6cRfTAMUGpU86lc6M+gwCW75I2b0nw298UQ+l3wRMKfn4tg6HCeH1w4dnhQsejI1QeYlo90bI4FVsf4F3bPEoVtrTtHU4.4AkQqJnIdWBVi46duJvm5YUcDV.mupvG89UUvJbkRlNxYWxnxa1PhZGjnYG98t0PzhVpoplDYgPWkA0RdVTsj3kfZTPM+ZibqC0BlFIkvO8Ocp1Wc4HrDGqPP2v3sgHjT0zReD4QXCgvhUGZLh38fjuInuQ4bvT+CX3eqltgdEXj2p93uAeDrvWau+YEiJlnKfLBOTcSzUXwJRPyTzFnoDapuaA3ln4tvWEPaEohOGcMAKRwaGqjhDchTSQ7tIJZDV7PJduTbBYSJd+zAHGgYcUYRKvwl2RMMQmCg7BfMPywLaHjW.uInTlWAOiYKzPGvnKf1FMP.acT.sC5LW0wCrwEbjlcQCHBUEmhJpGZ.2SBqJTsQmkRzOGwfDhFvbcM0BuhmWSMLQ2QILFt.bCzK4BHGWVbnazDsXMAclvZ8H+GHo3sPKD7sno9dTqBhzFbcTlD1fy4Q3iThNPjwZMlQsJ3SZzMRjyIv5I6JMQ2x4tA4gykpcLf4bBViXrAfSm6QRYZlxLAxfRvaEiOLEqcL1nTrNwXiSw5FjDADvZsTzdQSbUyTz9nKH3G2lGER6BySeImaSXEHMiR5KkrQjjKf571E3ZFmkWFYqHsVFWazHQvhC3zWpBqoLcPi9VLaE2qfDciz1c72VfoG5bGUBddz9nYDgkumWvQWxRAokSwBnpLZBealgtgYxZ478uQRMg73Mi5+sEmdPd4tXv5P0lp4A6Dqhbnwy07n8PAmvq.ZezPh5Le4gaVGM.1Rs.XRh7KRwfEcXprf2qYSnJknfeqYKzM3GfqJTXl0Dxhmn71KCwaEGTyTBONLmkKoPdYjwkyKiqU9ZwYoZmDp1gpShTCDzUqk4H6lHWIj8PufB9xxLk9n4Lrnz4Grj6tfCeUFmI5rOeZoLMPCGUJQSzMv9CkwzJr5PYTsgx72G2FpekkqSNtA43.+gOrAiLQoAJBJZCkmSipwP4YShqkSGGYKmsPrMGWlMs2krS9HeNttEC84X6kp1xn6WL0HKKDjC78kNYfn7Ub1peDxFQ6VWNaynp3ky1BVcCU7d0qtJOd6rE8NiJp.dE3x3gwrq4B4ZHf5CailgnAZLVc4vh3Pbh6Wl.sPujTl.sQCgSM3hCqBjhCeYwU2u.p9fWQxv.G0.CivEbeurv8PCA+xLUXLErOr8ObQjTDv0CEYeCrkE5NH9P1lgxDs.1CwgnXy.2.clE1l3tE80XQVBvaSgi.PsyXFpiSggCsxx.0NbKXzezGKDYGvNnw9v4kyZdcQmC2IvNrslKN3Lu7fGRYm6++LiobaeGrL+yQndnlHBHfl6M.T2ym4Qkay9PNe.uQQ824aT79ZhepwLpzZc413dkXiv8K9egMF8xN+RiwKWBWcL0.OvXxqdmOiyAueCe50w9IeRmOK1Vxba4.a44F69ZJ4rsQhs4eZtu9u+RhLOjl1Ufgyrx4SuL7h1WQXqjqylPDYVWx13Kyh+UdD0wCVI39L6EqEDrcV8MSPrIN3biwEzgYzwe4eb5Hr6FXQc19LYxhnqHFA87SUuNP36.drQw2Hn70qpW+PyUMmMzU5HZky+9utulCmuABbBYLmBXLyNlWe+eldiNsagRevjaJVJnpg+ZeWnZHb4DH0hwHNdpgbO0EwCaWO1hlSX1AM9OvuHRSUa8HRyXx+uLFtXKA+0VgOQfJS8iCPf4MKHnbnwTUajYgWDP42o1zWaYkWU6HXimpfMepB15oJX6mpfcdpB18oJXueZAUOU8Y9RtaXcWMsoyFG7BN55iYXHKOnjh1+EQKgIp.

It's for keyswitching. In the realtime script, on note, if a note is in the KS range, it updates a knob. That knob is linked to a knob in the deferred UI script, so it can update the key colors on screen. That's it really. The keyswitching is working, because I can hear the articulation change, it's just the linking part that doesn't work.

Two switches that are set up the same way, to mirror something from the realtime script to the UI script, work fine.

It's tricky to debug as it only happens in a compiled vst or standalone. I'll probably try Christoph's logger next: https://forum.hise.audio//post/26752

@d-healey It behaved the same when it was in a constant. Is there another way besides using a global variable or linking controls together with a callback?

When I export my project, a control in my realtime script that should be controlling a knob in the deferred script, isn't. The behavior is the same whether I use the linkedTo field or a callback. I thought maybe the reference to the other script was ending up undefined on init, so I tried getting the reference in the callback, but with the same result.

inline function oncurrentPhraseControl(component, value)
{
	local Interface = Synth.getMidiProcessor("Interface");
	Interface.setAttribute(Interface.currentPhraseKnob,value);
};

I'll try building a minimal project that replicates the issue but maybe somebody ran into this before? It always works fine in HISE, it is only unlinked in exports on all three OSs.

@d-healey I posted that comment because (in my memory anyway) I typed for and nothing happened, which led me to believe it doesn't appear for "for". The delay in autocomplete makes me much less likely to use it, while I use the instant popup in Sublime all the time.

How you fold code is of course user preference. I would quite like to be able to fold each control declaration along with its settings, callback assignment, and callback function, so when I'm looking for a control I can get an overview of all of them, and jump straight to the one I need without ctrl + f or the re-contextualization of bookmarks.

@d-healey I actually did not realize HISE had it for loops, would be nice if it appeared without pressing escape and with the same fluidity as in Sublime. The autocomplete in Sublime feels goood, it's instantaneous as you type. I'm not sure if the delay in HISE is intentional, maybe that's something we can tweak.

In Sublime you can code fold any line based on indentation. I use this quite a lot for folding away control declarations under a comment.

I didn't want to turn this thread into a wishlist for the HISE code editor, especially as I wanted to contribute fixes for some of these once I finish this library, but since we went there anyway...

For me the main issue is the low contrast, both just the color palette and lack of differentiation between functions, parameters, variables, control statements, and operators. I realize now looking at screenshots that the whole interface is blue tinted as well.

Sublime Text set to Javascript is quite usable, I haven't really compared with this. The bracket and parenthesis highlighting is far more visible in Sublime, and highlights from either side of the character. In HISE you have to put the cursor after the character, and the highlight is barely visible.

When typing (, HISE sometimes inserts () when it's not helpful to do so. Haven't quite figured out the logic, but I run into it a lot.

Sublime includes autocomplete for structures like, if, if else, for, which I use far more often than the API autocomplete and are huge time savers.

Usually if I'm looking in the API for a function I also need to browse the docs anyway. Sublime also autocompletes functions you have used already, the only thing missing is that tab to next parameter, the highlight state for which I find difficult to distinguish from the usual text selection highlight. This makes me not use it much.

In one of these screenshots, typing appends to the end. In the other, it clears and overwrites.

I use ctrl + left and right arrow a lot to jump through functions. In Sublime one press usually takes you to the next token, in HISE it takes you to the next token or separator, which takes longer and usually isn't what I want.

For keybindings, in Sublime I also have bindings for things like go to next sub-token in a string.

For search, in HISE it defaults to case sensitive every time it's run, and pressing ctrl+f sometimes does not highlight the search field if a search is already open (can't quite track this down atm)

I use code folding quite a lot, which makes it much easier to jump between files without losing my place.

In short, I really just prefer using an external editor, especially as I assume a "reload from file" button would be less work to implement than maintaining a code editor and all the edge cases and user preferences that can go along with that.

I would really just prefer a way to use an external editor. After several weeks of intense scripting work using only the HISE editor, the low contrast color scheme, lack of syntax highlighting, lack of keyboard shortcuts, slower response time, and many other quirks make me far prefer the (sadly proprietary) Sublime text.

I don't doubt that it will eventually be on par, but for the sake of getting work done I really need to be in Sublime at the moment. If the fastest way to reload the script is to load the xml I'll just keep doing that.