Flangers and phasers

[rasmusklump]

Is the Admiral Quality site still safe?
It's the site with the most aggressive adds and popups I have seen in a long time.

[SMH]

Admiral-mike asked : 'Is he sure? Customers report their AUs work.'

Not sure where the conflict is with my information.

Think he thought you meant the AUs don't work but you mean they don't need the fix? ok!!

[simon.a.billington]

Intel AU will also run in native Apple Silicon DAWs (without opening the DAW in Rosetta2) thanks to AUHostingCompatibilityService.

I didn't know that, thanks! Does this happen automagically, or are there settings and checkboxes to be aware of?

Does it also apply to AU instruments?

Apple is dropping Intel/Rosetta support with its next major macOS release. So it would be wise to transition away from any Intel code.

[jamcat]

Duplicate

[jamcat]

Duplicate

[jamcat]

Intel AU will also run in native Apple Silicon DAWs (without opening the DAW in Rosetta2) thanks to AUHostingCompatibilityService.

I didn't know that, thanks! Does this happen automagically, or are there settings and checkboxes to be aware of?

Does it also apply to AU instruments?

Nothing needs to be done by the user, so long as they already have Rosetta2 installed and an AU-capable host. It applies to all AU plugins. There’s nothing inherently different about instruments that would make it not apply to them as well.

Apple is dropping Intel/Rosetta support with its next major macOS release. So it would be wise to transition away from any Intel code.

Definitely the best advice to follow, though I think it’s actually 2 versions away still. But with Apple’s long-running yearly update regime now being codified by year-based os versioning, Rosetta’s end may only be a year and a half away.

But absolutely no developer should need more than a week to port an existing plugin with AI assistance. The era of excuse-making is over.

[simon.a.billington]

Intel AU will also run in native Apple Silicon DAWs (without opening the DAW in Rosetta2) thanks to AUHostingCompatibilityService.

I didn't know that, thanks! Does this happen automagically, or are there settings and checkboxes to be aware of?

Does it also apply to AU instruments?

Nothing needs to be done by the user, so long as they already have Rosetta2 installed and an AU-capable host. It applies to all AU plugins. There’s nothing inherently different about instruments that would make it not apply to them as well.

Apple is dropping Intel/Rosetta support with its next major macOS release. So it would be wise to transition away from any Intel code.

Definitely the best advice to follow, though I think it’s actually 2 versions away still. But with Apple’s long-running yearly update regime now being codified by year-based os versioning, Rosetta’s end may only be a year and a half away.

But absolutely no developer should need more than a week to port an existing plugin with AI assistance. The era of excuse-making is over.

Apple does this 5 year cycle thing with pretty much everything they do. In fact the first time around they went from ARM to Intel was a 5 year adoption. Now consider that the first M-Class machine dropped in 2020, they are already over due.

But if that's not enough to go by I'm also getting periodic warnings on my machine saying that a certain Intel background process won't be supported in an upcoming version of macOS. Here is the link it points to...

https://support.apple.com/en-au/102527? ... r-52526201

I certainly think that the case is pretty strong that Intel/Rosetta will be dropped with the next macOS 27 which will most likely be launched around September.

[La Mato]

Want to make a case for the HOFA PhaserChorusFlanger. Small footprint, easy to use and sounds really good. Added bonus that it can be used in the SYSTEM infrastructure.

[sqigls]

Intel AU will also run in native Apple Silicon DAWs (without opening the DAW in Rosetta2) thanks to AUHostingCompatibilityService.

I didn't know that, thanks! Does this happen automagically, or are there settings and checkboxes to be aware of?

Does it also apply to AU instruments?

Nothing needs to be done by the user, so long as they already have Rosetta2 installed and an AU-capable host. It applies to all AU plugins. There’s nothing inherently different about instruments that would make it not apply to them as well.

Apple is dropping Intel/Rosetta support with its next major macOS release. So it would be wise to transition away from any Intel code.

Definitely the best advice to follow, though I think it’s actually 2 versions away still. But with Apple’s long-running yearly update regime now being codified by year-based os versioning, Rosetta’s end may only be a year and a half away.

But absolutely no developer should need more than a week to port an existing plugin with AI assistance. The era of excuse-making is over.

Apple does this 5 year cycle thing with pretty much everything they do. In fact the first time around they went from ARM to Intel was a 5 year adoption. Now consider that the first M-Class machine dropped in 2020, they are already over due.

But if that's not enough to go by I'm also getting periodic warnings on my machine saying that a certain Intel background process won't be supported in an upcoming version of macOS. Here is the link it points to...

https://support.apple.com/en-au/102527? ... r-52526201

I certainly think that the case is pretty strong that Intel/Rosetta will be dropped with the next macOS 27 which will most likely be launched around September.

"certain Intel background process won't be supported" is more likely the kernel stuff ?
i was getting the same message when i was using the kernel version of the RME drivers.

[jamcat]

I certainly think that the case is pretty strong that Intel/Rosetta will be dropped with the next macOS 27 which will most likely be launched around September.

Here is the official word from Apple:

“Rosetta was designed to make the transition to Apple silicon easier, and we plan to make it available for the next two major macOS releases – through macOS 27 – as a general-purpose tool for Intel apps to help developers complete the migration of their apps. Beyond this timeframe, we will keep a subset of Rosetta functionality aimed at supporting older unmaintained gaming titles, that rely on Intel-based frameworks.”


So yes, Rosetta2 will still be supported in the next version, macOS 27, but will not be supported any longer starting with the version after next, macOS 28. So the Rosetta sunset is two versions away still.

[whyterabbyt]

But absolutely no developer should need more than a week to port an existing plugin with AI assistance. The era of excuse-making is over.

How many times have you done this yourself, then?

[Ivan_C]

But absolutely no developer should need more than a week to port an existing plugin with AI assistance. The era of excuse-making is over.

https://en.wikipedia.org/wiki/Dunning%E ... ger_effect
https://en.wikipedia.org/wiki/Ne_supra_crepidam

[jamcat]

How long did it take you, and which AI agent did you use?

[whyterabbyt]

How long did it take you, and which AI agent did you use?

You're the one making the claim, so how long did it take you, and which AI agent did you use?

[Ivan_C]

How long did it take you, and which AI agent did you use?

DKJ.png

It took me < 1 minute, and I did it without any AI agent