Hello developers, I have a few ideas to make the module tree a bit more user friendly.

1. Color coding the routing matrix: in case of a high number of channels, having the pairs or channels color coded would make it easier for the eye to distinguish the channels in case one has more than 8 channels.
2. By default all "children" are shown (FX, Midi Processors etc). i think it would be easier to navigate if they're hidden by default, or at least that saving the project also saves the session as you leave it, 10 samplers with processors and effects already make the module tree very long to scroll especially if you're on edit mode..... also it would make sense for a container to hide its child samplers when clicking on the arrow, in my opinion.
3. Every time i click on an arrow to hide the fx, the module tree resets to the top, and that becomes tedious to do it for each sampler/container. adding a shortcut like opt + click to hide everything would make sense.

That's all, thanx for reading! :)

@Chazrox you were right, the sprite sheet was spread the other way around
curious tho that it "compressed" the image that way tho.

at least now i understand that script better and i could give the peak meters to all the hise outputs with a loop and it's working! I'm slowly learning how scripting works. thank you both! :D

@d-healey

On the snippet it works. My bad, on my project i left the knobs linked to the gainFX with the processor ID, that's why it was not working properly

SOLUTION: Use Xcode 14.3.1 on Ventura

Hello developers, I have a few ideas to make the module tree a bit more user friendly.

1. Color coding the routing matrix: in case of a high number of channels, having the pairs or channels color coded would make it easier for the eye to distinguish the channels in case one has more than 8 channels.
2. By default all "children" are shown (FX, Midi Processors etc). i think it would be easier to navigate if they're hidden by default, or at least that saving the project also saves the session as you leave it, 10 samplers with processors and effects already make the module tree very long to scroll especially if you're on edit mode..... also it would make sense for a container to hide its child samplers when clicking on the arrow, in my opinion.
3. Every time i click on an arrow to hide the fx, the module tree resets to the top, and that becomes tedious to do it for each sampler/container. adding a shortcut like opt + click to hide everything would make sense.

That's all, thanx for reading! :)

@d-healey
I figured it out and now it works! the only issue is that if i transpose the choke groups don't work anymore. how can i fix that?

@d-healey
does this make sense? or how would it work?

evtList1 = [];
{
	Message.getEventId(41,42,43,44,45)
}

@d-healey but how can i make multiple event lists that contain only certain note numbers, so that "evtList.clear()" does not mute all the notes? at least that's what i think it's happening now

@d-healey
no, i tried it but it didn't work. as far as i understood that works within a sampler or container, doesn't it?

Hello everyone,
i searched on the forum for ways to have choke groups for the hihat, and i found a snippet that is only partly working for me. The hihat chokes each of its articulations correctly, but ALL the other drums get choked too (actually don't play at all). I have some samplers that are mixed, they contain samples from multiple drum parts, so i need to put the script processor under the master chain (and i need it to stay that way for routing reasons)

this is the "half-working" script on "oninit" interface

const var HihatFT = 44;
const var HihatSO = 45;
const var HihatO = 46;
const var HihatSC = 41;
const var HihatC = 42;

const var HihatProcessor = Synth.getMidiProcessor("Hihat Processor");

oninit (script processor)

const var HihatFT = 44;
const var HihatSO = 45;
const var HihatO = 46;
const var HihatSC = 41;
const var HihatC = 42;

const var HihatArt = [HihatFT, HihatC, HihatSC, 
HihatSO, HihatO];

const var evtList = [];

evtList.reserve(64);

onNoteon (script Processor

function onNoteOn()
{
    for (i = 0; i < 5; i++)
        
    if(Message.getNoteNumber() == HihatArt[i])
    {
        // Always use the for ... in loop if you don't need the index
        for(eventId in evtList)
        {
            // Send the note off command for the given event id            
            Synth.addVolumeFade(eventId, 30, -100);            
        }
        
        // Clear all notes
        evtList.clear();
        
        // This is necessary because you will kill the note artificially and HISE
        // can only kill artifical notes for stability reasons
        Message.makeArtificial();            
            
        // Add this ID to the list (it'll add the artificial event ID)
        evtList.push(Message.getEventId());
    }
    
        
    if(Message.getNoteNumber() != HihatFT & Message.getNoteNumber() != HihatC & Message.getNoteNumber() != HihatSC 
    & Message.getNoteNumber() != HihatSO & Message.getNoteNumber() != HihatO)
    {
      Message.ignoreEvent(true);
    }
 
}

I tried to make an array and name it evtListHH to tell hise to kill only the notes coming from the Hihat note numbers, but that did not work (or maybe the idea was right but i did it wrong).

how can i make it work?

Thanx in advance!

@d-healey I'm still much faster with photoshop than with codes
but i've found your HISE Paint Routines + vector graphics playlist, I'll give it a look :)

@Chazrox you were right, the sprite sheet was spread the other way around
curious tho that it "compressed" the image that way tho.

at least now i understand that script better and i could give the peak meters to all the hise outputs with a loop and it's working! I'm slowly learning how scripting works. thank you both! :D

@d-healey in the floating tile properties the size is set correctly, but i still don't get the right behavior from the peak meter :/

@d-healey
i'm a bit confused, if in the component properties i increase the width of the tile, also the height of the image is increasing, if i set it right, the image gets cut.

in the script i don't find a place where i can set the size of the image

g.drawImage("PeakMeter", [i * 20, 0, 20, a[2]], 0, 0 * z_value);

in this piece of script, the first two are x and y, the third seems to be the width of the channel R, because if i set it bigger than 20, the right bar will be bigger. "[2]" i still dont get what it is, if i set it to 3 i see the whole height of the bar. the first 0 seems to change nothing when i put another value, the last 0 changes the range of the movement: with a low number, hise will scroll the images of the sprite sheet, if the value is high like 518 (its the height of the meter) it will move like in the gif above. And in the original script from the snippet i don't see any image size value