@d-healey Brilliant - thank you, as always.

@aaronventure Thank you. Could you possibly show a code outline of how I'd do that — writing an event list to encoded file, and then decoding it? I'm little unclear. Cheers.

@clevername27 Of course, but I would like to be able to do this with a single sampler, because I'd need 6+ channel pairs and maintaining the rather complex modulator and FX setup for each sampler isn't ideal, and the whole thing cannot then scale.

I wrote about the usage of proessBlock for crazy simple routing here https://forum.hise.audio/topic/9325/channel-routing-with-a-few-lines-of-code?_=1715791474986

@d-healey said in A Few HISE Language Questions:

@clevername27

2: We have typeof

4: No

Thank you, Dave. I didn't realise we had typeof in HISE, cheers. That solves the function issue.

I guess I'm looking for something more like IsA, so I can determine what type(s) of HISE object(s) a variable is referencing.

@Mighty23 thanks this worked

@Christoph-Hart

no, not setting an error message anywhere. as far as I can see, there's only the one for the expansion handler.

@d-healey Thanks! I built HISE enabling FAUST and imported some .dsp files into scriptfx. Very useful!!

@goldee There are some examples on the forum. But start with the basics of scripting so you understand what you're doing and have control over it.

@Christoph-Hart Is there some hidden way to attach mouse scroll to the broadcaster?
I'm only seeing these events:

"clicked": false, "doubleClick": false, "rightClick": false, "mouseUp": false, "mouseDownX": 80, "mouseDownY": 16, "x": 80, "y": 16, "shiftDown": false, "cmdDown": false, "altDown": false, "ctrlDown": false, "hover": false, "insideDrag": 0, "drag": false, "isDragOnly": false, "dragX": 0, "dragY": 0

@paper_lung In addition to @d-healey's example,. if I'm understanding you correctly, you could simply have an if/then that read the FX parameter, and set the new value based on the current value.

@Lumi283 I made a video about lottie

I also did one about making a progress bar

And here's one that shows an easy way to count up and down in a loop or timer

Let me know if you need more info.

I have found a simple solution with the MidiList object:

When a Note On command comes in, then in a MidiList the index of the pressed key is set to the value of the note that is output. e.g. I press key 60 which is not active but only the next key so "60 -> 61" is stored in the MidiList. When a Note Off command comes in, before the Note Off command is sent, it is first checked whether another key also has this value If no key has this value, a Note Off command is sent for the note and the key is set to -1 in the MidiList. If one or more keys have this value, the NoteOff command is not sent

onInit()

reg midiKeyList = Engine.createMidiList();

onNoteOn()

const receivedNote = Message.getNoteNumber(); var outputNote = getOutputNoteBySnapMode(receivedNote); midiKeyList.setValue(receivedNote, outputNote); sendNoteToMidiOut(outputNote);

onNoteOff()

const receivedNote = Message.getNoteNumber(); var outputNote = getOutputNoteBySnapMode(receivedNote); midiKeyList.setValue(receivedNote, -1); // set pressed Note in midiList to -1 if (midiKeyList.getValueAmount(outputNote) <= 0) { sendNoteToMidiOut(outputNote); }

I hope you can understand it.
Thanks guys

@d-healey That will work except with some edge cases, but will also double the count of components in the component list :face_with_tears_of_joy:

@Lumi283 Hit me up if you have any questions.

@aaronventure said in MIDI Learn 2024:

How does this work with persistence?

Midi Mappings are stored in a preset so you don't have to do anything. The JSON objects are just temporary objects that you need for manipulating the data model (or display stuff on the UI).

@d-healey Cheers mate - that did it - thanks!