@David-Healey ha how do you think I feel, I'd already used it and got rid of it earlier in the project

@Christoph-Hart yes thankyou I figured that out after I posted and it is working as required.
Much appreciated

@David-Healey no it isn't you're right.

I'm just looking for a way to 'unload' an expansion when I go back to banks page really for a couple of reasons.

Is there a way to do that or something similar?

I can see the unloadExpansion() function in the API but I'm not sure how to call it?

I am trying to unload the currently loaded expansion at certain points but not sure what should go in front of it?
Is it exphandler, current expansion etc that goes before unloadExpansion();

Thanks in advance

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

@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