Hi，大家好~I am from China，Is a composer，I am very happy to create with you all

@d-healey I am using Content.createLocalLookAndFeel();
Tried your method and it worked, thank you very much

This prevents me from using this feature properly

@d-healey OK, thank you for your guidance. I think I can achieve the effect I want in the near future.

@d-healey Ahaha,god，It's so simple
Feeling mine so stupid。，Thanks very much David, you solved my problem again.

@Oli-Ullmann Yes, thank you very much for your help.

@mmprod They are universal, you just use LAF

@Oli-Ullmann cool，I don't know what I did wrong, my

g.setColour();

didn't work, but I deleted all the code and rewrote it according to the code snippet you gave, and it worked. I want to give you a hug to express my endless gratitude.

@mmprod marvelous，I success，thanks for you

@DabDab thaks very much!

@d-healey @Chazrox
I'm back. After many days, I reviewed the code again today and finally succeeded!
We need a loop！
I would also like to thank all my friends who provided me with help and various solutions! I love you all

function onNoteOn()
{
	local n = Message.getNoteNumber();
	local v = Message.getVelocity();
	if (n >= knbLoKey.getValue() && n <= knbHiKey.getValue())
		lastKs = n;		

	if (Synth.isArtificialEventActive(eventIds.getValue(lastNote)))
		Synth.addVolumeFade(eventIds.getValue(lastNote), knbFadeTime.getValue(), -100);


for (i = 48; i < 127; i++) {
	local e = eventIds.getValue(i);
		       
	if (e != -1)
	    Synth.noteOffByEventId(e);
	    
		if (n == knbKs.getValue() && Synth.isKeyDown(i))
		{
			ADSR.setAttribute(ADSR.Attack, fadeIn.getValue());

			lastKs = n;
			
			eventIds.setValue(i, Synth.playNote(i, v));	
				
			return Message.ignoreEvent(true);
		}else{
			ADSR.setAttribute(ADSR.Attack, knbResetAt.getValue());
		}
	}	
		lastNote = n;
		
		if (lastKs != knbKs.getValue())
			return Message.ignoreEvent(true);
	
		eventIds.setValue(n, Message.makeArtificial());
	
}

@d-healey

I found that KS will overwrite the value of lastNote. When the third KS is triggered, eventIds.setValue(lastNote, Synth.playNote(lastNote, Message.getVelocity())); does not play the original note value. Is it possible to write the lastNote value back to the first value in the onNoteOff function?

@Chazrox I used Synth.noteOffByEventId() instead and it works fine now

@d-healey said in Make the Gain knob smooth the gain?:

@CatABC said in Make the Gain knob smooth the gain?:

the note triggered by the third KS cannot be stopped.

Yeah this is the kind of hanging note issue I said you might run into. I'm just testing with my keyboard in realtime, haven't tried with MIDI in a daw but I expect it is less forgiving.

You'll need to dig into the code to see how to mitigate the hanging notes.

It's a bit cumbersome to work on because each time you make a change to one of the scripts you need to copy it over to the others. If you move it to an external file it might automatically update the others when it's compiled, I'm not sure though.

I added this line of code to each onNoteOff,

	Synth.addVolumeFade(eventIds.getValue(lastNote), 500, -100);

and it will have this error,

! onNoteOff() - Line 11, column 21: Event ID must be positive

but the note can be stopped. In addition, there is currently a problem that the third note does not play the note pressed above, but the note of KS itself.

@ulrik said in How to use KeySwitch to trigger sampling?:

@CatABC I guess that's how the eventData Envelopes work, if you trigger a key switch the fade will not be applied until you play next key
It seems to work flawlessly when playing legato but as soon as you release a playing key, and the fade has not worked its way through, it will continue the fade as soon as you start playing a key again.
It would be nice if the smoothing time will elapse even if no playing key is pressed

@d-healey I set the Smooth value of the EventData Envelope of the current Articulation to 1 when triggering other KS to avoid the Xfade at the beginning, but when switching the third KS on the same note, I can't set the second EventData Envelope back to its original value, or do you have any idea to solve this problem?

@d-healey

Aha, here is a free software loopMIDI, which can transfer DAW MIDI information to HISE in real time.

loopMIDI | Tobias Erichsen

(www.tobias-erichsen.de)

@d-healey I tried your Snippet, and I don't know if you have the same problem. When the third KS is triggered, the note triggered by the third KS cannot be stopped. In addition, when switching from the first KS to the second KS, and then switching from the second KS back to the original KS, there will be no sound, but there is always a level display on the waveform generator. I searched for a long time, but I couldn't solve the problem. This problem is too frustrating.

@d-healey said in Make the Gain knob smooth the gain?:

@CatABC said in Make the Gain knob smooth the gain?:

but if KS is triggered at the same time as the note, the problem I described will occur

Aha ok, I think you will run into an issue here because two notes triggered at the same time, how does it know which one to process first?

// articulationSwitcher/onInit    add these
 const eventIds = Engine.createMidiList();
 eventIds.fill(-99);
 reg lastNote;

// articulationSwitcher/onNoteOn    add these
		if (eventIds.getValue(lastNote) != -99)
		{
			Synth.addVolumeFade(eventIds.getValue(lastNote), 500, -100);
		}
			
		if (Synth.isKeyDown(lastNote))
			eventIds.setValue(lastNote, Synth.playNote(lastNote, Message.getVelocity()));	
		
	}
	lastNote = n;
	eventIds.setValue(n, Message.makeArtificial());

function onNoteOff()
{
	local n = Message.getNoteNumber();
	
	if (eventIds.getValue(n) != -99)
	{
		Synth.noteOffByEventId(eventIds.getValue(n));
		eventIds.setValue(n, -99);
	}
}
 

I combined the previous code, and the first two KS can work normally, but when the third KS is triggered, it can't transition normally. I'm stuck here.

@d-healey said in Make the Gain knob smooth the gain?:

@CatABC is that my keyswitcher on its own or your implementation of it?

function onNoteOn()
{
	local n = Message.getNoteNumber();
	
	if (n >= knbLoKey.getValue() && n <= knbHiKey.getValue())
	{
		Message.ignoreEvent(true);	 
		
		knbArticulation.setValue( n - knbLoKey.getValue());
		knbArticulation.changed();
		changeArticulation(n - knbLoKey.getValue());
	}
}

changeArticulation(n - knbLoKey.getValue());

I just explored it and found that this line of code cannot be deleted. Keeping it will not cause articulation confusion.

@d-healey is your code. I followed the video step by step to reproduce your operation.When KS is before the note, it works fine, but if KS is triggered at the same time as the note, the problem I described will occur