@Natan It depends in which script you are using it.

I am using it in the main interface script, it works..

https://forum.hise.audio/topic/79/scripting-best-practices

Updated. Added "else if" statements.

@Steve-Mohican You can achieve the sample delay with the Simple Gain unit. But we need to convert milliseconds to samples first.

Let's look at the principles. For example if we have 2 milliseconds delay in 44.1 kHz, the sample delay would be:

2 x 44.1 = 88.2 samples

If the sample rate was 96 kHz, sample delay would be:

2 x 96 = 192 samples

Acording to this equation you need to get the sample rate with Engine.getSampleRate() and calculate the ms delay amount. In your case since you need 4 samples delay, your equation will be;

4 / (Engine.getSampleRate())/1000

So you need to use below loop in a Simple Gain unit.

   if Over sampling is active
     {
        SimpleGain.setAttribute(SimpleGain.Delay, 0);
     }
        
    if Over sampling is not active
     {
        SimpleGain.setAttribute(SimpleGain.Delay, (4 / ((Engine.getSampleRate())/1000)));
     }        

NOTE: / 1000 is the conversion rate from Hz to kHz

@Natan For variable ranges, this can help: https://forum.hise.audio/topic/1036/lord-of-the-knobs/10

@Lorrislehorse Have you tried File > Open Recent Archive ?

@Natan Here you go. Console.print lines are for monitoring, you can comment out these lines

HiseSnippet 933.3ocuV0saSjCE1SZ8BIKEARHtdTkPJcWHZB+KPnlLosnH1VhHrU6Ufb83zXUO1i73AHfPhmEtCtfK3kga4Q.dBfime5LsDBYi1tSjhFeNmuy74iO+3AZEkEGqzHm5OdRDC4bF7vIRy3diIbIp+FHmyh2lDaXZ2LQ9ShHwwr.jiyR22Jvo9xnzmurtOQPjTVoHDZWEmx9KdH2TJcPmGvEhsHArGyCqX806zmpj8TBUBvmkvdnHB8.x9rcHVypgQN+1lAbiROzPLrXjyx9pfICGqdtLy9c4w78DL6h1ngfixDukRDXYrUJp2XtHXPw9NFAdYPYTXornvEvayC3GJuLZbtTEtkHpFObpMK50tJ87le54TgdKmQuyiGR07HSoFK29cbeIbPMh.GAUoUlsnZuqFtmBrPZZERNfskFVbHhl2zy6xt2vyas6tRC6O3nH139Lh18AR0d44.2ysvC6yL8TgQJIrn4pklrpE+Qw1clv5NED9yDg+pEbjKEbIycThjZ3JoqRVRDKdsRzjV.9xf6EIr0VowqVogK7j90aEyL6Zk2LU6e30ps06E58+Q8WsPe0+guVrRvZEo4Ezzs6cbW08Oy+L6W3l0JfOMH9kP7OFjWmtm+0geKgy268HBwdPITyoDWrtrRbaGkg8PYy0Z7pF0a75FtGW0nQSUWtyDL8TUaqu0yBXSYR3dLcwQSggPh9Qqjv+7JopE5zrnSECUx9Rt4gQL4Oq9BkGRgJskxYE7lIsN6r40YCE7.lFwCr8GKCknTVm2.6MW3CeZczb3gSk5gtGAL58e8s+K.6ebvebcze2eChgX6WjugfMYDSa313myFrmAMhy5dTGuAK9.iJJcGmmDAtd91yu3vF1thNSJ6d+jNgp..+Ew6nzgDA+krfALME7MzBGEmLZD+E1CgKgB4AAB1.UL2lMT5hOaCAyAeJhfkT4yjJToi7+ap3WgJcR9umJ+3D.XNjJHQPLGc3jchbtBqOpNEv1oWB9dR0I1mHSrlW5dd7.tgNd57s1T3KjbeRy274+qf2bzHF0TR1kwa8Om7C6QORkX3x82lXz17B7NIgCgqCQY.SjRlv1KzolsqU1ZO6ZajYHSFjt3avStx110N4JaWnDERnZ0SoYMar2v3zoR.NISunUc3FevZ21EcYvXuVd17S9SoTan3J.2mNlqt.Xt1Bf45K.lar.Xt4Bf4VK.laOSL16b1MwnByJS.AC1LsauiylRBjkklQh9dMZyCT

The last NVidia graphics card was used in a mac computer, almost 10 years ago

@d-healey said in Multi Instance DAW Crash Issue Guide:

This sounds fishy to me. Setting attributes shouldn't be causing any issues. I suspect there are other problems with the scripts.

It's been covered here by @Christoph-Hart befrore: https://forum.hise.audio/topic/2826/debugging-with-reaper/25

You can use as many setAttributes as you can, it's not a problem on most systems. But the issue is "Multi Instance DAW Crash" in "Some Systems".

That doesn't mean it happens in all computers. But if you see this in a computer, it will do that crash in all DAWs You know what: while I haven't seen any multi instance crash in my 7 years old laptop, some users were repoting this issue to me. Honestly I couldn't replicate it. Then I got a new Intel 10th generation i9, 128GB RAM, 12GB NVidia 2080Ti computer, then guess what: it crashes for 5 plugins Same plugin, new system.

Are you setting attributes only in deferred scripts?

Yeah, I am using it in main interface script only. But the issue happens also with the plugin that uses only One Timer Object (100ms - on preset label only). Whole plugin is a Parametric eq, ShapeFX and setAttributes. Nothing more. I can open 20 instances in old pc, but crash for 5 instances in new one Crash reporting beta testers see the multi instance crash too.

This is more interesting, when the deferring callbacks are disabled, sometimes crash reduces

Are you setting attributes in MIDI callbacks or timers?

No.

@LeeC said in Multi Instance DAW Crash Issue Guide:

@orange @Christoph-Hart
I know it depends, but is there a ballpark number for the amount of setAttributes we should be using simultaneously?

Also, would using the showControl instead of set("visible",value); to toggle visibility of components help to avoid crashes aswell?

I haven't seen any issues yet with using too many showControl or set("visible")... stuff. For multi-instance crash you need to make experiments with beta testers.

@dustbro said in Multi Instance DAW Crash Issue Guide:

@orange said in Multi Instance DAW Crash Issue Guide:

Number one cause is the amount of used setAttribute APIs

@orange @Christoph-Hart does this also include setValue()? If not, I might use scripts to set the value of panels, and then us the Panel Property Editor to assign Processor/Parameter IDs.
Can panels even do that?...

Since generally I use setAttributes, I haven't made experiments with setValue() & Panels.

But setValue should be ok I think.