HiSE not responding when loading 5g+ of samples
-
I'm working on a guitar library that has more than 10k samples (5GB on a HDD), with around 100 samplers. Whenever I open the project, HiSE becomes not responding. However it's only using 10% of the CPU and not even using a gig of memory (out of 64GB).
I made a debug version of the project by removing half of modules, and it opens fine.
So what would be the problem here? I'm using the newest 2.0 release version released 3 years ago.
-
@rcjach Why that many samplers? I'm surprised it your project will open with that many samplers. Loading that much ram isn't an issue but that many sampler modules definitely is. Also, definitely build one of the newer versions on GitHub. The develop version from the 27th is stable for me.
-
@crd I'm using a separated sampler for each articulation of each string, for round robins. Is there a better way to handle that?
I'll try installing VS to compile the newest version of HiSE, though I'm constantly running out of hard drive space...
-
@rcjach said in HiSE not responding when loading 5g+ of samples:
Is there a better way to handle that?
Yes!
You need to restructure your project.
There are 4 ways to separate samples:
- Multiple samplers
- Multiple groups
- Velocity
- Note number
Which one to choose depends on the situation. For a guitar I separate each string, rr, and up/down by velocity and each dynamic by rr group. But there are other ways to do this of course.
I'll try installing VS to compile the newest version of HiSE, though I'm constantly running out of hard drive space...
You should only have one copy of the HISE source code on your system.
-
@d-healey you mentioned about it a month ago, I was wondering if you separate rr and up/down by velocity, and dynamic by rr group, then don't you have to manually change the gain, velocity, and the rr group of each midi note?
-
@rcjach said in HiSE not responding when loading 5g+ of samples:
then don't you have to manually change the gain, velocity, and the rr group of each midi note?
The gain is handled by a modulator.
The other things are handled by a script.
-
@d-healey Hmm, is the modulation using velocity -> gain?
-
@rcjach Yes. You'll need to use a global modulator because otherwise the velocity value will be overwritten by the script that you'll use to trigger the correct sample.
-
This is not a bug I think. This is something over doing. Follow @d-healey 's way to run HISE and exported plugins smoothly.
-
I have some sample maps which work well in hise but once in the compiled vst, the Samples are mixed. it's really boring
