4 ms·
I work for an audio company. Indeed, that's unfair. Unlike the PPC to Intel transition. This time it's a little easier since most modern toolsets require much l
by rock_artist 6y ago
I work for an audio company.
Indeed, that's unfair.
Unlike the PPC to Intel transition. This time it's a little easier since most modern toolsets require much less changes in code.
Having said that some consideration to keep in mind:
- audio code needs to be optimized for real time thread constrains.
Many optimizations usually made by vectorizing rather than threading that would've lead to locks and synchronization not always possible for real-time processing.
So not all SIMD code can be compiled just by changing a flag.
- machine specific code. While rare. Some companies still got such code for various reasons. And needs more complex transition.
- Not all companies were able to obtain DTK. We for example, got our first M1 machine 3 weeks ago.
- Backward support. While we'd like to have universal builds, musicians use their systems for years. We still support 10.7.
With Big Sur Apple seems to break SHA1 signs making builds from Big Sur work reliably only on 10.11 or newer. (The first release to support SHA256 codesigns)
- some companies already got Universal builds.
REAPER, FabFilter and Adobe Audition are few I can remember.
Keep in mind electron, docker, Homebrew and even other "devs" tools still not fully Apple Silicon ready.
So indeed the above statement is unfair for a small industry (vs finance or other software markets)
- Wowfunhappy 6y ago> With Big Sur Apple seems to break SHA1 signs making builds from Big Sur work reliably only on 10.11 or newer. (The first release to support SHA256 codesigns) Affinity Photo is an Arm/Intel universal binary that’s also compatible with OS X 10.9. Maybe look into what they’re doing?
- rock_artist 6y agoI guess they're building on Catalina as we expect to do so until Apple or us/some other devs would find a way to use prdocutsign/codesign with backward compatibility on Big Sur
- marcan_42 6y agoI'm not saying I expect it to be done now, I'm saying I expect a good subset of audio companies to still be dragging their feet a year from now, judging by history. Yours may not be one of those :-)
- PaulDavisThe1st 6y agoWe've already released a "test" build of Ardour for M1. Because we already support Linux on ARM, it was relatively trivial - the main work was getting our build stack to compile first. Other than that, it just works. The same codebase supports Linux, Windows and macOS/OSX back to 10.8 and PPC.
- unixhero 6y agoBravo, love Ardour.
- mrpippy 6y agoI believe Xcode 12 can only target back to 10.9. (Xcode throws an error when you try to go older, I think the command-line tools can still go back farther though)
- rock_artist 6y ago1. Also 10.9 needs SHA1. 2. We've been able to input down to 10.7 and didn't see any issues. The issue is productsign/codesign linking Security.framework which I assume changed.
- emcq 6y agoCheck out sse2neon as a way to substitute your x86 SIMD instrinsics for ARM neon. Perf was good enough to ship in one of the past projects I worked with.
- rock_artist 6y agoThanks! Interesting. I'll look it up. What I know one of our devs didn't find equivalent to is ippsPowx_32fc_A11
- fay59 6y agoYou can produce two signed binaries, one for <10.11 that is signed with a SHA-1 and one for newer systems that is signed with SHA-256. Your update framework would have to know which one to pull, but that seems surmountable.