ARM/Intel Universal Binary... how?
-
Hmm, that's reasonable. Are you actually hitting dropouts? because the debug log warnings are very verbose and a occasional peak of 10% CPU usage isn't too critical.
-
@Christoph-Hart good question. Gonna do more testing today
-
So it is impossible to make an IPP enabled universal binary (both for M1 & Intel) with a M1 mac, right?
But we can do that with an intel mac?
-
@orange I'm not sure. I gotta fire up my Intel Mac and see what's up. Also ran into some weirdness with Packages on my M1 so it looks like I gotta make my installers with the intel mac as well.
Dan Korneff - Producer / Mixer / Audio Nerd
-
@dustbro It's interesting that VST3 files (turns into folders) can be a problem with Packages in M1 macs.
-
@dustbro Have you checked M1 universal binary inside the Intel mac?
Is develop branch successful for M1?
-
@orange said in ARM/Intel Universal Binary... how?:
Have you checked M1 universal binary inside the Intel mac?
Is develop branch successful for M1?I haven't yet. I'll probably be ready to do more testing in about a week.
-
I hope we will soon be able to use XCode 12.2 to 12.4 from non OS11 compatible machines, so we can export Universal Binaries from Intel.
Otherwise, the only solution would be to buy an OS11 computer (with or without M1, but you know how it is...) -
@dustbro hey, which new_layout commit you use because I can't force my setup to even compile app
-
@arminh the one from about 10 days ago
-
@dustbro I'm out of ideas ...
I tried compile this commit
https://github.com/christophhart/HISE/tree/27a94f3e11615fcfa793a9ec58ac531a75de5c7fBut I'm getting a lot of issues
-
Is it M1 or Intel mac?
Which XCode version are you using?
IPP enabled? -
M1, Xcode 13, IPP enabled
-
-
@dustbro ok I amble to build Hise, even with IPP flag, but I have error building plugin with IPP. I assume that there's no option to build intel x64 with app?
-
@arminh said in ARM/Intel Universal Binary... how?:
I have error building plugin with IPP
I'm unable to build a plugin from the latest commit as well.
Dan Korneff - Producer / Mixer / Audio Nerd
-
@Christoph-Hart Can you please clearify this situation?
- A couple of months ago you've declared that Hise can export M1 plugins but is Hise compatible?
- If yes, which macOS version do you suggest?
- Which XCode version do you suggest?
- How can we build universal binaries with IPP?
A lot of people is struggling with this but we haven't seen any directions from you about this.
Please help, or fix it. I think this is much more an emergency "to do" thing rather than "new layout".
-
A couple of months ago you've declared that Hise can export M1 plugins but is Hise compatible?
Exported plugins are native M1 compatible, but HISE isn't. The SNEX JIT compiler requires to be run under Rossetta and I will only start working on an native ARM JIT compiler when Apple announces the end of Rossetta and not a single day earlier.
If yes, which macOS version do you suggest?
I'm compiling on my MacBook Air M1 with Big Sur and Xcode 12.4.
How can we build universal binaries with IPP?
I think I will remove IPP from macOS builds altogether in the foreseeable future. The performance difference to Apples VDSP framework is negligible, so just disable IPP when you build universal binaries.
-
@christoph-hart said in ARM/Intel Universal Binary... how?:
Thank you for clearifying.
I think I will remove IPP from macOS builds altogether in the foreseeable future. The performance difference to Apples VDSP framework is negligible, so just disable IPP when you build universal binaries.
True for M1 systems but IPP is very important for intel systems. I think universal binary support would be needed at least 4-5 years more.
So for now we can't make universal binaries right? Must be individual for intel and M1? Can you add this feature please?
-
@dustbro said in ARM/Intel Universal Binary... how?:
@Christoph-Hart said in ARM/Intel Universal Binary... how?:
the apple stuff is fast enough
Maybe not? Checking out the ARM compiled plugin with a convolution plugin is giving me warnings in debug mode.
### PerformanceWarning -Time: **0.70** /CallbackIndex: **60** -Location: 'Convolution::ConvolutionRendering' -Voice Amount: **0** -Limit: '10.0%' Avg: '2.07%', Peak: '11.0%'Guys how can we see these debug reports?
I enabled debug mode before plugin compilation, but after building I can't see anything.
