@ustk The generosity of the man.

@DanH Hahaha, it's so simple, thank you very much for your guidance😙

@pcs800 I'm not sure, effects are not my strong area

@d-healey Okay, thanks David.🥂

@Christoph-Hart said in Mac FX failing pluginval.....:

@Lindon said in Mac FX failing pluginval.....:

DLL?, If so then if its broken(corrupt) for one HCFX shouldn't it be broken for all of them?

Yes, but the error you describe is not a deterministic programming logic error but a case of undefined behaviour - something in there is not clearing the buffers correctly and this may or may not result in trash values being in there which is what pluginval complained about.

Okay, well its all a bit academic and I dont want to monopolise your time, but that sorta doesnt jive with my understanding(which may well be where the fault lies)... these HCFX are simple filters, and there is no signal being sent thru them by pluginval, and they work fine in 3 cases (slots 1,2, & 4) but not a 4th(slot 3), where all cases are exactly the same "piece of code". One of them is generating "something unpleasant"(tm) which I might thing was the cumulative effect of the previous signal modifications, but then the 4th slot should accept this unpleasant output and reproduce it again, and it doesnt....

So bypass slot 3, but include slots 1,2, & 4 = passes
Bypass Slot 4, and include 1,2 & 3 = fail
bypass everything except 3 = fail
Bypass any combo that includes slot 3 = pass

well never mind this bit is working, more pressing issues(like the macro modulators not working at all...)

@Christoph-Hart Clever! 😎 can't wait for it!

..actually lets have a slightly more convoluted example - because I was actually thinking about doing this:

Lets say the player is free, and I work with 10 designers, each gets 70% of their expansions sales, so as a total Im getting 30% of all sales, and each designer in turn is getting 7% of all sales - assuming some sort of even spread of sales across all expansions...

@Oli-Ullmann said in Paste screenshot in HISE plugin?:

That sounds interesting! To do that, you would definitely have to check which OS is being used, as different operating systems use different folders. I'm also not sure if this can be configured individually for some operating systems... Tricky! 😁

This could just be asked to the user at first launch and stored in a pref file

Then background task to run a bash script (but yeah this one is OS dependent)

https://forum.hise.audio//post/101582

Fixed the presets not showing up unless the expansion column is visible

https://github.com/christophhart/HISE/pull/772

@HISEnberg (cc: @ulrik ) oh yes, and thank you, but that's not quite the problem. I've successfully compiled HISE and other VST/AU/AAX plugins with 32 outs. I've also compiled other DSP networks successfully before while utilizing all 32 outs, but never any with an external display buffer.

Something about having the extra channels in HISE is messing with any use of External DisplayBuffer in a compiled dll and causing a crash.

If anyone else can replicate this issue or give me a point in the right direction I'd much appreciate it: If HISE is compiled with the extra preprocessor tag NUM_MAX_CHANNELS=32, compiled DSP networks using an External DisplayBuffer cause a crash when loading into Hardcoded MasterFX (due to some sort of channel number mismatch)

Thanks again 🙏

@HISEnberg
Ah ok, thank you for the info! :-) Then I have to search for another granular solution.

@VirtualVirgin The editor drives me batty. It functions so differently to what I'm used to that I'm constantly making subtle typos that fail to compile.

I'm looking into coding in my familiar code editor and hopping back to HISE just to hit F5. Thinking about it, there might even be a way to automate it. Set up a file watcher and every time a script file int he HISE project is saved, tell HISE to compile. 🤔

@d-healey yeah sorry my slow half typing skills...

@ustk sure you can use a laf script function as always.

@DanH
Okay, I totally understand what you mean!

@Christoph-Hart Ah ok, thanks for the info.

@CatABC Send a complete example to learn from

@ustk

Yeah of course if it's c++ dsp, you can just use a global cable to send the graph to the UI
Keep a second, mono class of the compressor dsp without envelopes, and when a paramter changes, compute the response (staggered updates) using that instance and send it as a json to the UI side of Hise.

But you can even do this in Hise if you want. I doubt the compressor algorithm is complex. Just write it as Hise script and process your line through it.
Without envelopes, a compressor is a waveshaper. It'll just be a simple algo