Posts made by Fortune

I don't know what is your purpose but Parametric eq is not for frequency modulation. It will cause clicks in most daws because eq nodes are not smoothed.

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?

Anyone can help please?

Does anyone know which OpenGL version is using Hise? OpenGL, OpenGL2 or OpenGL3?

First one is CPU oriented.
Version 2 and 3 is using GPU.

As far as I know, OpenGL has some issues with laggy GUI, also some users must update graphic drivers to open plugins. Also on board graphic cards have more issues with OpenGL.

Is it possible to use alternative renderers like Skia Render (Google) or Blender2D or something with less problem?

macOS deprecated OpenGL too by the way.

Maybe this is a dumb question. But I couldn't find a way to enable / disable nodes with a connected button in scriptnode.

Enable / Disable option is only on nodes themselves but can we use setAttribute for this?

@orange Wow! That's what exactly I am looking for! Thank you so much mate, Thank you so much for being very helpful!!!

Hi

One master knob controls 2 slave knobs. Slave knob target values are not llinear (like in the graphic below). So I used arrays for that.

Each blue line between each dots is linear itself. The general linear function is below. Is it possible to divide each master knob value interval and apply the equation below with respective array values?

Let's say;

• if Master knob (X1) = -2 >> Knob A (YA1)= 1.3 and Knob B (YB1)= -3.4

• if Master knob (X2) = -1 >> Knob A (YA2)= 5.2 and Knob B (YB2) = 2.2

• if master knob is between -2 and -1, the code applies the equation below and finds the linear point. But for each interval, X1, X2, YA1, YA2, YB1, YB2 values will be shifted within the values in the array. How can we implement that?

NOTE: in below equation, X is the current value of the Master Knob

Equation for each slave knob

Target Value = (((Y1)-(Y2))/((X1)-(X2))*X + ((Y1)-(((Y1)-(Y2))/((X1)-(X2))*X1)))

HiseSnippet 1103.3ocsV8tahbCD2KI6cGzR0cR4C8iVQ2GH5HnkPRZjRqBABTgx+PkzzJc5DxYWSvJFaztlzvEEo9g9bUkGg9Jz2f6Mncr2E1ENBAgTVjXWOy7aledF6wtouzkFDH8QVouXXeJx5asaMTn5VsKgIPMNRK3PeexP1modEQUF1mDDP8PVVq7yZKrRuJx77kCpP3DgKMVDBcoj4ROg0iohk1r7wLNuNwidAqWBq2tbCWonpjKG.rYEaGTeh6MjqomQzlkxFY8pZdLkzukhnnAHqUqH8F1pq7ODg1eIKfcEmpGTD0BbTn35RtmlwZonpcYbulil0AHvKMiyAqDlCVy9TlGar73bwaMJvwHRlOrRMO5ULI8bVb5YkfdqFRu2Y2x0m0WEqQysuwtgPQ86PfRPRZEZKJUvJ1UkfEBUgdjan08gAiQjaWGm73scb1X+rYz+fRQfBeKwGerPd0g3eBOB70TUUYu9RALH25FsqqQMIhJyEQk0GEmj3NkD.zQq+IAGaRjGXBNSPwcFHbULo.KEwlncgujmycD97PX3CnajMy8Yyj1Ux4T.0sz1WP7g3ztdjWxsw93rYdvDfmmGEBzpLgpJgyuBV0laFzHdFO4Lmn2cQ8ZqMsXaCACf4+G2bq73MKlGC0E3+s9z9yFxVsUFxe4XfEKTJOdmBN.d3iRE1CJrE18ovW5qvuYoBaCAz3.Gsm.Gr4deZL8mNkOu7H1jpwvCW5R3XlwK5wcj93bLHdN6iY3eDuC75CeXiPk2GFIbzyze8P3KsIOn+KQ0+LohdND3L2mIclGxfmVUmNyTWTMhS8moZcmJ+4ALmXPuqn9iVfMxPXK6j8Dre5dBIaY4FtnKggRQCAScdep3o5TfhVoB8LVIhUvWJSGiuKpiQKNyi5iXd515wqPQFVG2Jt6eiV.O7Zayl+oAuV4EGbkoACO+ZiiHJhtyWzDBlj8o9JlN+YcD8V3Hkv9fosOhFbiR1GRyi2aBhWr47cwQ8hxCGO3O+X4dLOONsoLfoKxIIG.teK3jvHYk+2O+WGzijvSH.bRDOpn2ATJaTfMsF0Upwj8MOa5M16OdWRd9akmHxuexH+kCdpYwZk8ncHC3g63mptMlWu5Yqbww9eRxqGcmjHu+wIn42OQTrCiR1nnbB4JJ2DDPxIGdYs1Ge14UZkHTucXhPgZTdT50XMNzZzWehIbtsza.mnl7vb8MXhTnSQIO0Texn.RcCSlReQNgeQo66raxTtcmMeSMC9Bagdo4az8kxZWqSG3HfXxtpc8e+k+xQneQNPwDWeJQ4yfEI1mMnWK35itTfIBAkq63ZkR2aLbridrNyzhJ7LC9O3IRYQ8XqHkEGoD0i35Ka6F1RSeir2Xj.bRXtXZZXuMLFWbTuLaamBNHX6GqsqqNUrIv8YiYqk.Sok.y1KAlcVBL6tDX9gk.ydyEi9N5GNPI6EtMADzrl4LEKqZBBrJyrhD8+zMao4F

