@griffinboy Cool I got it to compile with the callback!
Now it's a matter of properly reading the JSON I am sending... -> Working

UI code:

const var RoutingManager = Engine.getGlobalRoutingManager();
const var DataCable = RoutingManager.getCable("dataCable");

const var data = {level: 0.0};


inline function onKnob1Control(component, value)
{
	data.level = value;
	
	DataCable.sendData(data);
};

C++

    global_cable_data()
    {
        // Register a data callback for the global cable
        this->registerDataCallback<GlobalCables::dataCable>([this](const var& data)
        {
            if (auto* obj = data.getDynamicObject())
            {
                const var& levelVar = obj->getProperty("level");

                //if (levelVar.isDouble() || levelVar.isInt())
                //{
                    gain = static_cast<float>(static_cast<double>(levelVar));
                //}
            }
        });
    }

This doesn't seem to update gain

EDIT: my bad... wasn't listening on the right set of speakers lol WORKING LKE A CHARM!!!
Thanks a lot @griffinboy !

@griffinboy I tried many keywords already with no luck...

@griffinboy Yeah cable is what I am trying to use, I need to receive JSON data from UI.

Thanks for your template code it's awesome! Well... when I'll be able to make it work lol

@griffinboy @Christoph-Hart What is the way to send the value to the node from the UI?
Is there a callback that should be defined?

Yeah as @d-healey says the audio pro industry is wide and DSP are everywhere from automotive the adaptive sound systems for venues and so on. I also think the plugin world will change in the future in the manner we are interacting with, and more AI/DSP research leads to the necessity of getting more and more specialised with tools that might not be simple to use for the "simple man". Of course the implementation of some tools is made easy sometimes, but then the top notch systems will always be ahead, broader, and more complex. And with complexity arises computation power and compatibility issues. I am happy to see many great tools arriving but afraid at the same time, not being able to catch up compared to specialised folks.
In fact if I agree the market will grow, it might be for more engineered DAWs and tools integrating tech that I can't compete with for myself (like DAWs doing almost everything in the box, very "intelligent" plugins, automatic mixing tools, and other funky sweeteners...) while I am still struggling with basic DSP theory like I'm stuck in the 90s...
But I might be off-topic lol

@Christoph-Hart @Orvillain Yeah I did read and pasted here the crash report. Unfortunately I can't reproduce the issue so I can't slap a debugger. Will try more...

Unfortunately when I publish a new version the users need to resync their full library in LogicPro in order to get the plugin to update to the new version, so I can't ask them to do it 10x per day...
This is another issue, as I don't think people have to do this each time they update a single plugin (and one of the customers has more than 1000 plugins...). It's like no matter what you do with the version number, Logic doesn't take it as a new version. But I'm no Logic user so, who knows...

@clevername27 said in Roadmap to HISE 5:

@Christoph-Hart Meanwhile, I was fired by all three clients because of HISE bugs and secret ScriptNode documentation. sigh

Same... I have one that is crashing some customer hosts and I can't seems to find why. simple stuff, no modulation inside, just scriptnode, faust and third party C++. Hopefully this will be fixed one day, but without a proper investigation chances are very thin...

Don't want to troll the thread that been said! But might worth to speak about that again during the meetup

@Christoph-Hart I wondered about using an audiofile as well, seems a nice solution especially if I am creating the curve in the script interface.

But a global cable seems promising too, I need to wrap my head around the data type it can send. Just sending the control points and creating the curve in C++ node is surely a more efficient solution...

@Christoph-Hart Any news on this ExternalData SliderPack size limitation?

Side question, is this the best way to send a shaper curve to third party C++? Or is there another data object I can use to directly send an array of values?

I am also thinking about directly sending the curve control points to C++ and compute the curve there instead of interface script. But then how do I send the points? external table?

@Adam_G you need to load metaplugin first in PD, then load hise in metaplugin

@pcs800 So your knob needs to have 20-20000 for min-max with a stepSize of 1.

The error message you get is probably because the knob isn't declared in the script. But anyway, it shouldn't show a "steppy" behaviour with the above settings, unless something else is wrong...

@pcs800 what are your min & max? because a 0 to 1 knob with the finest stepsize from the drop down still shows some sticky behaviour (a hundred point is not enough)

So you can either make the knob 0 to 100 and divide the value where you need it, or simply set a finer stepSize with MyKnob.set("stepSize", 0.001)

I think having this resolution in the dropdown could be useful for everyone, I'll check if I can add it and make a pull-request...

@Chazrox because in the first line you explicitly force it to be 12, so in the end it never changes
and in the second line it's the old value + 12. So next time the old value will be the new one, +12… this is an incrementation.

@d-healey said in ARRAY || Get index value??:

Looks like Greg got there first :)

true, but with no comparable answer

@Chazrox myArray[index]

@Lindon but does the warning stay in certain cases ?

@Dan-Korneff Yeah I agree, and it's probably related to the hard LogicPro validation crash I also have for another customer.

@Christoph-Hart Are you able to follow the isPluginParameter case these days?

@d-healey well no I didn't, but I was thinking about isPluginParameter potentially causing troubles at init since the bypass button is an external parameter and meta as well...

@d-healey Might be... I reckon there's a way to test CCs in Hise, I am right?

So I have several customers complaining the plugin loads (Cubase and Bitwig) but produces no sound. No needle moving, just turning parameters and nothing happens...

Any clue where I should start?

It's all network based (successfully compiled and loaded in hardcoded FXs) and using a tiny Faust node and some basic SNEX as well...

Should I necessarily replace my working SNEX nodes with C++ nodes for the real guys?