I see that native M1 support has been pushed out to some time in 2022

[Heater]

So disappointed.

[PhillipOrdonez]

At least they didn't move it to 2023!

[Jagwah]

INB4 excuses.

[Timmy Crowne]

I wonder if M1 support will be also optimized for M2. They’re slated to be released this year as well.

[DaveyG]

At least they didn't move it to 2023!

... yet!

[sQeetz]

At least they didn't move it to 2023!

... yet!

I fear that's what is going to happen, too....

[avasopht]

I wonder if M1 support will be also optimized for M2. They’re slated to be released this year as well.

Highly unlikely to be a completely new architecture. That would be suicide for Apple.

[selig]

I wonder if M1 support will be also optimized for M2. They’re slated to be released this year as well.

Highly unlikely to be a completely new architecture. That would be suicide for Apple.

Agreed - expect a similar transition as from moto 68000 to Intel a while back.

[sQeetz]

Agreed - expect a similar transition as from moto 68000 to Intel a while back.

Indeed. Now that they design the chips themselves I predict that a new architecture shift is not to be expected for a very long time. Just incremental upgrades to the existing one.

[PhillipOrdonez]

At least they didn't move it to 2023!

... yet!

Got to remain positive! Whatever happens, happens, we'll take things as they develop. For now, M1 support on 2022 is still on.

[sQeetz]

Got to remain positive! Whatever happens, happens, we'll take things as they develop. For now, M1 support on 2022 is still on.

Wish I could share your optimism

[QVprod]

With the performance on M1 being this bad... they absolutely HAVE to make that happen this year

viewtopic.php?p=601023#p601023

This is R11, I would hope R12 happens to run better though.

[StephenHutchinson]

With the performance on M1 being this bad... they absolutely HAVE to make that happen this year

viewtopic.php?p=601023#p601023

This is R11, I would hope R12 happens to run better though.

Since the most recent update, Reason 12 is running faster and better on my Mac mini M1 (16GB Ram). It wasn't in any way super sluggish before but now I feel the responsiveness has been improved. For instance, opening VST panels to get at the instrument/effect open much quicker, with almost zero lag time. Even using Rosetta for now, everything seems to work pretty fast. M1 support will be nice but for now things are pretty smooth, at least for me.

[sQeetz]

With the performance on M1 being this bad... they absolutely HAVE to make that happen this year

From all the things there are to complain about Reason on M1, performance isn’t actually one of them.
At least on my machine

[QVprod]

With the performance on M1 being this bad... they absolutely HAVE to make that happen this year

viewtopic.php?p=601023#p601023

This is R11, I would hope R12 happens to run better though.

Since the most recent update, Reason 12 is running faster and better on my Mac mini M1 (16GB Ram). It wasn't in any way super sluggish before but now I feel the responsiveness has been improved. For instance, opening VST panels to get at the instrument/effect open much quicker, with almost zero lag time. Even using Rosetta for now, everything seems to work pretty fast. M1 support will be nice but for now things are pretty smooth, at least for me.

From all the things there are to complain about Reason on M1, performance isn’t actually one of them.
At least on my machine

Good to hear!

[sQeetz]

Good to hear!

Indeed! It's the RRP that causes some headache (to me):
viewtopic.php?f=66&t=7527418

[integerpoet]

We know adding VST2 support was difficult for RS. They've posted about how it forced them to revamp their handling of buffering and latency throughout the entire app. I don't have any reason to believe adding VST3 support is that much of an earthquake, but I am pretty sure it's non-trivial.

We also know adding VST3 support is, from a marketing perspective, a prerequisite for Apple silicon support. Adding Apple silicon support without VST3 support would basically mean giving up all VST support because VST2 can't run on Apple silicon. Shipping that would be a non-starter from a marketing perspective.

As a result, adding VST3 support must come first. And when they have that working, it makes no sense for them to hold back from releasing it, given the incremental release cadence suggested by the subscription model that so many of you love to hate. It makes perfect sense for RS to work on and release VST3 support before Apple silicon support.

So maybe cut RS a little slack for cooperating with reality. Also, maybe stop whining so much. My word, you people.

[buddard]

We also know adding VST3 support is, from a marketing perspective, a prerequisite for Apple silicon support. Adding Apple silicon support without VST3 support would basically mean giving up all VST support because VST2 can't run on Apple silicon.

I'm sorry, but what do you mean by that?
I'm running plenty of Apple Silicon native VST2s, for example the entire Arturia V Collection 7 and the latest update of Microtonic.
My own internal VST2 test builds of HCS and Portatron also seem to be running fine.
I've tested them in Live, Reaper and Bitwig so far.

[Kilsane]

there are plenty of vst2 which are native Apple M1, example Serume which is VST2 M1 and there are others

[integerpoet]

I'm running plenty of Apple Silicon native VST2s, for example…

there are plenty of vst2 which are native Apple M1, example Serume which is VST2 M1 and there are others

I thought Steinberg announced there would never be a a VST2 SDK for Apple silicon. Did that change or did I misremember?

[tronam]

Funny, I used to think Reason would be one of the first DAWs to become M1 native, but now they're dead last. I bet even Protools will beat them to it, especially now that iLok has finally been fully ported.

[Billy+]

I'm running plenty of Apple Silicon native VST2s, for example…

there are plenty of vst2 which are native Apple M1, example Serume which is VST2 M1 and there are others

I thought Steinberg announced there would never be a a VST2 SDK for Apple silicon. Did that change or did I misremember?

I would like to know more about this stuff as well because it's somehow being sold that vst2 is going to disappear from M1 native plugins which I don't understand as compiling the C for another chipset should work, shouldn't it - yes I'm sure that some changes might need making but this shouldn't mean the end for updated plugins....

[Kilsane]

I'm running plenty of Apple Silicon native VST2s, for example…

there are plenty of vst2 which are native Apple M1, example Serume which is VST2 M1 and there are others

I thought Steinberg announced there would never be a a VST2 SDK for Apple silicon. Did that change or did I misremember?

no idea what Steinberg said, I didn't really follow except that in Cubase 12 M1 in there would not be support for the VST2 format

[tronam]

Steinberg are just not granting new VST2 SDK licenses any longer, but there’s nothing stopping current licensees from developing M1 native VST2 plug-ins and most already have.

[integerpoet]

Steinberg are just not granting new VST2 SDK licenses any longer, but there’s nothing stopping current licensees from developing M1 native VST2 plug-ins and most already have.

Ah. Subtle!

I did not realize Steinberg had ever released Apple silicon support in the VST2 SDK and it sounded as if they'd announced they never would.

But that (plus their announcement about Cubase 12) makes it seem like RS investing in VST2 on Apple silicon would be a bad idea.

I can see why RS would focus on VST3 before Apple silicon. As much as we might wish otherwise, their engineering staff isn't infinite.