@ustk Like in the below image, the dynamics fx has always edgy character. No matter if you reduce the ratio or something else. For the soft behaviour there is a "Knee Width" parameter. And this parameter is independent from attack or ratio. Really really hard stuff to do with this simple dynamics module / node.

@dustbro @ustk Thank you guys! Very useful information.

I also searched the knee factor too. I think Dynamics FX has a very Hard knee. Dynamics node and module uses simple envelope. In SimpleEnvelope.cpp there is

void EnvelopeDetector::setCoef( void )
	{
		coef_ = exp( -1000.0 / ( ms_ * sampleRate_ ) );
	}

Maybe this exponential value is related to knee. So faster detection, harder response. Slower detection softer response?

Also in Dynamics.node there are envelope settings:

envelope_follower::envelope_follower() :
	envelope(20.0, 50.0)

The release time of the compressor is maximum 250 ms.

Is it possible to set it longer like 1000, 2000, 3000 ms?

I am sure lot's of people are asking this. When will the scriptode rewrite finish? I have serious scriptnode projects but since the current scriptnode branch has issues I can't use. Also new rewritten version is more proper way to me.

Fingers crossed and we are looking forward to see the new, updated rewritten scriptnode. When will it be finished? @Christoph-Hart

@d-healey Same here like @dustbro & @Natan "GraphicRendering": true doesn't make the opengl combobox show up in CusotomSettings floating tile.

I am also confused that, in order to make OpenGl enable:

Is HISE_USE_OPENGL_FOR_PLUGIN=1 enough?
Or should I do HISE_USE_OPENGL_FOR_PLUGIN=1 and "GraphicRendering": true both?

@Lunacy-Audio said in HISE HEAVY ON GPU PROCESSING?:

I think you need to add a Settings Floating Tile and set the content data like this:

const var settingsEngineTile = Content.getComponent("settings_Engine_Tile");
const var isPlugin = Engine.isPlugin();
const var tileData = {
            "Type": "CustomSettings",
            "Driver": !isPlugin,
            "Device": !isPlugin,
            "Output": !isPlugin,
            "BufferSize": !isPlugin,
            "SampleRate": !isPlugin,
            "GlobalBPM": false,
            "StreamingMode": true,
            "DebugMode": false,
            "GraphicRendering": true,
            "ScaleFactor": true,
            "SustainCC": false,
            "ClearMidiCC": true,
            "SampleLocation": true,
            "ScaleFactorList": [
                0.5,
                0.75,
                1,
                1.25,
                1.5,
                2
            ]
        };

settingsEngineTile.setContentData(tileData);

graphicRendering is the OpenGL combobox that allows the user to toggle it on/off.

Oh I see Thank you.
So if I use this floating tile I won't need to use HISE_USE_OPENGL_FOR_PLUGIN=1 in extra definitions menu, right?
Also there is no combobox for Graphic Rendering even when I make it true.

@Lunacy-Audio So first I need to set HISE_USE_OPENGL_FOR_PLUGIN=1 in extra definitions menu.

And also must use in Settings Floating Tile?

Also I can't see use open gl option in Custom Settings Floating Tile

@Lunacy-Audio Very interesting info, thank you so much.

So maybe it is better to compile with open gl and without open gl separately, right?

@Lunacy-Audio said in HISE HEAVY ON GPU PROCESSING?:

@DanH Be wary of the OpenGL option. It's a naughty little beast and will screw up a lot of things if you're not careful. It's better to optimize your GUI first by removing unnecessary hover and drag callbacks from panels, etc.

Try optimizing the code as well: https://forum.hise.audio/topic/79/scripting-best-practices/2

So is it possible that enabling open gl can cause issues? What have you experienced so far? Can you please give an example or a little bit info about it please?

@tomekslesicki I'm afraid that working crossover bands are not available in Hise yet.
Scriptnode Linkwitz Riley Filter has a phase issue and not working properly.

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

@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

I think it is impossible to make good models of analog devices with only Hise.

Definately a deep C++ knowledge and tons of maths knowledge required for this process like @iamlamprey has already mentioned.

Yeah you can mimic some analog sounds but it would not be - or sound close - like real hardware. Only hise is not enough definately. Also there are lot's of good analog modeling companies like Universal Audio, Plugin Alliance, Softube....etc. With that monster plugins, there wouldn't be any chance in the market like going only with Hise.

I will suggest learn Hise deeply. Learn C++ deeply. Learn Math stuff and DSP deeply. Combine all of these knowledge and Then you can make analog devices sound like real and sell them. If you are on a serious business of course.