Having used all 3 fairly extensively, here are my thoughts on the 3 different pieces of software for what it's worth.

I came from both Romplur & Maize before transitioning to HISE. They are easy to use but you hit issues and/or limitations pretty quickly IMO.
Maize & Romplur are very similar to each other despite the Romplur CEO saying otherwise.

Romplur has a huge issue if you want to use real sample mapping for each individual note and will just grind your DAW to a halt if you have even a modest number of presets/banks.
Maize doesn't have that issue at all depsite being the significantly older software.
With both, you are limited to the built in effects and functionality so if you have far reaching or even moderate ambitions you will hit the ceiling fairly quickly.

They only really have 2 advantages over HISE and one was mentioned by the OP - that you can export both Windows & Mac format plugins on 1 platform, you don't need to have a Mac to export Mac plugins and so on.
The other advantage is ease of install.
Other than that, I would say HISE wins hands down in every other category.

But in fairness to HISE, once you have got your head around the HISE install/build process & how it works, it's not really an issue tbh

After making the move to HISE I would 100% never consider moving back to either of the other 2 and the more I learn with HISE, the more possibilities there are and the more powerful/flexible it becomes.

@d-healey Turns out you were kinda right and I had done something stupid.

When I changed the preset browser from 3 to 2 columns I just left the default widths as 3 x 0.33333
It didn't seem to matter as it worked fine in HISE but in a built plugin it was doing what I described in my OP.

After your suggestion I flicked it back to 3 columns, re-exported and sure enough the factory presets weren't editable & the add buttons were there as they should be.

I then changed it back to 2 columns but set the widths to 2 x 0.5 and when I re-exported it this time it was also working correctly.

Glad I have that sorted as it was really bugging me. Thanks for the assist

@rzrsharpeprod can I just say, this forum is great as people are very forthcoming with suggestions and help. It is much appreciated and quite rare in a forum I find so thanks everyone

@d-healey ah ok strange.

Thankyou for your help as I now have it working properly and selecting the correct samplemaps.

I've also got the expansion load working in daw as well so I can progress with my project which is great news.

Thanks again, your help is always invaluable

@d-healey Ok thankyou. I have created a minimal project and sent it to you via DM

@d-healey Thankyou, as usual your help was invaluable.
Ironically I have been using autocomplete quite a bit recently but it didn't even occur to me in this case.

Thanks again, it is doing what I want it to do now

@Lindon @d-healey

Thankyou both. I tried both methods and have come up with something that works.

I need to do a little rejigging of the samples once to get it working 100%.
That is a one time job and after that I can add new samplemaps without messing up my presets and having to manually reassign the samplemaps which is exactly what I wanted.

Thanks again, your help is much appreciated

@gorangrooves said in FL Studio midi problem:

@gorangrooves Found it. For anyone else looking, it is in:

top menu Options-> Audio Settings-> CPU-> Align Tick Lengths

Apologies I've only just seen this. Glad you found the setting though

@d-healey I forgot to say earlier but this worked like a charm. Thankyou for your help as it would have taken me forever to figure that out (if ever)

@DabDab yes that the code I used to get it working in he first place but it didn't translate across when I made firther changes in daw.

@Christoph-Hart said that it should though so I'll double check something else isn't stopping it

@Lindon yes that what I have done. The panel is above the preset browser in my project.
That panel is essentially a 2 x 4 grid of 'buttons' (one for each tag) inside that panel and when the 'buttons' are clicked currently it prints a list of all presets that have that tag to the console depending on which button was clicked. This is working correctly so the tags are being picked up and read correctly by hise which is good.

What I'm looking to try and do ultimately is have the preset browser filter to show only the bass presets if I click the bass tags button, only the bells presets if I click the bells tag button and so on.

@Lindon so that means it is possible to have the preset browser affected (in this case filtered) to show just the presets I want based on the click actions of a separate panel (containing my tags)?

I've no idea how to begin with that as I don't know what calls can affect the preset browser and can't seem to find anything from poking around here. As I says I wasn't even sure it was possible at all tbh

@rzrsharpeprod
Ok an update. I have created json files and got Hise to read them and populate inside a panel. If I click on the tag text it prints to the console with any presets that have that tag which is good.

So my next hurdle is now can I/is it even possible to filter the preset browser to show just the presets that have that particular tag?

I am really struggling to find out how to get preset - in particular expansion preset tagging to work from an external file.
I have looked around the forum and found some posts on it but nothing that explains the process with enough detail that I can have a go at it myself.

As far as I understand I can use a JSON or XML file in each expansion folder and then put the tags for each preset inside that expansion in the file. I am not sure which or the 2 formats is best to work with, does it matter or are either easy for hisento pul in and use?

Once I have that file, how do I go about getting Hise to read the file so that the tags can be used in the project? I assume it is best to use the file system but don't know how to point it at the expansion folder to pick up the json/XML file.

So in short I am falling at the first hurdle and can't even get the tags into hise to even start thinking about using them correctly in the project.
Any help with the file format and loading it into hise would be much appreciated as without hat I can't do anything else.

@Lindon How do you go about creating the buttons on the left for the tags? And if you click them do they filter the preset browser accordingly? ie clicking the Pad button will show you just the presets with a pad tag etc?

I would like to add tags my expansion presets with the idea that a user can then use 'type' buttons to filter on the types of sound within the selected expansion.

I am not 100% sure how to add tags to the presets in each expansion, is it best to have 1 xml/json file per expansion detailing the tags for each preset for that expansion or should it be done per preset? Is there a required format for these files?
Once you have added the tags, what is the best way to call them into HISE so that it can read & use them?

Once the tags are in there, the buttons would be something like the image below

Clicking one marked 'Bass' for example would filter on any presets with the tag Bass.
The result would be similar to typing the word Bass into the search bar (providing the word Bass was in the preset names) ie only those presets would show up and the rest would be hidden/filtered out.
Is this even possible with the standard preset browser?

As always thanks in advance as it's a bit of a tricky one

@rzrsharpeprod @d-healey I realised that the bottom section of the tiles were transparent so when I filled them and changed to drawing them in the grid under each one it worked

@d-healey I found one of your posts on here saying something similar but I can't get it to underneath with a bottom right offset like a true dropshadow would. It seems to draw from all sides at once and only on top and on the bottom portion of the tiles with the text not on the image. Presumably it is also drawing it on the bottom and right edges as well but you can't see it as it outside the bounds of the child panel

@d-healey Now that this has all come together and is working nicely, the dropshadow question has reared it's ugly head.

How can I add a dropshadow - preferably an offset one - underneath each child panel?

@d-healey Yeah it's a bit odd. I'll build a minimal example later when I'm home and post a snippet.