Factory Preset Creator

d.healey

Well I agree with you fully that user presets should be for the user to save their front end values, I feel though that we need a system for developers to create different setups of their instruments that go beyond what the user preset system is intended for.

Other than hacking the preset system I can't see a way to allow the user to switch instruments from a single VSTi. With instruments than only require sample maps to be swapped it's not such a big deal but when working on a varied collection of instruments, where modulators, effects, scripts, etc. also change from instrument to instrument, incorporating all the various parameter settings into the front end script isn't practical. With Kontakt I'd just create a separate NKI for each instrument but using the preset browser seems so much better than providing lots of individual VSTis.

So I think this little preset hack is the simplest way and can be easily dropped in to any project to allow a developer to create a detailed variation of their instrument that is easy for the user to load.

The labels are for entering the Bank, Category, and Name of the preset. So if I want to save a piccolo preset I might enter "Woodwind", "Flutes", "Piccolo". The only problem I found was that the Bank and Category had to have already been created as the save preset function doesn't create the folder structure.

The new floating tile system seems very interesting. Does its introduction mean you'll be removing the standard header with the preset browser? And the default on-screen keyboard?

Christoph Hart

I admit this might be useful in certain scenarios. But be prepared for some hiccups as there are a lot of things happening when creating modules and its impossible to predict all combinations.

I think adding / removing or changing states of modulators and effects should come without problems, but as soon as you change a sound generator, it will trigger a global recompile of all scripts and this might cause some very nasty issues with multithreading.

Can't you use the preset browser instead of the labels? The preset browser just assumes a two level folder hierarchy for Banks and Categories and would be perfectly capable to do these things without having to write script code for this. I am offering these functions for user preset handling on the script side:

load next / previous user preset
save user preset (with a given name)
open the preset browser
get the name of the currently loaded preset.

The floating tile system will indeed replace both the virtual keyboard as well as the top bar (in fact it already has, because I removed these components from the compiled interface a few days ago).

However everything that can be found there can be put into a floating tile, so if you've fallen in love with the top bar - which would be a little bit awkward :), you can still recreate it, but customise it better.

The reason for this decision was that almost everybody wants to fully customise the whole appearance of the plugin's interface. I'd rather provide a collection of ready made C++ components that can be shuffled together using the JSON data from the HISE layout.

d.healey

Oh I just got what you mean about using the preset browser instead, that makes so much more sense :)

When you mention changing sound generators does that mean restoring their state or adding/removing them from the instrument? I'm thinking I might just be able to live with swapping out the sample maps and not worry about saving their state - although might be an issue if two presets need a different number of RR groups.

Christoph Hart

RR Groups should actually be saved within the SampleMap - if that is not the case, it's a bug and will be fixed :)

d.healey

Aha that should make things easier

d.healey

It's just occurred to me why I'm not using the built in preset browser, that will only work with the front end script so won't work with this script. I've just been trying to implement this script in a project and already I've run into a problem with it not restoring MIDI processors. One element that will likely vary between different sample sets for many instruments is the playable key range and the key-switch range and I'm currently adding that functionality with a separate script that keeps everything nice and modular but to do it with the built in preset system I'd lose the modularity. I'm again thinking it will just be easier to use a separate VSTi for each instrument although as we both know that won't be as convenient for the user.

Christoph Hart

Why not wrap it in a namespace and offer this in an external file that can be used from the frontend interface directly?

And changing the key colours dynamically when swapping sample maps should be no problem (just store the data in an array that correlates to the sample map list).

And if you want to change attributes of a MIDI processor, you could also directly set its attributes instead of restoring the whole thing.

d.healey

The namespace idea is good. The problem with storing the attributes of the MIDI processors is there are a lot of MIDI processors in some of my instruments, if there was a way to iterate through all of the attributes of each MIDI processor then that would be practical as it could then easily be automated in a loop but currently I'd have to do it manually for each processor and it would vary between projects.

Christoph Hart

Well, you can just create arrays with values that have the same length as the MIDI processor has attributes and go crazy with for loops:

