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

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

@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);

@HISEnberg said in SlotFX (Hardcoded) Persistence?:

Engine.addModuleStateToUserPreset(var moduleId)

Yeh this seems to be working, I still have a dereferenced nullptr on the interface somewhere when I try and delete the plugin that I have to track down but otherwise it's doing the thing

@cassettedeath Scratch that

Incase anyone encounters the same issue I did, I used

var myPresetList = Engine.getUserPresetList(); const var RandomPreset = Content.getComponent("RandomPreset"); inline function onRandomPresetControl(component, value) { if(value) { // Get the current list of presets from disk local presets = Engine.getUserPresetList(); if(presets.length > 0) { // Pick a random index local index = Math.floor(Math.random() * presets.length); // Load it by name with the .preset extension Engine.loadUserPreset(presets[index] + ".preset"); } else { Console.print("No user presets available."); } } } RandomPreset.setControlCallback(onRandomPresetControl);

this is happening to me too, and is preventing me from properly debugging a crash @Christoph-Hart

@d-healey OK， I understand, thank you David

@lijas90 You have to put them in the folder before you map them.

So now you have the choice, either you can remap them - which is what I would do if it's not too many samples.

Or you can edit the xml file to use the wildcard instead of the absolute path.

@d-healeyOk, I think I know where the problem is. I hadn’t downloaded the Apple Silicon version of Xcode. I’m still having some issues but I’m making progress. Thanks, David!

@d-healey Thanks for the advice, this makes a lot of sense ill be doing this!!