Trying to create a random pitch detune effect in HISE

[LeeC]

@ustk Just had a search around thanks.

Wow, 2.50% max with the same snippet :astonished_face:

Like I said mine shows around 60% easily and if I duplicate the 'ScriptFX' I start to hear glitching and dropouts in the audio.

Appreciate that we aren't exactly comparing apples to apples here with the different systems etc but, I thought that my Mac Pro would be apple to handle a ton of instances of the ScriptFx in your snippet.

If anyone experiences similar or has any ideas what's going on please share.

Cheers

[LeeC]

Duplicated the ScriptFX a few times and we're up around 250%

[Christoph Hart]

Quick question: do you use the Debug build of HISE? That might explain the huge CPU difference.

I've loaded the snippet, takes 3,5% on my CPU, but it's a fairly powerful i9 notebook.

As long as your MacPro is >2010, there's clearly something wrong.

Also be aware that scriptnode patches which use frame-based processing are supposed to be compiled into a C++ module for production builds - if you compile it to C++ that particular patch shouldn't take more than 0.5% - even in the HISE CPU meter.

[LeeC]

Hey @Christoph-Hart,

Yes I'm using a debug version of HISE 2.1.0

Guess it's time for me to get latest.
Could you point to the right/best version to be using?

Appreciate the response

[Christoph Hart]

This post is deleted!

[Christoph Hart]

Ahh, never use the Debug build and complain about CPU :)

It contains tons of boilerplate code that is supposed to help during debugging. Just recompile HISE with the "Build for Profiling" menu command and it will optimise HISE to run about 50x - 80x faster (expect it to take about 3x longer to compile though).

[LeeC]

@Christoph-Hart great, thanks for testing!

Ok, so I first need to get off the debug version I'm using and then I need to learn how to compile scriptnode patches into C++ modules.

Thanks for steering me in the right direction (I've been spinning in circles all day on this one).

Can somebody please point me to the latest version of HISE to be using?

Not sure how I ended up on debug anyway to be honest but It's been working fine so avoided updating until now.

Cheers

[Christoph Hart]

You don't need to get a different code, just open the HISE XCode project again that you've compiled to the Debug version and tell Xcode to compile it in a different setting (Product -> Build -> Build for Profiling)

[LeeC]

@Christoph-Hart nice.

Thanks again

[LeeC]

Yep, recompiled with "Build fo Profiling" and the CPU performance is night and day!
Bye bye debug mode

BIG thanks for the heads up @Christoph-Hart and thanks @ustk for testing earlier