@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 | HISE | Project Settings

The properties for your project

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...

@ulrik I have a glide script, but the two don't work together. In fact I find the Arp doesn't work with any other midi scripts, it just does its own thing.

@ulrik Thanks - yes worked on my other machine too, weird! Got round it by using fillRoundedRectangle with 0 corners...

@Jlev777 yes currently the granulator is in a module that is not part of the DLL compilation codebase, but I actually don't see a reason why this is the case apart from "I didn't bother before"

I've moved the code and removed that limitation so now you should be able to compile it.

@Lindon said in Setting up my M1 mac for Universal binary compiles....:

What OS do I need to be running? - I'm guessing its coming with V12(Monterey)

Traditionally the OS that your new mac comes with is the lowest macOS version that you can run, sadly. So if there is a need for backwards compatibility (when is there not?) that may present issues. Virtualization for pure testing can of course be done in VMWare Fusion including sound and drivers actually, but building/compiling via virtualized macOS is ill advised, I tried :(

What version of Xcode do I need (bearing in mind that there's at least one of the later versions that wont work with HISE)

Xcode can most likely be run in a few lower versions than the latest, even though the OS is newer and not explicitly supported. Reference the Xcode versions easily here:

Xcode Releases

More than you ever wanted to know™

favicon

xcodereleases.com (xcodereleases.com)

Nice overview there. But do download from your account from the link that @orange left above.

@Casey-Kolb Big Leagues!

@ulrik Superb, that does the trick!