Merry Christmas to everyone

@iamlamprey said in How to Emulate Hardware or Software Instruments/FX in HISE:

@Fortune Not including analysis tools and math programs like Matlab, why don't you think HISE is enough? IIRC the JIT stuff lets you work directly on the audio buffer with C++ (or something close enough to it).

For analysis tools, of course these are a must to have, I didn't even need to mention this

Hise is sooo good and sweet. But I am just saying that, analog models can't be done with ONLY Hise. Hise is just a one tool to must have. There are other things to do like C++, maths...etc that I mentioned for analog modeling

Will there be a some kind of drag n drop (vertical or horizontal) plugin player in the future?
For example like below:

@dustbro For example, if the delay time of the plugin is 500 samples; just insert this code into the begining of the on init script;

Engine.setLatencySamples(500);

With this way, plugin reports delay compensation to the DAW in the very begining of the initialization.

I am using it on fx plugins it doesn't give errors. But it doesn't work in almost all DAWs.

@Christoph-Hart Yes definately persists.

Just a quick tip ; You can check the latency and phase cancellation with that way very quickly (also known as Null Test);

• Open your DAW, Insert an audio loop or sample in a track.
• Duplicate this track and invert the phase of the second track.
• When you play both of two tracks simultaneously you will hear pure silence because two tracks cancel each other. That's what we expect.
• Then insert the Hise made plugin into just one track (no matter phase inverted or normal). Just let one track's fx slot be empty, other track's slot with Hise made plugin.
• If the plugin hasn't phase cancellation problem (or latency), you should still hear pure silence too. If you hear silence, activate all of the EQ nodes, and saturation unit, twak them a little bit for checking if there is some phase issue or not. But since the plugin has a latency, you will hear some audio with phasing issue.

Let me know if there is something I can do. Best regards

@orange Sounds great, Looks great. Congrats.
You are one of the best developers in this Hise community!

Can we change knob image strips with a button? When we do that, will it crash on a compiled plugin?

Thank you man for this great guide Amazingly useful!!!!

Like you've suggested, for test purpose I removed some setattributes in my code and the crash issue almost fixed interestingly. Why is this happenning?

@Tania-Ghosh said in How to Emulate Hardware or Software Instruments/FX in HISE:

@iamlamprey @Lindon @Fortune ... I have one question.... For more customization do I need to write own C++ DSP code? if so, then how to integrate my custom DSP Modules with HISE? HISE works with Java script... I can do basic stuffs with JUCE or WDL but it is very daunting to work entirely with JUCE/WDL/RackAFX and make a complete plugins with JUCE only(without HISE).. I love HISE so much because of it's API and JAVASCRIPT....What steps do I need to follow to overcome this type of DSP C++ integrated approach?.. I have seen @orange has made some emulation stuffs with HISE using C++.

Very simple, just learn and test There are lots of sources for learning this oceanic knowledge on the internet.

https://www.musicdsp.org/en/latest/ is one of them to make a good start.

@Christoph-Hart I understand, thank you!

Can we change GUI height with a button?
When we do that, will it crash on a compiled plugin?

Content.makeFrontInterface(600, 500);

const var Button1 = Content.getComponent("Button1");

inline function onButton1Control(component, value)
{
	if(value)
	    Content.makeFrontInterface(600, 500);
	else    
	    Content.makeFrontInterface(600, 200);
};

Content.getComponent("Button1").setControlCallback(onButton1Control);

@d-healey said in Changing knob image strips with a button:

It won't work because only images that are used on the interface are available in the compiled plugin.

I expected something like this, than you for the information

Can we change knob image strips with a button? When we do that, will it crash on a compiled plugin?

@Christoph-Hart said in SOUL:

I'm still waiting for @fortune to chime in about new feature additions

Ahahahaha

No man, I really love your art and appreciate your effort so much.
But sometimes I really need to criticize, because in my mind, this beautiful art, HISE, must be perfect. There shouldn't be any deficiencies in HISE.

I hope it makes sense.

Looks cool.

But is this feature necessary, when there are really serious bugs that need to be fixed immediately in Hise? I think No

Bug fixes first please...

@orange said in Solution for Slow GUI Performance on Macs (mostly with Radeon GPU):

There is s laggy and slow GUI element performance issue on some mac's (especially with Radeon GPU) with major DAWs like Logic Pro X, Cubase...etc.

Here is the solution:

Change display color settings to "sRGB IEC61966-2.1"

That solves the issue

https://www.logicprohelp.com/forum/viewtopic.php?t=149736

You're the king! Thank you!!!

@Natan No definately it has an audible phase problem, especially in the low frequencies. If you can't you hear it, you can see it in a frequency analyser.

@Christoph-Hart I hope new scriptnode will have a working Linkwitz Riley filter for this splitting stuff. Current scriptnode's Linkwitz Riley filter is broke and making phase effect, it's been reported a couple of times before.

Remarkablex example is the best solution for now, at least works much more better than scriptnode Linkwitz Riley filter. But even that one gives a little bit phase effect too.

Because of that, it is impossible to make a proper bandsplit with Hise for now.

@Christoph-Hart said in snex :

Upload an example then I take a look. All my plugins work fine with multiple instances.

I will prepare a minimal example.

But even if I prepare that, it will probably work in your system (like it works in one of my systems, but the other system crashes). because this issue happens on some systems, so replicating could be difficult for you. I can give these information and I think it will help you to find out:

In my project, there are approx. 15 setAttributes in a single inline function. Totally 6 different inline functions (each one have approx. 15 setAttributes)

The problem happens when opening the daw project again, while adding instances, there is no problem. Open the plugins in daw, save project, close the daw. Then try to open the daw again, the daw crashes.

• 4 plugin instance, daw project can't be opened, crash!
• One plugin instance, daw project opens without any crash, no problem.
• 20 plugin instance, daw project opens without any crash, interesting, but no problem.
• Issue happens on Windows
• Not only Cubase 10, 11. It also happens in Reaper, Studio One 3, 4, 5and in other daws..
• The issue is very random. In one Windows system, daw project can be opened without any crashes. But in another system it can't be opened. Intel i5, i7, i9 doesn't matter. NVidia or AMD Graphic card doesn't matter.
• Deferring Callback enabled. Enabling OpenGL causes much more crashes.

I think the cause is Audio UI thread, that Moody Camels queue makes a hammering which is also mentioned in forum. And it is definately about Hise, not the project.

This issue MUST BE SOLVED, it's not a simple thing to be passing off like FL Studio delay compensation issue (I also think it is very important too).