@aaronventure I would expect it to work in the same way as component value broadcasters and component control callbacks. - I've never tested which triggers first. I think after the callback would make the most sense.

Edit: I just did the test with the value broadcaster and it fires before the component control callback, but I think for MIDI messages it makes sense for the callback to fire first - although I haven't given it much thought.

@aaronventure Oh I understand now, that wouldn't be affected at all. The broadcaster only exists within the script processor in which it is declared.

It's like having multiple on note on callbacks in a single processor.

@jeffd no idea, debugging these kind of mystery issues is never fun

@jeffd Try a new project and see if the same issue occurs.

@musictop said in Let’s Build the “League of Newbies”:

Cool, I am working on some stuff in Rhapsody and have some questions and such.

Nice, send me a PM

@aaronventure Broadcasters have a priority setting for this purpose. But most of my modules are independent and the order doesn't matter.

@aaronventure That's it!

@aaronventure In on note on I call articulationHandler.onNoteOn() which handles all the necessary stuff for updating the UI. This is just one example, I also have a similar call in on controller, for my guitar stuff I have similar things.

Basically anything that responds to MIDI input currently has to be called directly from the MIDI callbacks, I'd like to see an observer pattern option as this is the way HISE seems to be going in general and it's making things so much more modular.

@ustk I think I had the same dream

@VirtualVirgin You can only pass a single parameter to the function. To pass multiple values you place them in an array:
Label1.setConsumedKeyPresses([{keyCode: 27}, {keyCode: 13}]);

A broadcaster that is triggered by incoming MIDI.

Example use case:

I have a list of articulations on the UI. When a "keyswitch" is pressed I change the selected articulation displayed in the list. This is managed from an "Articulation Handler" namespace.

My current solution is to call the necessary function in the articulation handler from the on note on callback. But it would be nice if the behaviour could be self-contained within the namespace and the note on callback didn't need to be aware of the articulation handler's existence.

@jeffd Yeah I've seen that before

@jeffd Looks like you unlocked a hidden feature :)

@VirtualVirgin said in How does the .keyPressCallback() work?:

The parameters in curly brackets, that is not a key : value pair I think but is it JSON?

JSON is made up of key/value pairs, so yes it's a JSON object with a key value pair :)

@VirtualVirgin said in How does the .keyPressCallback() work?:

That "hasFocus" seems reversed. Is that a bug, or do I not understand the logic of it?

Yeah seems inverted to me too - there are a few things in HISE like that.

@jeffd I thought the stereo/mono thing was only for effects

@VirtualVirgin

Ok so you start off with this

const var Label1 = Content.getComponent("Label1");

Label1.setConsumedKeyPresses("all");

Label1.setKeyPressCallback(function(event)
{
	Console.print(trace(event));
});

Click on the label and start pressing keys, and you'll see the data that comes up for the keys you're interested in. - Notice that at this point we are consuming all keypresses.

Once you've got the data for just the keypresses you are interested in you can replace "all" with that data.

For example:

const var Label1 = Content.getComponent("Label1");

Label1.setConsumedKeyPresses({keyCode: 27});

Label1.setKeyPressCallback(function(event)
{
	if (event.isFocusChange)
	{
		// Respond to focus changes here
		Console.print("FOCUS CHANGE");
		return;
	}
	
	// If we get to here, then the escape key (27) must have been pressed
	Console.print("ESC PRESSED!!!");
	
});

@jeffd I'm not familiar with the activation system so I won't be much help with that.

@jeffd Well that at least implies samples are being loaded. Try it in Reaper

@jeffd What does the RAM usage for your plugin show?

@jeffd That's only useful for a standalone app, if you're using it as a plugin then the input devices is controlled by the host.