@MikeB Thanks! It worked now! Apparently, I had to make sure all steps for enabling IPP are done right.

@DabDab @d-healey
I see, thank you!

@ustk Superb.. That's what I wanted. I got stuck in it.

@Fortune I’ll keep checking tomorrow. I think I saw it again today but couldn’t be 100% sure as it’s such a small movement 😂

@tomekslesicki I am trying to do this now using a global modulator container with an lfo , then in scriptnode I have a global_receive but how can I send the global modulator container lfo to the global receive ?

The global send/receive does state " Send the sginal anywhere in HISE " but it seems like its only a send /receive within scriptnode ?

EDIT : the Global_mod node will receive the LFO from global modulator !

@d-healey yeah I hate that middle position property: -1 is a terrible default value, that‘s why scriptnode uses a skew factor as property which defaults to linear (=1).

@Fortune That will just modulate the speed , I would just like to control the speed with a synced clock.

@d-healey That did it! 😎
So Hise certainly was more permissive before...

@DabDab laf.loadImage()

@d-healey Got it.

Thanks everyone for the clarification! Based on the general consensus I thought I'd successfully exported a universal binary (I had 2 versions of Xcode on my Big Sur computer, 10.3 and 13.2.1) and didn't have a way to check until I recently borrowed a fresh, Rosetta-less M1 laptop and it didn't work. In lieu of holding the laptop hostage, I looked into how to check on any Mac via Terminal:

Export plugin Right click > "Show package contents" > Contents > MacOS > [plugin executable file] Type "lipo -archs " into Terminal and drag the executable in. Terminal returns "x86_64 arm64" if it's a universal binary and "x86_64" if it's Intel only.

Mine were Intel only at first because HISE was using the older version of Xcode to export (I'm guessing because that's what I used to compile HISE itself), so I just had to open the autogenerated Xcode project in the newer Xcode version and export from there. Everything was already set up correctly in the file, so I assume you would not have these issues if your whole setup was not based on an older version of Xcode.

@Christoph-Hart Nice feature :)

@Christoph-Hart okay, thank you for the explanation. I'll change this in my project after i compiled the latest commit for the converter node. 😉

@DabDab iirc you'll need to create all the buttons etc that the script refers to as well

Link Preview Image HISE | Docs

favicon

(docs.hise.audio)

@Christoph-Hart Okay, I see. Too bad but I see the time-sucking black hole in re-inventing the wheel for you, especially for such a unique computing environment. Already lots of time spend making new features and fixing bugs. Not worth it.

@Christoph-Hart Thanks for the clarification!

The CPUs instruction set for SIMD seems to be a big factor for the actual gains. I found a nice thesis by a guy named Anthony Blake called "Computing the fast Fourier transform on SIMD microprocessors", including lots of comparisons from quite recent machines (i7-2600, around 7yrs old "only":=). It included a high-performance FFT library called SFFT / Spiral, vDSP, Intel IPP and FFW3: (page 140 in pdf)

https://www.cs.waikato.ac.nz/~ihw/PhD_theses/Anthony_Blake.pdf

According to the benchmarks, another library called SFFT (Sparse Fast Fourier Transform) was used that partially trashed the others (FFW3/vDSP/IPP) around the 4-64 bit sets in lots of tests. But according to the Spiral SFFT page:

the algorithm can be faster than modern FFT libraries. However, the reference implementation is not optimized for modern hardware features such as the cache hierarchy, vector instruction sets, or multithreading.

Too bad, would have loved to stare at some more graphs and then going "I wish I understood the context". :) It is now being used in 3D FFT to analyze the trajectories of gravitational pulls or ... well space n shit 😁

@d-healey Thanks for the video, I saw it yesterday and it is really good. He explains it perfectly.

@d-healey Hahaha, sure - i already did so! :grinning_face_with_sweat:
But sometimes it's hard to find the correct answers without asking, when you have absolutely no clue, where to search for it... ;-)

@Lindon @DanH @BWSounds ah I didn't see the other thread, thanks 👍

bump bump - anyone got any ideas? If not I will launch a feature request...