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:

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 :)

@Christoph-Hart
I would think it's best just to let the user decide if they want to use it, like any other CC.

Now, upon testing the CC learn (I was curious to make sure it is blocking the consumed CCs at the output for use with MIDI plugins, and it does), but I must say that the CC learn being channel agnostic is not a good idea. This is not how most VST instruments will handle this.

Here in this simple MIDI utility I made, I just ran a test to check the channel filter operation in conjunction with the MIDI learn.

The MIDI learned control to CC#1 (Velocity Transpose Amount) is not affected by the channel filter, so even if my notes aren't going through, my CC values are.

The MIDI learns need to be channel selectable somehow in order to work in multitimbral settings where the VSTi endpoint is only meant to receive from one channel, otherwise you will have lots of unwanted CC messages going to the other channels/instruments.

Is there a way currently to make sure the CC learn can be filtered by channel?

I am not seeing channel selection in the MidiLearnPanel:

@d-healey said in Adding an LAF knob ("rotary slider") did not work properly and changed appearance of other items as well:

.setLocalLookAndFeel()

Thanks! All is looking as expected now and I can move on in your tutorial :)

@VirtualVirgin Sorry about the multiples! I kept getting a "bad gateway error" when trying to post and it didn't look like they went through.

@d-healey said in Help with iteration:

@VirtualVirgin for that use case it's better to use a panel rather than an array of buttons. Using a panel is also dynamic so you can change the number of dot boxes on the fly

In the example above the buttons are already on a panel.
Are you saying I should use a panel instead of buttons?
I can get multiple values from different places on a panel?

@d-healey said in Help with iteration:

@VirtualVirgin

What's a dot box?

A "DotBox" is just a modification of your checkbox.
I prefer the dots for button matrices:

I am trying to make variable definitions for 16 "Dotboxes" here, but I apparently have the syntax wrong:

How should I write it?

@d-healey said in Can I hide/collapse a long piece of code like this path?:

@VirtualVirgin

Right click, and uncheck "Enable line breaks"

Thank you!!

I just want to make it easier to scroll past.

@d-healey

Three thumbs up!
Building matrices is on my todo list for next week, so this will come in handy!

Sample Modeling instruments do essentially what you are asking about here, so it's definitely do-able.

"All Samplemodeling instruments exploit Dr. Giorgio Tommasini’s patented 'Harmonic Alignment' technique, which ensures for the first time seamless transitions across virtually infinite dynamics, from pianissimo to fortissimo."

https://www.samplemodeling.com/about-us/

I can't seem to find any more information on the patent, but if I come across something I will post it.

You should probably ask Aaron Venture some questions, as his instruments are doing something similar:

"Phase-aligned samples result in no perceived cross-fades between the layers; the response is smooth, musical, and sounds like the real thing."

https://www.aaronventure.com/infinite-brass

@Christoph-Hart
I would think it's best just to let the user decide if they want to use it, like any other CC.

Now, upon testing the CC learn (I was curious to make sure it is blocking the consumed CCs at the output for use with MIDI plugins, and it does), but I must say that the CC learn being channel agnostic is not a good idea. This is not how most VST instruments will handle this.

Here in this simple MIDI utility I made, I just ran a test to check the channel filter operation in conjunction with the MIDI learn.

The MIDI learned control to CC#1 (Velocity Transpose Amount) is not affected by the channel filter, so even if my notes aren't going through, my CC values are.

The MIDI learns need to be channel selectable somehow in order to work in multitimbral settings where the VSTi endpoint is only meant to receive from one channel, otherwise you will have lots of unwanted CC messages going to the other channels/instruments.

Is there a way currently to make sure the CC learn can be filtered by channel?

I am not seeing channel selection in the MidiLearnPanel:

@d-healey said in Confusing results from message delay?:

@VirtualVirgin I have a chord detector script which adds notes to an array as they come in and then processes them. Sounds like a similar thing.

Here's a simple snippet that adds note numbers to an array in on note on and removes them in on note off. Works with notes played at the same time and sequentially.

HiseSnippet 731.3ocsUstSaCCE1tzfV6tngzd.xOKSHTaoEnBMMfdYqaqP0JCMooIjiiSiEI1QNNrUMs248FrcbRfFfJtTokeTky8udNemSFqjTVbrTgvUOYVDCgel0jYBseWeBWfF1Cgeg0HRrloryTc3rHRbLyEgwq7NiBbkxnzm+71CIADAkMWEBcpjSYehGx0y0Nd+OxCBFPbYmvCK3cq8GRkhtx.YBfmUrpihHzyISYGQLtUxB8dRrOB+ZKGhScB0ya6lN65UuUy1McbZ41Bz3rSmNc7Z2fzdqcnTDd09tbsTMQSzrXHoGJcmMwW9CQVANkGycBXFgFnIPkyTi55yCbGeYyIFgvkGOuUsRVq5UVi3t7qzOuk8xTC1yinXSCW5tfTiGAjvEfT4LHsl0DphGomawfmmZMT.SPOBLaJBkLeQk9.1pqD7Pn2LjbNafBDtJhZaWu9F1vOquW0pJ1TagDvs8ar+122yKQP0bovVJNBzdrn15U+U0JARJIvV.9LB.AL.2bJSab3njPGlplISURSylQIw9C8.aGDnXD2Ym3yTrZBvieW09lo2y6QmeEKTdwhRn4OrRFDXb2jyaX1vLWrk7.qIRq0F1WPBRXW4HLIt93c0G13kl0+K3nTLTv0GGwxkGHCbMiMy62lLfxGfvaeYXOhlX3G45.+hXJM2.GbO1EvFYFaohUOV74ZYDrSdKpDPhktIAD80Y1lc9bCP+3ZzICkQDy0yJdS3QP2qemz8GJDWyZLWS8WLFKs.LBcp+GXL+Hwys564wn54.rr0futrWDtmx+YYhlKlNhnU7ehvVv9vD3XJkAUWHXAPxsvkLrkL45FYSGXBS3lJ7W3I2XCiLN2XiKMhBITk7LZ1Vf4LzSR0.XRjdltB78BP1tAJcynXeNDtJdl4pbwTcq.atrAt0xFXqkMv1KafaurAtyxF3t2eflOZcPhVFls1fPiF2O8TBF2WP.FXJaE8OLLOJoG

Thanks :)
I'll check this out tomorrow.
I did end up solving for the delay problem by moving the rest of the code into a child container with another script processor.

The notes from the note recorder get delayed by 1 sample, and that gives room for the array to record all of the voices before sorting the order in the next module.
The basic problem that the delay solves is that the array cannot be sorted and reversed until all of the notes are in.

It is working so far:

I have a stray note off that I will try to clean up, but at the moment is not effecting the function.