Posts made by Christoph Hart

https://github.com/christophhart/HISE/blob/master/hi_scripting/scripting/api/ScriptingApiContent.cpp

Line 751 reveals the answer

To be honest I have no interest embedding other copy protection services. There is the GPL way, the simple solution sketched up here and an inhouse solution for more advanced copy protection so there are plenty of options available.

I embedded TurboActivate in a product a few years ago and it was absolute nightmare so I vowed to myself to never do this again

@Lindon Yeah but if it explodes let me know.

You should be fine with up to 100 of them per plugin instance.

Well, MIDI out came up literally three days ago, so I'll add this after I finished this feature.

Also, with this system you can make your LFO with custom loop points yourself. Classic case of "Teach a man how to fish"

One of the main reasons why I am adding this is to remove the pressure from the inbuilt modules to catch every possible use case: There will be ready made modules for 90% of the use cases, but if you need something special like you've requested, you can get your hands dirty and patch it yourself. Be aware that this system also includes a C++ code generator that will spit out a C++ class mirroring your patch with close to hand-written performance, so in the end you won't have any performance overhead.

And what's the problem with the sample load process?

Next teaser

I just mirrored the JUCE functionality here which works with integers and I don't see an actual use case where this does become a real problem so chances are tiny that I'll add this - or in other words: 9000 up votes and I'll do it

Yes I removed a few settings that are either redundant or not working:

• Open GL mode (is deactivated since a long time internally, never got it to work consistently anyway)
• CC sustain remap (totally exotic use case, just use a MIDI processor for that feature if you really need it)
• Global transpose along with the Tuning floating tile.

This is the commit in question:

https://github.com/christophhart/HISE/commit/95d58ecd88d7fc45d05726377c98d7573cba559b

The other ones should be there.

Alright guys, more than 6 upvotes and I‘ll look into it

The thing with keyboard strokes is that they are terrible inconsistent across different DAWs so you better avoid shortcuts on plugins.

@Dalart said in I'll just leave this here:

is this sorta like the routing matrix thingy

It's the routing matrix on steroids

Sounds like something is weird with your project. Have you tried creating exporting just a sine wave generator and check whether the issue persists?

Enter VST3 in the search bar of the settings window

It's a development tool. Basically it lets you combine DSP building blocks in a more detailed manner than the current HISE module architecture. It's mostly for custom FX right now, but I have plans to extend it to voice level in order to build up custom sound generators.

A short teaser for the new upcoming feature:

Theres a box you need to tick in the settings to enable VST3 export.

Nah it‘s a glitch because JUCE changed something with the var to String conversion. Will take a look at it.

Looks like a MIDI channel routing issue (apart from the channel there can‘t be anything different than playing on the piano roll. Try changing the channel on your keyboard.

Yes that is correct FloatingTiles don‘t have a saveable state so the property is hidden.

My guess is that you have a UI control somewhere that shows the preset browser and is set to saveInPreset=true so that it fires its callback on preset load.

Yeah, I am afraid my current branch policy is inspired by the Spongebob episode "Opposite Day"

so there is some method to pick current sample map name?

Yes, there is Sampler.getCurrentSampleMapId()

Great video, Dave - there is also another advantage of loading the user preset you show before saving and that is that it keeps the Git commit history as clean as possible (otherwise it would be scattered with meaningless value changes).

The only thing I'd like to add to this is that it's a weird design decision to make a knob responsible for displaying the user preset name - for the sake of demonstration in this video it's certainly sufficient, but if people try to replicate this in their real projects it gets a bit messy.

The cleanest solution is using a timer and query the name periodically:

const var presetUpdater = Engine.createTimerObject();

presetUpdater.setTimerCallback(function()
{
    var text = Label1.get("text");
    var preset = Engine.getCurrentUserPresetName();
    
    if(preset == "")
        preset = "Gerald");
        
    // Check if it has changed before updating the text
    // in order to save a bit CPU.
    if(text != preset)
        Label1.set("text", preset);
});

// Check this 5 times per second.
presetUpdater.startTimer(200);

Normally, polling is not the smartest way of communication - the cleanest solution would be a callback onUserPresetChange() that you can use, but for this simple use case it is fine.