Topics created by VirtualVirgin

@VirtualVirgin just delete them then.

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

@VirtualVirgin

Right click, and uncheck "Enable line breaks"

a85c46f4-8f4f-41d1-892d-8eab2c2ec354-image.png

Thank you!!

@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.

Screenshot 2024-11-12 at 11.28.22 AM.png

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:
Screenshot 2024-11-12 at 11.59.53 AM.png

@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

Peek 2024-11-11 23-23.gif

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.
Screenshot 2024-11-11 at 10.52.57 PM.png

Screenshot 2024-11-12 at 12.25.24 AM.png

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:
Screenshot 2024-11-12 at 12.33.00 AM.png

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

@VirtualVirgin said in Is there a method to force parallelization of code processing?:

@Lindon said in Is there a method to force parallelization of code processing?:

@VirtualVirgin this is not how MIDI works - as the MIDI Spec 1.0 makes very plain - MIDI is a serial protocol, so the notes must follow each other and cannot arrive at the same time....

I understand in theory the idea that that the MIDI messages are in serial.
If you generate notes for harmony, say using the Synth.addNoteOn() in HISE,
the order you generate them in the code will be the order they arise later on in a MIDI monitor, even if they are generated at the same sample. Note numbers generated out of sort order, say 74, 60, 77, will show up in the MIDI monitor later in that same order.

But in practice, the way I see it, MIDI messages that occur within the same sample are in some ways handled as if happening at the same time because a timestamp will read the same for all notes at that sample, and cannot be distinguished from using that information. So for time ID purposes they are the same.

MIDI from quantized DAWs, notation software and plugins generating harmonies will therefore return a time delta of "0" between messages in those vertical stacks (chords).

Screenshot 2024-11-10 at 12.17.09 PM.png

So not technically "at the same time", but from an ID perspective certainly categorized as the "at the same time" (timestamp).

Anyway, my question arises from trying to figure out how to handle MIDI messages occurring on the same sample when they need processing with a quick turnaround.
I'm sure you know a bit about it. I'll have some more questions later.

Yes, but no..... the MIDI spec says (if I remember correctly) that any receiving object needs only to act serially, so it can freely ignore the timestamp... so what you are doing is legal and accounted for - but no midi processor is required to process it in the same sample.... in fact given the laws of physics - they cant. - So it should come as no surprise when a midi processor of some sort (in this case HISE) doesnt behave the way you want.

@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.

@VirtualVirgin yeah been like this for yeeeeaaaarrrs....

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

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?

@VirtualVirgin You'd need to loop through the array and keep count in a variable

Ideally you use reserve(128) and a for loop where you push default values in the onInit callback.

Javascript usually doesn‘t complain about passing around undefined values but I found it to be the most frustrating source of issues while debugging (a little typo in the variable name goes through multiple function calls undetected and finding where it breaks is super annoying).

@aaronventure better safe than sorry :) but yes, the requirement for non-allocating local number variables was one of the first things I hacked into the scripting engine.

@d-healey said in Adding tabs in the Code Editor?:

@VirtualVirgin right click in it and a script editor - it will be removed when you restart HISE

Search "hydra tabs" to know more

Thanks :)
Had no idea all of that was in there.

@ulrik
Worked great! I like the that the text value follows the slider. I was considering adding that in :)

@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 said in Replacing stock button image:

The entire transparent area

What about if it's 50% transparent? And you didn't want that part affected by the background colour.

You can do this with look and feel though - including using an image.

@VirtualVirgin As I mentioned previously, that feature is to bring in external scripts that have been included in the snippet using the "include" keyword.

@orange said in Very newb question: how do I load an image file?:

@VirtualVirgin Copy the image file to the project's Images folder. After that, you can change all of the properties with setPropertiesFromJSON easily. I also added Width and Height for example.

const var VVLogo = Content.getComponent("VVLogo"); Content.setPropertiesFromJSON("VVLogo", { "width": 150, "height": 150, "fileName": "{PROJECT_FOLDER}VV_logo.jpg" });

Thank you :)
Yes, this solved it!

@ustk said in Simple question: How do I change the color of the button state light?:

@VirtualVirgin just use the alpha for the background as well

laf.registerFunction("drawToggleButton", function(g, obj) { //g.setColour(obj.bgColour); g.setColour(Colours.withAlpha(obj.bgColour, obj.value ? 1.0 : 0.5)); // <= this instead g.fillRoundedRectangle(obj.area, 4.0); /* This is not needed since you do it right above, no matter if the button is clicked/hover or not if(obj.over) g.fillRoundedRectangle(obj.area, 4.0); if(obj.down) g.fillRoundedRectangle(obj.area, 4.0); */ g.setColour(Colours.withAlpha(obj.textColour, obj.value ? 1.0 : 0.5)); g.setFont("Arial Bold", 14.0); g.drawAlignedText(obj.text, obj.area, "centred"); });

Thanks! This works just as I expected.