VST3's and Reaper - anyone getting any weird UI locking behaviour???

[Orvillain]

I notice when loading my latest plugin into Reaper, everything works and it generates sound. But the Reaper UI itself locks up, until I close the plugin UI. Anyone come across this before?

[HISEnberg]

@Orvillain Are you using the FFT or any other audio analyzer?

[Christoph Hart]

@Orvillain are you using a filter display? There was a weird issue that caused UI freezes on Cubase since a few commits.

I've fixed some performance issues with both the filter graphs and the FFT spectrum displays this week so make sure it still occurs with the latest commit.

[Orvillain]

Yep, I am using filter displays. My HISE version is:
cf957bdb5481d27615b064c4b5ae41e9d150e53b

Which is from the 22nd of Sept, but I can see there's some FFT spectrum stuff in later commits. I'll upgrade and see if it changes anything!

All working fine in Ableton Live btw. Seemed to be Reaper only.

[HISEnberg]

@Christoph-Hart I'm kind of curious how this works between DAWs, for me the UI locking behaviour happens with ProTools on my Mac. How is the data transmitted between the plugin, the SDK and the DAW. How is the behaviour so markedly different across the different DAW and OS setups? I.e. do you know where I can look to learn more about this topic?

[Christoph Hart]

@HISEnberg you can't. DAWs work in mysterious ways and there is no unified way how DAWs are supposed to handle their UI tasks, except for it obviously being rendered on the UI thread.

I found out about these issues because showing a filter graph in our plugin caused the Cubase Mixer to stop rendering its peak meters, curiously the plugin itself was still rendering fine, but it seemed to consume all resources allocated to UI rendering by Cubase so that their mixer fell short. How this is prioritised and what different DAWs do to mitigate this is completely opaque, but in this case it was just something in the HISE code that was unintentionally slowing down the rendering.

But make sure to check out the latest commits too, it might fix the problem you were having a few months ago.

[HISEnberg]

@Christoph-Hart For sure I'll give it a try and report back. I had my eye on those. I noticed by reducing the FFT buffer sizes (and all the buffers I was using for that matter) seemed to free up more resources, so I'll definitely give these fixes a chance and see if it helps. Thanks for the response!

[Orvillain]

@Christoph-Hart So I rebult on Windows using the latest dev, and all is fine.

However on MacOS I had a network that wouldn't compile. I rolled back to: eb4a726d3285033a0081cba078b60826abcb1e40

and it did compile.

So Windows fine. MacOS seems fine from a few commits ago. Latest fails on a particular network of mine - and it was a Dual Filter network, with graphs. So I'm guessing it is something to do with that.

[Christoph Hart]

@Orvillain what's the error message?

[Christoph Hart]

FYI, if it's failing here:

	operator bool() const
	{
        return (static_cast<bool>(*static_cast<const base_wrapper<Ts, Is>*>(this)) && ...);
	}

I'm already on it, there's some advanced meta template stuff that doesn't work out :)

[Orvillain]

@Christoph-Hart said in VST3's and Reaper - anyone getting any weird UI locking behaviour???:

FYI, if it's failing here:

	operator bool() const
	{
        return (static_cast<bool>(*static_cast<const base_wrapper<Ts, Is>*>(this)) && ...);
	}

I'm already on it, there's some advanced meta template stuff that doesn't work out :)

Hey Chris, for avoidance of doubt, whatever you did, fixed the issue! Cheers!

[It_Used]

@Orvillain apparently, the problem is in the Reaper itself, everything works fine for me on version 7.23.