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

David is right.

If you're creating controls using a helper function, simply create another one. You can then be increasing a counter which you can use to automatically set up the sliders in order for every control created.

Callbacks could be tricky, because if you simply put the function into the callback for another control, depending on the exact situation, you could end up with the same stuff executing twice, which may or may not be problem, but is something you should be aware of.

So you'll have to decide whether you'll be assigning a function as a callback for both controls, or do something else. You could use a broadcaster to automatically update the values of the simplified slider whenever the main control changes (attaching controls could be automatized with the helper function). The helper function should also let you automatize the assignment of a control callback for the simplified sliders: this would be an inline function defined outside of the helper function, which would be calling .changed() of the main slider. You could also automate the targeting of the correct pair component via ID by deciding on a naming scheme (e.g. Slider1_main and Slider1_simplified) and using the component argument of the callback function to get the target.

This not only simplifies your code by letting you only worry about the true functionality of a single callback function per control, but calling changed() for the main slider makes sure that that particular component gets set as "last touched" for the DAW, letting you maintain the mirage of it all being a "single control".

Another way would be to actually be using only a single set of controls, storing dimensioning and positioning data into JSON, creating a switch in your every LAF and changing all these properties when the simplified GUI button gets clicked. Depending on your GUI setup, you might also have to reparent controls (can you even do this beyond on init?), so this approach doesn't scale super well and would need a bit of tailoring for each individual GUI.

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

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

@eliasbor In the Property Editor on the right side, click on your SliderPack and change the SliderPackIndex (near the bottom) to either 1 or 2.

@d-healey aaaah ok now it works thank you!

@d-healey I've been watching the post for a few days, did you manage to do it? I don't quite understand how to do it

@d-healey Righto, thanks!

Bump - anyone with web view experience able to weigh in? I've done some more playing around and can't get any further with it.

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

@udalilprofile you can paint on panels so it should possible

https://m.youtube.com/watch?v=nmB_Ml-XWGg

This video covers it somewhat but you would need tweak it for what you’re looking for

@d-healey Thank you as always.

@d-healey Thank you - can you explain that a bit more? I'm not sure what you mean. Got ya- will try!

@Xenox-AFL
If you want to set the value of a button/slider/component in an array you have to do something like this:

array[0].setValue();

@d-healey pity. but I'm diggint the solution you posted a while ago, so that's probably the way I'll be going. It's a brilliant idea you had there.

@mmprod This is awesome- exactly what I needed (thank you!)

@bendurso d'uh. :) thanks

@orange wow...just should've scrolled back a few days in the forum lol...question...this is connected to a delay...how would I connect it to just the global BPM?

@d-healey No, only if the app active, I tried this without the timer now, and it works nicely
As soon as I make the app active it's possible to use the setKeypressCallback
So in. the snippet, I removed the timer function and it worked
😀

@griffinboy the SNEX API has three main container types and if you want to use the index template for interpolating / safe access you need to use them. They differ in their ability to change their size dynamically and whether or not they "own" the data:

span: owns the data, compile time size (allocated on creation) dyn: doesn't own the data, only refers to it heap: owns the data, but allocates it dynamically

The easiest entry into this would be creating a dyn<T> container with a simple T* pointer and a size. Almost any container in the world will give you access to the raw data. Here's a std::vector<float> example:

std::vector<float> x; x.push_back(1.0f); x.push_back(1.0f); x.push_back(1.0f); dyn<float> snexContainer(x.data(), x.size());