HiseSnippet 1137.3oc0X0kaaaDDdojXSDSUPSQO.D5IYDWYRQEmebMrMciMbS8OnJvn.FFoTjKsVDpcEVtzotA9fj25Qnu1iPetWjdCZmkjxjThRPxHFnl.ZA2YluY+1YmYAGcBm4hCCYbjxid6UivHkuTs2UTwfcG3PnnC9djxiUOzITf45IhruZjSXH1ConTceo.k50PwO+yV1NANTWblHD5TFwE+ijgDQlzeY62PBB1ywC+VxvbV2c6CbYzcYArHfOUUMPibbeuyE3ibjlUQEcIA+gPjhgpUm172a1+21o8DO6GM.F8A4WdgUWlmEFlhbi3bLUbJ.Gonp7uvih5q8HBFumvQfAeV0l4cUuArOPSV5SIgj9AX4DSTOfSIhQ6NfD3cx3vVHBoT6jrfX0jf32ndHwibi7rf4WEqPOCQ9voRkhTpVAJYNKJsGKvS5fYPup4nWsD58D0dtbxHQlFI295ToyfcIJQU9iZpvoTnP+RGttOgGJ1QeS8yLZarptQaS4Pmy2ng1DFYmXzKk5egb34RixaVHFd2aZmIGrJ5wDSm1kxg0mzu6IWdvz3751WfEENaZ0LVeyUJr.8hWf4.JwfXT4fYGIDLpbKrKiJfLt1NddIBa0LUYyU06.6NSiU1Pas0zO6G5c7QiAdt1XbgX4oyHLWPvg6wYCklk2GergltdyPmKwGPOgiA6a9JcemfP7pwZ3NdD19bVzHPdSylMztNcAWqvJVB+smG+sg01b8YrArWvMf8msMfMrA7intBBipynGwD3iosVQ6iZ00tdJM99koRRYNKH.yKSq7NJ9bf0hFMrOluJD.Chvw1Q7SEpu4liCzqzPqNrkqW2GReHPD1XCch92kVA0N.SuPL.D8zmJsLwz5wolxP4NBAmzORfaQVMExYjyg3Q85WCVVheSqllgiSRemxyofx6Z4OLbnLO5au7z2dgnu8sg9YtFXObjAWAV7dUsE6dU2jL4bFxnGPIhiGguYdR91XIFnaxyxKJK+Juz37pRLKSzzWliRqtf2Vza0efZ7oPoWkapnlq3+MTV+hU9RIsZJGg5U4MxPXcB.clEhNw2SzoTPVyBjE.xpS5J8+tx5xxkdzmmbIi65bo4+QBY4UJUSgBuIhSqdbZZUu.hGliHfS9BU4gEJNxj+i8PK.1GDisSAv+9m9zet0hC1ZRv+0VKb4vCUSt6nz5A+655gmYdKpGLJuHp6r.0E.0c86SEQZ2SJhlagSs6mENKL3tE.usk0eWVUGzfCyKJvQTrqGYmhoJfDjBEeGHCfgDwU46jbIZExnzVgLK6vZAo6STOgHbGTNeqTBegS+6Z9l1XYC0W66icEYjsl5d+7ssKxkfJ+DKRPnWbnC74V+JzC8QQC6Aso6hAlPovGHJ6qthLSNYtgbtLxzCS8LF2zcpRS4bkTkliUhF53xYuyMIgT155Cik.bhF+G.TW8P4bcywYhRdOD5K6cttx.w2BLubDcVZDVKMhtKMhmszHVeoQ77kFwKlCBYSv6DIXCSJKPn+C..59Q1

d.healey

Thanks for the code example. I think though that this still requires that I know in advance how many attributes each script processor has and I need to keep track of these manually. If we could do a for loop type thing to iterate over an arbitrary number of attributes then a few lines of code could handle any number of scripts with any number of attributes and the values of the attributes could be saved automatically into the user preset. Maybe I'm looking at this the wrong way though, I'll play around some more with your script example.

Christoph Hart

You need to know the number of attributes anyway when you create the preset data, or am I missing the point?

d.healey

Yes currently I would need to know the number of attributes, but if we had a function that could give us the number of attributes for a script then I could do something like this.

for (s in scripts)
{
	for (i = 0; i < s.numAttributes; i++)
	{
		presetData[i] = s.getAttribute(i);
	}
}

Christoph Hart

Ah yes, that makes sense (I thought you're creating those by hand, but for this approach, you'll need a getNumAttributes() method). I'll add this tomorrow.

d.healey

Thanks Christoph, should be very useful :)

d.healey

Could this getNumAttributes() function also work for other modules such as effects, modulators, and envelopes too?

Christoph Hart

Yes of course...

Christoph Hart

Alright, the changes are pushed to the repository.

d.healey

Excellent, building now!

d.healey

Seems to work perfectly, this is awesome. I'll be putting together a namespace version of this preset script soon which should be much more reliable and easier to use. Thanks again!

Christoph Hart

I noticed one caveat with this method: if you are restoring custom scripts by iterating over all attributes, it will ignore the saveInPreset property (so everything gets restored). This is because the index is just the order of declaration and if I skip non-saveInPreset parameters, there would be a mismatch between those numbers which will cause all types of problems.

However the saveInPreset property just makes sense on the main interface script anyway so it shouldn't be too much of a restriction.

Also note that you can only use float numbers in the method setAttribute(value). And if your module has a table or a sliderpack that needs to be restored, you're also out of luck and need to go back to exportState / restoreState.

BTW, the current implementation of restoreState for scripted modules loads the stored script and recompiles it. I could add another function (eg. restoreContent) which doesn't recompile things, but only restore the values of the preexisting script interface (which is much more lightweight and not causing issues with multithread locking).

Factory Preset Creator

31

1.7k

11.7k

102.0k