Different sample maps shared monoliths

[d.healey]

If I have two sample maps that use the same samples but have different settings, or perhaps one sample map uses a subset of the samples, will I need to create two monoliths of the same samples, one for each sample map? or is there a way to tell the sample map which monolith to use?

[Christoph Hart]

Actually this is not possible with the current system (the monoliths are kind of hardwired to the sample map with the same ID), but this is a legitimate request so I'll think about it.

What's your use case? Maybe there's another workaround.

[d.healey]

I have one sampler with staccato samples and another sampler with the same staccato samples but also with sputato samples. What I'll probably do is put the sputato samples in a separate sampler.

[d.healey]

What about if the name of the monolith(s) was stored within the sample map XML? then it would be easy to have several sample maps point to a single set of monoliths. I don't know how feasible it would be but it would also be cool if a single sample map could point to multiple monoliths, then if you copy samples from several samples into another sampler (I can think of reasons for this) everything would still link up.

[d.healey]

Digging up this dinosaur.

I'm successfully using the monolith reference system for sustain/release samples. In this case both sample maps are identical, the only difference is the start positions.

Now I have another situation that seems to fail with the monolith reference and I'm wondering if there is an easy tweak that could be added to make this work.

I have a sample map that contains staccato and staccatissimo articulations. The dynamics are mapped to velocity and the round robins are mapped to groups.

I want to use the same staccato samples in another sample map, but only the first round robin and I want to map the dynamic to the group.

Could this be achieved with the monolith reference system?

[d.healey]

Ah actually it doesn't work for my releases either because I removed a few of the samples that I didn't like the release for and stretched adjacent samples to fill the gaps, this seems to mess up the monolith reference.

[d.healey]

Bump bump, would be really nice if I didn't have to make all my release triggers as separate files :) :) :)

[d.healey]

Using sample monoliths I'm occasionally having crashes.

I've tracked it down to an assert jassert(isPositiveAndBelow(startSample, size));

In void* HiseSampleBuffer::getWritePointer(int channel, int startSample)

In this case I have a sustain sample map and a releases sample map. Both contain the same samples, the releases sample map references the sustain monolith.