@d-healey Yeah, I looked carefully and it is indeed.:cat_face_with_tears_of_joy:

@Lindon said in I don't really understand this pairing system for HISE MIDI note on and note off messages:

@VirtualVirgin print the Event ID and see if they match...

So here it is with the Event ID:

Screenshot 2024-11-09 at 11.30.56 AM.png

As you can see, the hung note (the last 60 on the list) is not closing the note on 60 that just preceded it.

So I would assume that HISE is trying to match the event ID of the note off to a note on before making it "available" or "active".

I just don't understand this method or the point of it.

Why is it trying to close notes that are already closed?
In the type of MIDI engineering I am used to, if a note off occurs after a note on of the same channel and note number, it closes that note, end of story. No other special conditions needed.

Is there some way to turn this Event ID matching system off for the note messages?
I would like that last note off 60 to close the previous note on, no matter the Event ID.

I know this may muddy the waters a bit...but ive actually never code signed my VST3/AU...only my AAX because its required...Ive only ever codesigned the .PKG when I was using those and the Standalone app(via apple's signing/ notarizing in Xcode) now I have a custom installer that I built and I only have to codesign/Notirize it via Xcode(not via the terminal) and I dont worry about the cosigning any of the individual binaries...and all my plugins run just fine for my users...

@HISEnberg Aha, thank you! I was getting errors because I am using NUM_HARDCODED_FX_MODS=6, and addModuleStateToUserPreset cannot work with child processors. But I edited the XML file and now it saves how I want it to.

@Dan-Korneff PERFECT! Thanks!

I am having similar problem in mac OSX. AU plugins showing but VST3 for Mac not showing up.

Nevermind!
Once I closed and reopened the project from the new folder name it works.
That one should have been obvious to me.

Oh this is great!
I copied a panel with a bunch of components on it and they all copy in one go :)

@Lindon I have this wrong, I just checked an old script. It is obj.isTicked and it allows you to set a specific paint routine for the object selected.

Looks like you can implement CSS on the combobox now so I imagine this is a much stronger alternative:

Link Preview Image HISE | Docs

favicon

(docs.hise.audio)

@orange said in Need someone to implement a design with Hise LAF - not sure where to look!:

Then this could be the topic of the next video :)

It's in the queue

@d-healey Thnx for sharing!
I also have this issue.

@Christoph-Hart Could you help me with this?

@orange Tysm :)))))

So it seems the artificial note offs do not work unless you use
Message.sendToMidiOut();

I find this a bit confusing as other messages work properly to pass on to subsequent modules in the rack. Why would the artificial note offs be treated differently from that?

In the Event Logger they now appear to "pair" (the brackets on the left side) with the note ons that precede them at the same note number:

Screenshot 2024-11-07 at 9.25.28 PM.png

I thought the
Message.sendToMidiOut();
was essentially just routing a copy any MIDI appearing at that point to go to the output of the plugin, so I'm not clear on why that would be effecting the internal relationship of note on to note off messages. Where exactly were the note offs going before that would make them appear on the Event Logger, but not have them usable?