[feature request] Working with lots of groups
-
Here's an example of where a good group list would be very helpful
There are some missing samples in at least one of my 35 groups. So I'm going to have to keep opening that right click menu and going through the groups one at a time until I find them - unless you know a faster way?
Also, here I'm just looking at group 16, but...
-
@d-healey Yes
-
I have 48 groups now :crying_face: :loudly_crying_face:
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
Working on a project now where I have about 15 sample sets - each is a separate articulation for the same instrument - sustain, staccato, tremolo, etc.
All will use the same modulation chain, envelopes, effects, etc. and I manage RRs from my own script.
I'm seeing no benefit to using more than one sampler at this stage and would like to just separate the different articulations by group. However this is going to require a lot of groups and the group management in HISE is really bad when you have lots of groups. So now I'm thinking to use more samplers just so I don't have to deal with the group system...
I'd still really like to see a group table, with the ability to name groups - I know Christoph that you suggested this is misusing groups, but I think it's just using them. The alternative is misusing samplers and having to manage multiple identical modulation chains which goes against the DRY principle. Or maybe there is some advantage to using multiple samplers that I'm unaware of that makes it worthwhile?
-
@d-healey Are you absolutely relying on velocity in the maps? I personally found that I can cram a lot of artics into a single map just by giving up velocity, a 128x128 map can handle 15 articulations where each one has 8 RRs. You then ignore the incoming velocity and use the artificial velocity to pick different round robins.
-
@aaronventure Yeah I do that kind of stuff too for some instruments.
For this particular instrument, a dulcimer, all the articulations have dynamics controlled by velocity so the simplest solution is map each dynamic to its own velocity range and stick a velocity gain modulator on the sampler.
-
@d-healey if the groups are the issue, then it's not simpler. Lay it all out into a single or few groups with 1 sample per velocity, write out the constatnts about the velocity numbers where you mapped which articulation, and then ignore the note after storing it's velocity. Use your algorithm to play the correct art/rr sample and use the stored physical velocity to send event data for that id which you can use in modulars exactly as if it were a velocity modulator, or take it into scriotnode and do whatever you want.
Your modulator workflow remains the same, but your group troubles go away.
-
@aaronventure Using groups is much simpler than the velocity option. The groups aren't the issue, it's the group management ui in HISE that makes it cumbersome to work with.
I should also add that the samples have been named in such a way that it makes it very convenient to drop them in to the sampler and use the auto-mapper, to map them to velocity instead would require a lot of manual shuffling around. I also avoid a lot of extra scripting using the groups the way I am.
-
@d-healey true, your sample naming scheme would have to change for the automapper to map them properly to the velocities instead.
The sampler UI is problematic yes. I haven't been long enough to know for sure (and I don't feel like building old commits just to check), but it feels like the oldest part of HISE (it's in the name, after all), it really does need some love. It's the only part of the whole dev experience that is below Kontakt's /UI.
I know what I suggested are just band aids and not solutions of the root problem.
-
@aaronventure said in [feature request] Working with lots of groups:
It's the only part of the whole dev experience that is below Kontakt's /UI.
Yeah I'd agree on this, although Kontakt's group management is pretty bad too, but it does have the group table in the monitor window which is basically what I'd like to see in HISE.
