Your wishes have been heard:

https://github.com/christophhart/HISE/commit/4c8930b123ad49d9a4df697fa7fbf9348789b70e

BTW, I am working on a full example of implementing a copy protection scheme like you described. I'll put it into the tutorial repo in a few minutes.

Yes, implementing a sleep functionality in a multithreaded environment is the worst. I have played around with this, but it involves stack unrolling and restoring the value of every local variable.

@Christoph-Hart really, I'm at the point of taking any (even slightly ragged) functionality... so thanks

@Christoph-Hart Hi, is there any correction planned on this?

@d-healey Thanks! I was trying to figure out how to make that work, but not having much luck- haven't done any programming since a college course on Unity over three years ago now; more than a little rusty.

@dustbro said in Formant Filter:

If you find some code on the net that has the right kind of license, @Christoph-Hart could probably wrap it in HISE.

Something here:

GitHub Search Result

and here:

Example

Got this error today! I think your topic should be on Bug Reports

1.png

I thought of another use case for this. If I load in multiple instances of my plugin and I want to purge a mic position in all instances I have to go to each instance individually and click the purge button. If I could link all the instances together and just set the purge state on one it would be much faster.

Yes if your material is 16bit from the start, you won‘t get any benefits from using Full dynamics. Just disable it at exporting and the end user will not have this option.

Oh and the .hrx compression / decompression is 100% bit equal, the Full Dynamics is something baked into HLAC directly.

@christoph-hart It says this in the technical documentation

Construct a time and pitch stretcher object to run at the given sample rate, with the given number of channels

https://breakfastquay.com/rubberband/code-doc/classRubberBand_1_1RubberBandStretcher.html

Yeah sure, why not. I wonder why I didn't add it already (normally I add both getters and setters whenever I add a property).

I've just been doing some stuff with HISEs LFO, trying to imitate something I was doing in Kontakt previously. To get the same LFO response in Kontakt as I get in HISE I have to set Kontakt's LFO phase to 275, so it would be handy if I could adjust it in HISE to get it to match Kontakt.

@christoph-hart said in Sample editor spectrogram:

Might be worth it...

I think so :)

@christoph-hart said in Feature Request - Monolith/File System:

The samples are protected and the end user won't have to move them around individually. I can even remember that some people wanted to delete a few unused .ch1 files of a library on hard drives where space is tight.

So True!!!

@christoph-hart fair enough

I have added a RebuildPoolFiles setting which makes sure that the cached files are cleaned before exporting. For bigger projects it does add some overhead to the compilation time so the pro-option is turning it off and knowing when to delete them manually :)

@christoph-hart wow! I was playing with STK on Faust and it rocks!!!

Ah, that's just the print function. If there are no digits, it will print an integer. If you need a certain amount of digits, use Engine.doubleToString():

Console.print(Engine.doubleToString(2.0, 2));

@aombk HISE is really great for making instruments, which is what it's designed for. It also has some limited capability (which I haven't explored) for making effects but it's not really the best platform for that as that isn't its main focus. You'd probably have more luck with something like Cabbage, although as far as I know that doesn't provide a node based GUI.

You could write your own C++ module for HISE which would probably be better than writing your own effect from scratch in JUCE because you'd be able to take advantage of the things that are already part of HISE, such as the routing system and existing effects. You could also incorporate your module into the HISE source so that others could benefit from it and build upon/off it.