I just wanted to make a note on how helpful David Healey is in this community, and that his tireless efforts to upgrade everyone’s knowledge are noticed and appreciated!

Thank you, David :)

Happy New Year!

Christoph,

First off, I would like to thank you for this amazing development tool for music :)

I am quite happy to be taking the plunge and learning as much about coding in HISE every day since watching and following the David Healey tutorial video: "How to make a synth"

Now, my main goals with HISE involve making MIDI plugins; some to be released as free utilities, and others as a paid product.

In my tests it seems that HISE does not receive or pass (thru) some MIDI message types:
MIDI clock
MTC
MMC
SysEx
etc.

Then there is Program Change, which HISE can accept and use, but not generate or pass (thru).

My concern:
When using HISE to make MIDI plugins, blocking these messages may deny users access to certain features that are needed for the next plugin in the chain (often a VSTi).

Therefore, if I am to produce MIDI plugins I am apprehensive about blocking those messages, and I, myself as a MIDI plugin customer would not be happy if a plugin that I purchased were to deny the passage of those messages to the output stage.

Personally, I do a lot of orchestral template mockups in a system where the articulation switching of VSTis is managed by expression maps (in Dorico, Nuendo, Bidule and Reaper) which are changed via incoming program change messages. Currently, I can't actually use any of my HISE produced MIDI plugins within this system, as without PC messages, it blocks the articulation switching.

In addition, there are many VSTis that can utilize program change messages directly to change patches. Kontakt, Omnisphere and VSL for starters.

And from my observation, it seems that many electronic producers with outboard gear setups require MTC (MIDI time code) and/or MIDI clock to sync devices.

I also have use-cases for plugin designs involving MIDI clock, MTC and SysEx and would love to have access to them for making custom MIDI controller managers.

Given that, I would like to add a feature request of three different levels (sorted from lowest to highest complexity):

1. a function to pass all unused MIDI messages directly to the MIDI output (without any processing)
2. a method of allowing HISE users to get and set MIDI messages in raw MIDI hex (so we can roll our own)
3. a feature set in the Message class for these other MIDI message types, similar to the ones available for note on, note off and CC.

Thanks for your time,
Craig

@clevername27 Thank you very much for your time!
You have a lot of incite to provide and I found the instruction as well as conversation to be quite worthwhile. I would certainly sign up again for more!

I am not sure what is causing this, but sometimes when I open a project/preset I am not getting any MIDI input and when I check the settings the MIDI inputs have been turned off:

Whereas I am certain I have saved it like this:

Yes, you can send MIDI out from button clicks.
I am working on a series of MIDI plugins at the moment.

You need to enable MIDI out in settings:

When using UI components to generate MIDI notes, you need to use Synth.addNoteOn() and Synth.addNoteOff() on the callback to you component.

Here I have pads (made with panels) which play chords when you use a mouse click.
It turns the notes off when the mouse is up.

			// mouse callbacks for the pads -- 
			pad.setMouseCallback(function[unitSize](event)
			{
				var ps = this.data.pitchSet;
				var l = ps.length;			
				
				if (event.clicked)
				{
					var velocity = Math.round(event.y / unitSize * 127);							
					for (k = 0; k < l; k++)
						Synth.addNoteOn(1, ps[k], velocity, 0);									
				}
				
				if (event.mouseUp)
				{				
					for (k = 0; k < l; k++)
						Synth.addNoteOff(1, ps[k], 0);
				}				
			});		

To get the MIDI to output from the plugin,
as others have said you must use Message.sendToMidiOut();

To make sure it catches everything (and not some intermediate stage of MIDI),
I always place these functions in a script processor and container after all of my other containers:

And place the Message.sendToMidiOut() on each of the three MIDI callbacks:

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

@HISEnberg Done, I created the group chat. I guess anyone else who is interested can post here and we can add them in.

Add me :)
I'll check it out.

@d-healey Worked! Thank you!

@VirtualVirgin said in HISE Meet Up:

Sorry I came in late! I was looking for a Doodle invite in my email.
When I checked in at the forum here, I noticed that the meeting was already going!

Once the time is accepted, Doodle should send it out in an email to everyone, and my Gmail puts that right in my calendar, so super convenient :)

Oh I see, it's like an optical illusion.
I need to do some more math on it.

@DabDab said in I'm having issues converting an SVG:

@ustk Thank you. Got the fundamentals. one last question. How can I do tracking circle?. Increase /decrease just like regular knobman things.

With

Content.createPath()

and

Path.addArc(var area, var fromRadians, var toRadians)

Multiply your arc endpoint (var toRadians) by obj.valueNormalized.

@d-healey Worked! Thank you!

@d-healey So I tried that:

But I get the same errors.
It is still looking for the ipp.

@d-healey So I tried this list (which is close to what I had done for the last three attempts).
This time I extracted the .zip directly to the the one I downloaded instead of copying that to some other place on my computer. This time it looked like the Projuicer initialized again, as it had the popups appear in the lower left to ignore.
When I checked the Preprocessor Definitions however it still said "PERFETTO=1" .
I tried adding the "USE_IPP=0" as you suggested:

But building in Visual Studio is still giving me the same errors about the ipp:

Ideas?

@d-healey I'm not finding any other copy of the source code on this computer (except under "Roaming\Recent" - so just a reference to the one I was just using). I have not built on Windows yet.

@d-healey What should I do about the other definitions that were there and now not?
I don't know what they are. Should I add them? I don't know how they are worded.

I'm trying to build the latest HISE develop branch on Widows 11 with Visual Studio 2022 and getting an error about ipp:

"Cannot open include file: 'ippcore_tl.h': No such file or directory"
"Cannot open include file: 'ippcore.h': No such file or directory"

Well, I'm not trying to use IPP and it is deselected the projucer.

When I trash the source code, redownload and then try to start again,
the Projucer keeps "remembering" the HISE standalone file, but it seems to have altered the settings so now the "Preprocessor Definitions" shows this:

Whereas the first time I went to build, Perfetto was set to "0" and there were others that were set to "1". I never changed this and don't understand how it has been changed, or why it is remembering this even after trashing the source code (and JUCE).

Ideas?

@d-healey said in Can I use this.over or this.down for paint routine on panel?:

@VirtualVirgin In the a panel's mouse callback you get a parameter, usually called event. This holds that information.

https://docs.hise.dev/scripting/scripting-in-hise/scriptpanel.html#the-mouseevent-callback

...

And I just re-read your question - you need to use a mouse callback, the panel is only repainted when you call the repaint function, so you can't dynamically get mouse information within it.

Thanks,
that is generally the way I do it, but I was trying to transfer an LAF to a paint routine and was wondering if there was any trick to lower the workload of it that I didn't know of.

When doing an LAF, you can use "obj.over", "obj.down" etc. to get the mouse state and change the appearance.

Can I use "this.over", "this.down" etc. to do the same for a panel?
I'm not getting any result from this Console.print():

		    if(this.over)
		    	Console.print("hover!");
		    	g.setColour(this.itemColour2);  
		        g.fillRoundedRectangle(ka, keyRound);
		    
		    
		    if(this.down)
		    	g.setColour(this.bgColour);
		        g.fillRoundedRectangle(ka, keyRound);

Just hoping I can do it this way without having to go use the mouseCallback explicitly for the panel.

@d-healey Thanks! That works :)

What is the proper syntax to use this?
I am trying this and getting an error: