Avoids dependency on LDC 1.28/1.29 on macOS 10.12 to 10.14

[p0nce]

We have installed InnerPitch FREE from auburnsounds as AU, VST2 and
VST3.

Only the AU plugin appears in the DAW and not the VST2 and VST3
versions.

The message then always appears that the Audio Unit V2 plugin cannot be
opened.

We've tried a number of things, but nothing changes.

The operating system is OS Mojave version 10.14.6.

DAW is Ableton Live 11 Suite version 11.3.11.

Do you have any help?

[p0nce]

Sounds a bit like #800

[p0nce]

I'm on macOS 10.14.6 with Ableton Live 10. All steps can be reproduced with Inner Pitch 1.0.0, only AU displayed. Same message on opening.

• [x] try to build Inner Pitch with LDC 1.33 and reproduce the same issue locally on Mojave => So what happens: when plugin is built in debug mode with DUB and LDC 1.33 on Mojave x86_64,

  • VST still not listed in Ableton (symbols are here)???
  • VST can be loaded by process
  • AU listed and pass auvaltool and Logic validation (EDIT: OK this was Wren file loading a non existing file)
  • AU load crash Ableton and Logic (EDIT: OK this was Wren file loading a non existing file)
  • list and load VST3 and AU, not VST after rescan. Annoying, since only VST won't crash on resize and gets presets, but well those are other bugs.

• [x] try to build Inner Pitch with former preferred LDC on Sonoma (since we've updated :()

  • current working hypothesis is that the right LDC to use is LDC 1.28.0

[p0nce]

Inner Pitch rebuilt with LDC 1.28 doesn't exhibit the Mojave issue, we should get back 10.13 and 10.14 compat that way. My guess is that this was probably a newer LDC built with newer Xcode and not the right flags, so not supporting older macOS. 1.28 strongly recommended for now on on Dplug plug-in to avoid this issue The real cutoff compiler is somewhere between 1.29 and 1.33, only more testing will tell. 4 customers reported that bug in 6 days so that's very common bug.

[p0nce]

Fixed for the customers

[p0nce]

Need proper fix.

Note: the new --compiler-x86_64 allows to choose a --compiler just for the x86_64 binaries.

[p0nce]

Testing Lens as VST3 in Mojave:

• [x] LDC 1.35 Universal package => Live 10 on Mojave doesn't scan the VST3
• [x] LDC 1.31 Universal package => basically same behaviour than 1.35 and 1.30
• [x] LDC 1.30 Universal package => crash Live 10 on Mojave (if scanned in earlier version), otherwise
• [x] LDC 1.29 x86_64 package => same as 1.28, no issue
• [x] LDC 1.28 x86_64 package => scans, instantiates, no issue

mmmm, is there maybe something special to do when using a Universal LDC package?

• [x] Possible to use the x86_64 package with the newer >= 1.30 compilers?
  • [x] 1.30 => yes
  • [x] 1.31 => yes
  • [x] 1.35 => yes

Note: all of them after >=1.30 get the following:

ld: warning: object file (/Users/guill/Desktop/compilers/ldc2-1.35.0-osx-x86_64/lib/libphobos2-ldc.a(inftrees.c.o)) was built for newer macOS version (10.12) than being linked (10.10)

Meaning we may loose more than 10.12 to 10.14 with that.

• [x] is that warning a problem on 10.14? => no, but probably prevents even more compatibility. Might explain why some people report software working in 10.10 and 10.11 sometimes.

• [x] Possible to use a mixture of compilers for having top codegen on arm64?

  • [x] 1.35 arm64 + 1.28.1 x86_64 =>yup, it works everywhere, in Rosetta, arm64, and native x86_64, from 10.14 to Sonoma.

  • [x] We need a Wiki page for maximum macOS compatibility advice.

[p0nce]

Sum up in https://github.com/AuburnSounds/Dplug/wiki/macOS-Compatibility-Advice