Apple announces new Mac Mini, Air + 13" MBP featuring their own M1 chip.

[Etienne1973]

Audiounits are not longer detected after an installation.

True.

The user has to reboot the Mac first.

Logging out and back in is enough in most cases. My experience.

[Sascha Franck]

Hasn't that been fixed with Mojave? Anyhow, I have a little script saved, performing the mentioned command (I'm under High Sierra). Works fine. No need to reboot or re-login.

[audiothing]

But how it is a good thing? Every new macOS os bringing some work on a table that Windows doesn't. Sierra, High Sierra, Mojave, Catalina has compatibility issues and idiosyncrasies. One can take 2010 installer on windows and run it in 2020 and it would work. One can take 32 bit daw and plugins and they would work. I mean you run your own company the way you'd like but as customer i prefer stability and longer support like on windows to catalina compatibility issues.

I don't remember any big compatibility issue up to Mojave.
Backward compatibility, while can be seen as a strength, it's also a weakness for security and technology progress. Anyway, nobody is forcing you to update to Catalina or Big Sur (unlike the forced Windows 10 updates). I'm actually using Mojave on my main machines, and that's good enough to build our entire plugins catalog from Lion to Catalina.
And if you really really need that old 32bit DAW/plugin or software that has not been updated for 10 years, you can still keep an older machine running or run a VM.

Moving to Silicon will, of course, force us to drop some older macOS versions (I still need to check how far we can go), but this also keeps us active in developing and maintaining our software. And this is a good thing for the business and the customers!

Seriously? you should run killall -9? =))))

Why not? I agree that it should have been fixed years ago, but it's really not a big deal. Either restart your Mac or run that command, it just forces the AU to rescan when you open your DAW.

[audiothing]

It is a well-known and serious technical problem with Audiounits which appeared with OSX 10.9.

As said, I agree it should have been fixed already, but I wouldn't call it a "serious technical problem".

I also remember the drama with 'notarisation'. A massive number of developers had serious problems with it. There is a long thread about it on the developer-forum on kvr.

Sure, some had problems with notarization. We didn't. It took just few days of work to implement the process in our build script. Now it's fully automated, and, again, never had major issues with it.

[anttimaatteri]

I looked at the blurb and saw 3.5 times CPU power the last mac mini and thought - Bull. A little digging and I found the detail - 3.5 is compared to an i3 version from 2018 doing a transcoding task. So while that is an improvement and suggests it is a powerful chip it is certainly not a particularly good metric for assessing how VST performance will compare with my i7.

its funny isnt it . that advertising strat is the best i ever read hahaha. appleoids are already jizzing about it, ready to blow them and their money away for their redesigned "bunker-tablets tech", formerly know as laptops and desktops. best strategy for getting rid of hackintosh coms tho.

[revvy]

Probably be better if some devs simply stopped developing for certain platforms.

Less calls to the whaaaaambulance for sure.

[Markus Krause]

I am aware that some people don't like what I write about Apple. But it's all facts. Sorry if i should have hurt your personal feelings

We devs also have the right to voice our opinions. Especially when things go wrong for a long time I see it as a duty to inform the customers about these facts. Keep in mind that I am a senior software developer (full stack with university diploma ) who is programming plugins since 20 years (full-time) . I have very detailed knowledge about how computers, operating systems, plugins and software works

I will getting such a new Mac mini for development and testing. There are still many people using this platform.

But I will not recommend the ARM Mac to our customers. There will be trouble with various plugins and hosts. This is nearly inevitable.
I don't care if you buy such a machine or not. It's your money. But you can't say that you haven't been warned

[zvenx]

The issue is that it is not facts.
In a lot of those are your opinion that you parade as facts.
That is EXACTLY the issue.

I think, and this is just a guess, your issue with apple and vst3 is that you see spending time on them and no financial rewards directly for that time. Which yeah it is your call.

You are of course entitled to your opinions, but don't masquerade them as facts.

rsp

[Markus Krause]

Sorry Richard. You are a just a beta tester, but not a developer. You know nothing at all about programming. If i remember correctly you do not even own a mac.

In some months you will notice that my warning about the technical problems will turn out as true...

I will not further join this discussion and waste my time on kvr. Bye bye

[zvenx]

I am typing to you on a mac as we speak.
I use cubase on mac and nuendo on pc. Audiothing who is a developer already showed your 'facts' were incorrect.
I have had many convos with developers that I beta test for, over the years, both large companies and one man shows, asking some of the very issues you raised... Unless they all conspired to lie to me.
rsp

[chk071]

I am typing to you on a mac as we speak.
I use cubase on mac and nuendo on pc. Audiothing who is a developer already showed your facts were incorrect.

Actually he rather presents his opinion than to prove Markus' points incorrect. And, I can well see where Markus is coming from. I take a brief look into coding sometimes (mostly web development), and, things are moving fast really. And, in this case, we're taking about a whole new architecture. Mac OS is just way more bleeding edge then Windows, and, I understand that this can be very frustrating for developers (and users).

[chk071]

Probably be better if some devs simply stopped developing for certain platforms.

Problem with that is that there would be a lot of "Boo-hoo-hoo... no Mac version.. " then. It's almost an obligation to serve both platforms. Simply because of Apple's market share for audio apps.

[Markus Krause]

Dear Richard,

Beeing able to compile a plugin for a new CPU is one thing.
Beeing able to run various plugins in various hosts within an emulated environment and running it in a completely new OS is another thing.
We just have to look back to the transition from 68000 to Intel for this. Most likely similar problems will arise again.
We will see in a few months wo was right...

Have a nice evening,
Markus

[Ploki]

Dear Richard,

Beeing able to compile a plugin for a new CPU is one thing.
Beeing able to run various plugins in various hosts within an emulated environment and running it in a completely new OS is another thing.
We just have to look back to the transition from 68000 to Intel for this. Most likely similar problems will arise again.
We will see in a few months wo was right...

Have a nice evening,
Markus

i don't think it's all that comparable.
First of all, they already made it possible to use ARM stuff on Mac with same codebase years ago. Some devs (Fabfilter) have already made ARM stuff for iOS, also years ago, even before apple made it easy with Catalyst.
Running stuff under Rosetta2 is less problematic. We'll see how stuff plays out in practice, but i don't think it's gonna be nearly as bad as you predict.

[zvenx]

Dear Markus ,

I do except a change in architecture to entail work, but this was not the only claim you made as facts.
It is the other stuff I took greater issue with. For instance my macbook pro is a 2014 macbook pro and I am running mojave by choice, it reminds me daily that I can run Catalina... That mac is now six years old not three years old.

What I did say though is from the developers whom I have had one on one convos with on it, the change to ARM/Silicon Mac wasn't as bad as either they or I expected it to be.


I personally don't like to be a guinea pig so for sure I would not be buying any first edition ARM Macs. On that we fully agree on.

rsp