Reload Sample Maps

[Lindon]

So I'm looking for a way (that is not restarting HISE) to reload sample maps that I have changed externally to HISE...I see we have Export>Unload Sample Maps, is that it? If not, is there something? If not, can we have it?

[clevername27]

@Lindon I realise this is less than helpful, but isn't there a specific command to reload sample maps?

[Lindon]

@clevername27 said in Reload Sample Maps:

@Lindon I realise this is less than helpful, but isn't there a specific command to reload sample maps?

nope, samples yes, maps no....unless I'm mistaken (not unusual)

[clevername27]

@Lindon Oh, OK. I do this in my plugin (not sure if it's in what I sent). I wrote s short function scan for samplers, get the name if its current sample map, and reload. In the broadcaster receiver, the number of activations is recorded, and compared to the total number of samplers. When the numbers match, the function is done.

[Lindon]

@clevername27 sorry maybe Im not being clear.

When HISE (not my plugin) loads it reads the Sample Maps folder for the sample maps....and it does this just once on start up, so now if I make a change (outside HISE) to a sample map - and I do this a fair bit to be honest as I have a bunch of batch based processes... then the only way for me to test the change is to close HISE and reopen it. What I'd like (just to save me doing this 200 times a day) is a menu option that says "Reload Sample Maps from Disk"

[Christoph Hart]

@Lindon the reason why they are cached is to make sure that the data is consistent at all places so if I write this function I would have to ensure that the cache is properly invalidated everywhere just for that minor workflow improvement.

[Lindon]

@Christoph-Hart well I'd argue that its not a minor workflow improvement for me, but I get what you are saying...

[Christoph Hart]

@Lindon I'd rather argue that if you have to edit the samplemaps on a regular basis outside of it might rather make sense to encorporate that functionality into HISE (as long as it's not a super specific use case).

Eg. I always have to resort to editing the samplemaps when I need to switch the samplemap back to not using monoliths and there is absolutely no reason why I shouldn't add that function into a context menu now that we're talking about this.

[Lindon]

@Christoph-Hart well my case is I guess a bit special.

I'm often working with customers who have an extensive set of Kontakt instruments, so I need to convert their nki's to sample maps...and I have written a Creator Tools Lua script that does this for me...

So the customer sends me 250 NKI's and I load them all up one by one in Kontakt and run this script against them.. now I have 250 Sample Maps, no problem - put them all in the Sample Maps folder and the samples in the Samples folder and start HISE....

I then make the ch1 files and send the results to the customer....

..who inevitably wants to make changes to the layouts, volumes, pitch , loops etc. So they send me 55 revision NKIs.....

Back to the Creator Tools script and generate new sample maps, copy these to Sample Maps and restart HISE..

So this is great if they get all 55 revisions to me at one time , but as Im sure you can guess I get sent these a dribs and drabs..... 0ne or two at a time..so this would be a real time saver for me.

[clevername27]

@Lindon (I see Chris addressed your question, so I'll bail out.)