@CatABC
Okay, so you want to take a screenshot of the plug-in background? I don't think that's possible.

@Christoph-Hart Amazing! So do you think you will just present all of the new features and we can arrange a separate meetup for the modulation system then? I imagine a majority of the questions are going to be about this...

@d-healey can I ask you to set this up as you did last time? I can help creating the doodle poll if need be. I don't think I am alone in assuming that we would love to see a short presentation on your new online course, how things are going and your game plan for it!

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

Link Preview Image Show expansion presets, regardless of expansion column visibility by davidhealey · Pull Request #772 · christophhart/HISE

Forum thread: https://forum.hise.audio/topic/13373/preset-browser-and-expansions-again

favicon

GitHub (github.com)

@Christoph-Hart Nice, thanks! Yeah, the idea is to start with just a few sound designers for now — actually, just one who reached out to me, hehe.

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

Just seeing that using Engine.addModuleStateToUserPreset("MyFlex") solves this!

@Lindon well the macro modulators fail to work at all - still -

@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

This has already been discussed somewhere here.
The “Extract Metadata for Mapping” button is not in sync with the internal variable. That means it may appear to be on, but it’s actually off. A simple workaround is to toggle the button off and on again.

@Christoph-Hart , I think this can be easily fixed in FileImportDialog on line 39:

metadataButton->setToggleState(true, sendNotification);