Populate samplers after plugin launches
-
@d-healey good call. Removing the sample folder cuts load time down to 20ish seconds.
-
@dustbro Are the samples in .ch format?
-
@d-healey yes
-
How many gigs of samples?
-
@d-healey about 3GB
-
Not a huge sample amount. Have you tried a different host?
-
@dustbro any particular reason for that many samplers? Can't consolidate down to less samplers with more RR groups or layers instead?
-
@LightandSound said in Populate samplers after plugin launches:
any particular reason for that many samplers?
The samplers contain multi mic samples, and every time I put more than one instrument with multi mics into a sampler, the instrument act weird or there are conflicts.
I'm in too much of a rush to trouble shoot now... but I will try to consolidate in the future -
You have multiple instruments loaded at once?
-
@d-healey It's a drum instrument, so I consider each drum a different instrument.... but also, different articulations of each instrument get funny if I put them in the same sampler.
I have 5 articulations of a Hi-Hat (3 mic positions for each). When they are put into the same sampler and assigned to different midi notes, things get strange.
Maybe it's a file naming structure? I'll investigate further when I have more time. -
Yeah things can get tricky with that kind of thing. Are you using HISE's built in multi-mic handling?
-
@d-healey said in Populate samplers after plugin launches:
Are you using HISE's built in multi-mic handling?
Yup. Merge multi mic