@Orvillain yeah that‘s just a glitch of the popup interface of the editor and I never looked at one long enough to bother fixing it.

@HISEnberg said in FFT Analyser Settings...:

do you recall what edits to the source code you made to get these properties to stick?

As @sinewavekid said, you need to put it in your script.

It's a bit long winded because you have to get the display buffer, but wrap it in a function and it keeps it tidy.

@ustk Confirmed on Ventura and Windows 11.

Oopsies, there was indeed a typo that caused the step size to be 2 instead of 1, so every even value was skipped. This only affected dragging operations, so there is no preset backwards compatibility issue.

It's fixed now.

@Natan Is this solved yet? Since I got the same problem with my Arp that is doesn't stop when the DAW is stopped.

Think I've solved it.

@Christoph-Hart This is set to 11 in develop. I've changed in to 10.7 and now it's running on Catalina.

b91dabbb-64b6-4fad-82bc-66eef8ae5d14-image.png

Is anyone else experiencing this? I even tried the exported version 4.0.0 of HISE and ran into the same issue. I tested on Windows as well, same problem.

I also tested with the 3.6.2 release, with Loris installed in the HISE app data folder, and got the same issue. That’s strange.. maybe I'm doing something wrong?

This are my settings when trying to export:

Screenshot 2025-08-15 at 7.06.57 PM.png

@aaronventure said in Active CPU profiling not working:

@Christoph-Hart I think he's missing the CPU percentages on individual nodes (which were quite nice, frankly).

yes that is what i meant - sorry for not being more clear

@Christoph-Hart That it, thanks.

@Christoph-Hart Yep, that has fixed it, thanks!!

@Christoph-Hart Thanks :)
I was using "Ctrl+D" after finding the first occurrence, but this is quicker.
I was hoping that there was search and replace feature that worked across the external .js files as well. Doing a big cleanup at the moment so looking for ways to correct older names I had for certain data labels which may be used in multiple scripts.

@Christoph-Hart

Seems fixed, thank you!

@Christoph-Hart oh yeah a buffer why haven’t I thought about that… I’ll try.
My array is only made of numbers, but I’ll check in case an undefined is hiding somewhere…

@Christoph-Hart Correct, but it should match the number of groups the user has set, which is the previous behaviour - I can do this but I figured you'd changed it for a reason.