BAD BAD BAD HISE!

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

[d.healey]

Now HISE is being even more strange

[ossian1961]

Awwww! :O

[d.healey]

I just converted all of my sample maps to monoliths and so far (fingers crossed) everything seems to be working. So maybe HISE is having some problems with wav files...

[Dan Korneff]

I've been having no luck with the sampler in the latest build. Check this thread for more:
https://forum.hise.audio/topic/1121/sampler-issues-latest-build/15

[Dan Korneff]

Could be a CPU issue... I can't make monoliths on my PC, but can on my mac. Either way, I get errors on both when creating monoliths

[d.healey]

@dustbro said in BAD BAD BAD HISE!:

I've been having no luck with the sampler in the latest build. Check this thread for more:
https://forum.hise.audio/topic/1121/sampler-issues-latest-build/15

Yeah I've been following that thread. No idea what the cause is, I'm not using the latest build though.

[Lindon]

Oh no EVERYTHING is gone now... none of the hip files have anything in them the xml doesnt work - @Christoph its now useless -

every single autosave is now empty

All I get from HISE is:

ModernistXylophone:! Component with name wasn't found

[d.healey]

This post is deleted!

[Lindon]

Oh I go one to open....its an old back up but..

[Christoph Hart]

Wow, this is like going to the supermarket, coming back and your house is on fire :)

So first things first: @Lindon, if you have any file somewhere that contains more than just zero byte, send it to me and I'll try to recover it. I assume you have made backup copies, otherwise, please use Git in the future and take this as a (admittingly annoying) lesson.

@d-healey Can you explain the exact process needed to reproduce this issue (I get that it has something to do with changing types of components), but I lost track of where you put it.

To the other people: please make a separate thread for every bug. A general "HISE IS BAD" thread is not the smartest way to get heard :)

[d.healey]

@Christoph-Hart said in BAD BAD BAD HISE!:

@d-healey Can you explain the exact process needed to reproduce this issue (I get that it has something to do with changing types of components), but I lost track of where you put it.

Actually all my problems stopped once I converted the wavs to a monolith :)

[Christoph Hart]

Yes, this is in fact a problem, because I also convert the sample to monoliths as soon as they are edited, so I don't enjoy the bugginess of HISE's playback of non-monolithed files (I consider using .wav files in HISE as a small intermediate step, but maybe I am wrong with this assumption).