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

@d-healey I'll have a look at that thankyou. I may have set it/not set it correctly from one OS to another maybe

@d-healey so there's nothing that you know of that would cause it to happen on Mac when it works fine on windows?

It's the exact same code for both versions and has happened on every project ever regardless of whether it used expansions or just regular presets.

It looks like it loads the preset and samplemaps but no sound plays on Mac but it does on the windows version.

There's no extra setting or process that needs to be turned on/off on Mac or anything?

It seems odd that it's every project but I know little about macs TBF, they're a mystery to me. I only have it to build the Mac version, everything is built on windows

@d-healey I figured out what it was - there was a line of code clashing with another and it was unloading the expansion when it went back to the grid.
Tested it and it worked...happy days or so I thought.

My colleague has just confirmed that it isn't working on Mac though even though I took the offending line of code out.
In fact none of the mac builds ever have a preloaded sound whether they are expansions or straight presets. I have never been able to figure it out so the above is hardly a surprise really.

Have you got any idea why the mac version would act differently to the windows version in daw
when it is the same code?

@d-healey I just did a test build with the expansion and samplemap comboboxes visible so I could see if they loaded empty.
Both comboboxes are populated in DAW so now I'm even more confused as what you said made sense but looks like it isn't the case.

@rzrsharpeprod That would make sense. I'll have a look through my code as have another project where it does recall whatever preset was active when you compiled. I'll compare the 2 and see if I can find it

@d-healey That makes sense, but the preset not being loaded doesn't as nothing plays for sure and I'm not sure why?

@d-healey That's what I thought but it just loads the expansion correctly and changes the label correctly to the preset name but it is not selected in the preset browser and therefore presumably it is not actually selecting the preset, just remembering some of the settings from when it was compiled

@rzrsharpeprod That's what I was worried about.

I can do the old trick of saving and compiling with the one I want to be default loaded. This compiles fine but when you load it in DAW it looks as if it is loaded (shows as current preset on label etc) but in reality nothing is actually set so nothing plays.

I was hoping there was a way around this but it seems maybe not?

Default preset when using expansions.

Can anyone tell me the correct syntax for entering a default preset in the preferences/settings menu when you are using expansions.

What do I need to enter into the box, is it any of the below:

Preset name.preset
Expansions name/Preset name.preset
Expansions/Expansions name/Preset name.preset
or any of the above without the .preset?

Thanks in advance

@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.