@Lurch Cheers dude! I'll check it out!

So until we have native Cmajor support in HISE, how much of a pain would it be to compile a Cmajor patch as C++ and then use it in HISE as a 3rd party C++ node? Is there a web of dependent libraries you'll have to worry about including?

@Christoph-Hart What about the slider pack limitation of 128?

Could it be extended?
Or perhaps it would be better to use a cable with complex data to send a more precise curve?

Hey apologies for the bump. But I got this to work by putting:
JUCE_LOG_ASSERTIONS=1

into the preprocessor definitions and then rebuilding. I get data from my custom c++ node printing to the visual studio log:
947b7f47-31e0-48be-ad66-7de6be45afe0-image.png

It wasn't working until I did that.

I ended up piping data through a global cable and plotting it to a scriptPanel - it is pretty good actually!!!

But I would like to know how to utilise the display buffers directly on the node.

@Christoph-Hart

🤣

Cool thanks! I'm still figuring out how all of this interfaces, but getting there and making good progress!

@Orvillain

Oh yeah yeah, I found faults with the provided script too. I had to do some casting. I think that's correct.

@Christoph-Hart

Good to know that it wasn't anything bad. It didn't seem to be breaking anything.

Is it okay for me to use this function then? It says that I shouldn't here unless I'm rendering. But I couldn't really see why, so I've been using it

@griffinboy

edit* Rephrased into a more answerable question hopefully!

@bendurso Not that I'm aware of

@Morphoice hmm, weird, anyways, I've added a safe check as well as the option to edit the flags set by the node_properties.json file in the DLL exporter. This should fix most issues related to this subject.

@fellhouseaudio said in C++ API: SliderBase cannot find Constant Modulator (SIGSEV):

reach a SIGSEV in RootObject.h:61

I opened a github issue

@Christoph-Hart

Thanks I'll look into it!

@griffinboy For what I understand, it's not Hise to support latency, be it variable or not. Hise just reports what you want, so if you want it to be variable, technically, you should be able to do it.
But the DAW might not like it... It doesn't seem to be something "normal" to report a continuously changing value, but I can't refer to anything else than my own perfectible thoughts...

Thank you!!!

@mmprod Yep! We haven't announced it yet, so…well, if you know who I am, you probably know who it is. HISE will be on it! 👻

@ustk

I did have it working wonderfully. But I'm going to have to get back to you.
My copy of hise has gone completely insane - it cannot see any of my thirdparty nodes now, not even in old projects. I've really messed something up badly

edit: After doing some more tests, I think this is a bug

@Christoph-Hart This is super helpful and more than enough to get me started. Much appreciated.

@ustk Yeah it's giving me super weird behaviour too, and it seems like the data objects have a "memory" so even when you change the number of sliders it shows a previous number that was being used.