@Gudru said in change slope of filter fx:

@ustk thank you! if i had ahdsr on one filter, would i need to duplicate everything on the other? would controlling one attack knob on the ui control all attacks on all filters, to get slope?

you dont get filter slope(dB drop off over 1 octave) from the envelope - you need as @ustk says place filters in series to get increased slopes - so a 6dB slope filter, followed by another = a 12dB filter etc.

If you have filters in series like this then you will need to manage each ones q and freq together along with all the modulators(if you are using envelopes say) again "together"

This might be a useful read;

Link Preview Image Cascading filters | EarLevel Engineering

favicon

(www.earlevel.com)

@bendurso You have to have saveInPreset enabled, but in your postcallback you check if it's an internal preset load (DAW value) or not.

@Lindon yup, you can get shorter keys, have to use software though, but not at all worth the hassle

Click yes to rewrite the batch file. Then show us the contents of that file.

You don't need to compile Rhapsody instruments though, just export them directly Export >> Export Project

Also you don't need to add your includes the Rhapsody boilerplate folder, just leave them in the Scripts folder (or a sub-folder of your choice). Not that it will hurt to put them in the boilerplate folder though.

@d-healey
oh man, im trippin... thanks

@d-healey said in building HISE..:

@Lindon According to Christoph it should do. In the single test I did it went from about 20-25 minutes to 10-15 minutes in my VM. But it's possible that was caused by something else.

hmm, probably worth the risk then...

@d-healey yes, you right, i updated HISE using your fresh awesome script, and it was so refreshing that i almost started to jump around and scream of happiness :)

@d-healey yup I would also try to do it with OSC, it‘s a established protocol for exactly the kind of data you want to push around in a audio / music context.

@d-healey works like a charm!

laf.registerFunction("drawPresetBrowserDialog", function(g, obj) { if (obj.title == "Delete User Preset") { //draw delete dialog } else if (obj.title == "Rename User Preset") { //draw rename dialog } else if (obj.title == "Add new User Preset") { //draw add dialog } });

@Sawer You haven't set the processor ID

@Christoph-Hart is there a way to remove a CC assignment with scripting?

@Christoph-Hart thanks! I just totally forgot the modulation container exists for these cases!

@aaronventure Not something I've looked into, usually anytime I need smoothing I'm using a modulator that handles it.

@Dominik-Mayer Haven't got a bit of what you said but it sounds like you're having fun 😆

Once you've compressed your sample maps, you can open one of them in the sampler and from the right click context menu select Tools > Redirect Monolith Reference, and select the monolith (ch file) that contains the "master" version of the samples.

For example if you have a staccato sample map, and you are also using the staccato samples as release tails you could redirect the release tails sample map to use the samples in the staccato monolith. You can then delete the release sample map ch file.

You might also need to use Engine.setAllowDuplicateSamples(false); but I can't remember if that's necessary.

f5c722fb-e0dc-47ad-9fca-ba7488655d73-image.png

@Christoph-Hart thank you, it's solved now.
In some mystical way some nodes were in the AdditionalSourceCode folder, and I don't even have any of that stuff in this plugin.
I remember I started mixtring with script node to try something out, and I was in this project folder when I did that, it must had been a leftover.

I just deleted them and everything went fine 👍

@d-healey

Awesome. Thanks David!