As with any new macOS, Apple removes old code, some plug-ins might break to some extent. - if you see anything let us know! we’ll do our best to resolve that.
Beta/pre-release software is known to change. Each new beta might break/fix/change things.
We’ll do our best to keep this post up-to-date and report if we see any change in behavior.
As always! We suggest to avoid using such beta as a daily driver for your DAW .
Image-Line mac beta plug-ins (http://www.image-line.com/documents/news.php?tag=gross+beat)
Edison, Gross Beat, Harmless, Harmor, Maximus, Ogun, Slicex, Sytrus and Vocodex.
Might show up as black screen instead of showing their UI.
While we’re investigating internally if there’s a possible workaround, We’ve reported the issue to Apple. You can also reproduce this issue without 32 Lives just by opening the App itself.
Any new update on combatiablity with Mojave? I’ve uninstalled and reinstalled 32 Lives 3 times now… and still no dice. Will this work? or and I out of these plug-ins? Thanks
Hi @adamstan58, as clearly stated here. 32 Lives works just fine with Mojave.
There are specific plug-ins that have some incompatibility issues. but overall 32 Lives works with Mojave.
As stated above, Image-Line are known to not show UI. we have yet to find a workaround to changes introduced in Mojave in that regard. We do promise to update if we have any update on the subject.
have you found a solution to the black sceen in gross beat? I have been running Gross Beat through 32 Lives on El Capitan for months just fine. as soon as i updated to mojave it crashed to a black screen.
Sadly, Mojave has a lot of quirks (or as Apple describes it “compromises” for 32bit and some graphics frameworks used with some 32 bit apps).
We do our best to improve compatibility as possible and committed to 32 Lives.
With that said, it’s not always possible to add ‘workarounds’ to resolve issues between macOS and old plug-ins. especially when newer macOS versions change or remove code that was expected by those old plug-ins.
We have yet to find a solution to allow those plug-ins to work on modern macOS.
I have a problem with 32Lives V 2.0.6 (installed under macos High Sierra) and the newly installed Mojave with update 10.14.6. When i start the desktop app, after half a minute it eats up nearly my whole RAM (16 GB) and scans every plugin so slowly (a minute or 2 for one plugin) that i have to abort it. Is this normal after a system upgrade? Is there something i can do?
Hi @vaikl,
This sounds like unexpected behavior.
We would greatly appreciate if you’llcontact us through support and we’ll schedule a remote desktop support session to resolve the issue.
Hi tal, thanks for your support, but I’ll be on the move for some days now and therefore not at my comp. I’ll ring in when i’m back.
I’ve tried several things in the meantime, especially a fresh install of 32L 2.0.6 and tips like resetting SMC and NVRAM, but nothing helped:( It doesn’t matter if i use the desktop app or any resurrected plugin in a DAW (Live 10.0.6) by opening the plugin manager - the first 150 (or so) plugins go fast, then 32L reaches about 11 GB wired RAM / 17GB virtual RAM and is dying together with the Finder actions more and more until my macmini (late 2012, 16GB RAM) freezes. I have about 450 VST and AU to scan.
Is there any way to manually override the 32L startup plugin scan in the standard VST and Components folders and “hard-code” the app to scan only user folders??
BTW - on the sunny side of this issue I encountered that on Mojave and in Live my old “PowerCore stars” Virus Powercore and VSS3 runs like Olympic champs with - together - only 3-4% CPU power under normal PowerCore Compact settings, which was impossible under High Sierra. And… my Korg monologue is able to remote control the Virus plugin over MIDI with no extra config or tools. Yay!!:-))
.
very sad