Round Robin + Group XFade

[Casey Kolb]

@d-healey ah yes, I see. We will have multiple velocity layers (ie a sample for velocity 0-27, 28-56, 57-80, and so on)

[d.healey]

@Casey-Kolb If you're not using velocity crossfades you could compress the range of velocities you are using to map those samples and use scripting to remap the incoming velocity to the correct one. That would free up the rest of the velocity range for repetition samples.

[Casey Kolb]

@d-healey That's an interesting idea. Do you think that's cleaner than switching dynamic groups (1/2, 3/4, 5/6, etc) with scripting?

[Christoph Hart]

@Casey-Kolb there is an inbuilt solution for this now:

HISE | Docs

(docs.hise.audio)

[Casey Kolb]

@Christoph-Hart Killer! Thank you.

[Simon]

Bumping again to say that I have an instrument that runs into this constraint, without a way to work around it: lots of samples that need to be categorized into RR, dyanmic, and variant.

I'll just use lots of samplers, but it would be really cool if we could assign samples to both an rr and a dynamic layer, like if the groups used to set up "group fade" were separate from those to set up RRs.

[d.healey]

@Simon Is there a reason you can't use the velocity range for round robins since you're using groups for dynamics?

[Simon]

Yes, because legato samples are mapped to velocity.

[d.healey]

@Simon Why can't you have both mapped to velocity? You have 127 values to play with.

[Simon]

When the amount of rr x dyn is high, the samples don't fit, without doing something janky like offsetting some sets of samples in both note and velocity, which makes working with the maps more difficult. A two octave instrument, six playing styles, and two dynamics is enough to make it not fit comfortably in 127 notes or vels. Plus, my favorite thing about HISE is leaving behind the janky workarounds I had to use all the time in Kontakt. Not needing to manage duplicates of all groups just to have multiple mics is the best :)

The point is not that having lots of rrs and dynamics is impossible, but that it would be very convenient if RRs and crossfade dynamics could be used separately and simultaneously, with a UI that makes the distinction easy to work with.

[d.healey]

@Simon said in Round Robin + Group XFade:

six playing styles

One sampler per style.
Note range just for the pitches
Groups for the dynamics
Velocity for repetitions (and legato if you don't want to or can't use a separate sampler for them).

@Simon said in Round Robin + Group XFade:

it would be very convenient if RRs and crossfade dynamics could be used separately and simultaneously, with a UI that makes the distinction easy to work with.

I agree, but in the meantime I'm trying to find solutions that avoid using lots samplers

[d.healey]

Actually I just checked and it's now possible in HISE to have lots of groups with xfade, and with the setMultiGroupIndex function you should be able to use RRs and dynamics with groups - I find the group management in HISE much worse than Kontakt's though so I avoid lots of groups where possible.

[Simon]

I tried a build from develop but it still looks like group xfade works on the first 8 rr groups. Maybe I misunderstood?

[d.healey]

@Simon It's an interface issue I think. Click this XFade on button and you'll see a table for every group. However setting them all individually seems like a nightmare so I would add a script to your project with however many tables you need, let's say you have 3 dynamics, so 3 tables. And through the magic of scripting use those to set the xfade tables for all the RRs.

Ignore that, looks like Christoph already foresaw this issue - https://docs.hise.dev/scripting/scripting-api/sampler/index.html#setmultigroupindex