BAD BAD BAD HISE!

[d.healey]

I've started going through all the testing tools in the tools menu, so far I've discovered that for some reason none of my sample maps had the correct ID set.

[Lindon]

OK I found that too! - so how do I set it correctly?

OK looking at the sample map as XML shows the sample map set like this:

<samplemap ID=""

-- so that looks wrong

[d.healey]

@Lindon Tools >> Update Sample Map Ids Based On File Names

[Lindon]

thanks yeah just found it.

[Lindon]

OK I think I'm back to where I was this morning (I've completely rebuilt the UI) now all I need to do is work out how to load samples on init.

I cant get loadSampleMap to even be recognised as a command.

[Lindon]

What the!!!! its done it again. Everything LOST..... this release seems to be broken in some way.

[d.healey]

@Lindon What version are you using? Save as an xml as well as .hip. Use GIT to keep working versions. Did you get the sampler as a child synth? If so you need to use SamplerName.asSampler().loadSampleMap()

[ossian1961]

@d-healey
I have same issues though my project isn't based on samples, just a synth with synth modules.

[d.healey]

@ossian1961 Can you post a snippet?

[Lindon]

@d-healey I'm on 2.0 build 650

[Lindon]

@d-healey I must still be doing something wrong - where is the documentation???

heres my init call back (I have a sampled called Voice1):

Content.makeFrontInterface(635, 310);
Voice1.asSampler().loadSampleMap("{PROJECT FOLDER}/SampleMaps/XylophoneVoice1");

[d.healey]

@Lindon Yeah that's not quite right. Not sure if it's specifically documented but it will be hidden away on the forum somewhere. I keep thinking we need a wiki :)

So first you have to get the sampler in a variable - right click on the sampler and select Create script variable declaration and then paste into your script.

Then you will have a variable called something like Voice1 in your case.

To load a sample map you'll use Voice1.asSampler().loadSampleMap("XylophoneVoice1"). When loading sample maps HISE automatically uses the SampleMaps folder.

[Lindon]

@d-healey said in BAD BAD BAD HISE!:

asSampler()

Sigh so this means then that the API documentation on the web is wrong/incomplete and the api documentation in the instrument itself is wrong/incomplete - WTF!

really "asSampler()" appears precisely nowhere.... Ok well moveing on...

So when I deploy my vst how do I structure the folders?

the dll alongside two folders called "Samples" and "SampleMaps"

Will that suffice to make the dll start and automatically load the sample maps - so I dont have all this .hp1 silliness??

[d.healey]

@Lindon
There will be a reference to it somewhere because I think Christoph told me on this forum.

So you only need to use asSampler if you use getChildSynth to store the sampler reference in a variable. If you use getSampler instead then there is no need. However I prefer to use getChildSynth because sometimes you'll want to treat it as a childSynth and sometimes you'll want to treat it as a sampler.

The sample maps will be embedded in the exported VST, all you need to supply is the ch monolith files, assuming you've converted your samples to monoliths. If you want to be fancy and include an installer then you'll want to use the Export >> Export samples for installer tool which will compress the samples into an HR archive. This is a delivery format only which provides a smaller download for your customers. Once the user opens the instrument they will be asked to give the location of the hr1 file which will then be extracted to their chosen location, after which they can delete the HR files. Here's some detailed user documentation for this process - https://librewave.com/knowledge-base/sample-library-installation-guide/#Installing_the_samples

[ossian1961]

@d-healey said in BAD BAD BAD HISE!:

@ossian1961 Can you post a snippet?

D'you mean about the bug?

[d.healey]

@ossian1961 I mean open your project go to Export >> Export as HISE Snippet and post it here. Then I can open the project and see if I can find the problem.

[ossian1961]

@d-healey I'll do if it fails again, I mean, it happened four times on twenty and more times I opened it... it's like that sometimes the automatic preset saving gets trouble, though it's the XML that fails and return same message that it's unable to load the interface.

[d.healey]

@ossian1961 XML is much easier to fix because we can view it in a text editor.

[ossian1961]

@d-healey said in BAD BAD BAD HISE!:

@ossian1961 XML is much easier to fix because we can view it in a text editor.

Anyway I hope it doesn't happen, it's a quite annoying thing ;)

[d.healey]

Urg mine's broken again now...