@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 
@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?
But my ranges are the same... Could it be because the skewFactor is different? Is it bad?
Most importantly, can this cause issues with DAWs?
I have several customers complaining:
@Dan-Korneff said in Running a shell script:
I think the .command will automatically open terminal.
Seriously ? I searched for hours and GPT couldn't say more than "use Automator to start the shell automatically..." 
Your're the man 
@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?
@griffinboy said in C++ Third Party node SliderPack, Span & sfloat:
The thing you must makes sure of when using this xfade method, is getting it to update to the latest version. For instance if you do a bunch of small changes, it needs to finish the first crossfade, and then look to see if the current value doesn't match what it needs to be (since you may have moved it again during it's xfade). At the end of the xfade this check just needs to be inserted, and to retrigger another fade if so.
Effectively this seems to be the trickiest part, even if easy to understand the principle... I'm getting there step by step! 
@d-healey Yeah I've seen that command, but then I don't know what "still single-threaded" means if we can set the number of threads...
@Natan I recommend the Macbook Air M1 with 16GB and the fastest CPU option (10 core I think). It compiles HISE almost as fast as my 9900K desktop without a f...
Forum (forum.hise.audio)
@d-healey @dannytaurus Could it be related to a multi-threading not optimised for mac when using xcode? I reckon a discussion about this and a possible flag to enable/disable. I think it's about the mac preferring to work with a single thread or something like that...
@Dan-Korneff @griffinboy Very interesting, thanks guys! I'll try to apply this concept with the sliderpack and local span for old/new curve
@Dan-Korneff Instead of the fractional + jmap, is there a particular reason you're not using an interpolator? Also the counter is not per channel but the idea makes sense even if not optimised