I checked it: in the MIDI file, the notes are written before the controller. When the MIDI file plays on a MIDI track connected to love language test the plugin in ... It is well-known that MIDI lags if you are transmitting lots of data, regardless of the hardware you use to send it. And music is very timing- ...Latency occurs when software sound modules and/or effects that respond to MIDI data begin consuming too much processor time. As you add voices ...

@orange Yeah, that's a good point.

@DanH Thanks. The elements are all there. I guess I will have to look very closely to see if I can spot anything out of the ordinary.

@ustk Australia. English. I am waiting to hear whether he has any alternative languages or keyboards set up in his system.

@d-healey Aha. Found it. I see the working plugin. I guess the references to others are just stored in some Logic cache. Thanks, Dave!

@DanH right so just 'FACTORY/YourCoolPreset' works... no need for .preset at the end or 'UserPresets' before :)

@RastaChess you are very welcome 😊

@Christoph-Hart I am delighted to report that the method you provided here works like a charm! Thank you so much!

For anyone using it, just remember to set the condition that if

Engine.getOS() == "OSX"

use the method above and place those variables as 'var' inside the condition.

@gorangrooves Seems that updating to the latest XCode 15.2 fixed the issues.

@d-healey Success. Managed to compile AAX and VST2 just as well. Thank you, Dave, and thank you, Christoph!

So, if I understand correctly, the colors for combo boxes were set in the actual combo boxes without the LAF

I just reread your exampe and noticed you were using the popup menu LAF functions. The popup menu is not part of the combobox component, so there are no colours in the obj parameter.

A good practice for anything regarding LAF customization is to always use Console.print(trace(obj)) as first line of the function, then you'll see everything you can work with.

@Christoph-Hart I disabled everything in my plugin other than the main declarations, paths, and LAF.
I even disabled fonts, synth defer callbacks. I have nothing else to disable.

There are 2 issues.

One has something to do with one of my scripts, resulting in onNoteOn not working and the expanding panel not expanding. I'll get to that in a little bit.

The second issue has to do with Pro Tools not displaying anything that is painted using paths. It displays simple elements created using the paint routine but no SVG paths. My previous version of plugin didn't use any paths, hence the reason why it displays ok in PT.

When I use your test script to repaint everything, after a few seconds, all elements show up. So, my conclusion is that there is a bug with painting SVG paths in PT on init.

Can you replicate this issue on your end?

@d-healey Sweet. You are very welcome. Even if you decide to make your own (to suit your plugins) at some point, this should help the process be quicker. 😁

@ustk Thanks. So, this would be something for @Christoph-Hart to implement at some point if he deems it worthwhile? :beaming_face_with_smiling_eyes:

@d-healey Awesome. Thank you very much! That will help me greatly.

@d-healey No, it is not that. I have enabled it, and the other meters are working.

@d-healey Of course! I overlooked that critical part and only focused on the decay. Thank you so much, Dave! That was illuminating, and I think I am almost finished with the most sophisticated hi-hat script in history of the universe :beaming_face_with_smiling_eyes:

@d-healey Thank you!

@d-healey Looking at the matrix output, it moves at the rate set by the floating tile.
So, I guess the setting I was looking for was hidden in a weird place :beaming_face_with_smiling_eyes:

Thank you for the tip!