Separating User MIDI Input and MIDI Player Events

[bozhidar]

Hi everyone,

I’m working on a live accompaniment setup in HISE and I need some guidance on properly separating user input from MIDI Player output.

Here’s my situation:

I want to use a MIDI Player to play accompaniment patterns (bass, chords, fills, etc.).

At the same time, I want to allow live keyboard input from the user.

I need to clearly know which notes are played by the user and which notes come from the MIDI Player, so I can:

Run chord detection only on user input

Transpose the MIDI Player notes in real time

Avoid conflicts between user notes and pattern notes.

I’d appreciate any advice, examples, or tips — I want to make sure I know exactly when a note comes from the user and when it comes from the MIDI Player.

Thanks in advance!

[HISEnberg]

@bozhidar There isn’t much in the docs about it but you just need to assign your two different MIDI sources (MIDI Player & User input) to two different MIDI channels. This SOS articles describes it, and it’s fairly simple to setup in HISE

https://www.soundonsound.com/techniques/midi-basics-part-1

https://docs.hise.dev/hise-modules/midi-processors/list/channelsetter.html

[Lindon]

isnt this what isArtificialEventActive() for?

I assume (so watch out) that the MIDI player events are artificial and user input are not..

https://docs.hise.dev/scripting/scripting-api/synth/index.html#isartificialeventactive