Mac Studio "happier" with smaller buffer?

[James Steele]

The only way DP itself is in Rosetta 2 mode is if you do a Get Info on the DP application and check the box to open in Rosetta 2. If it’s not checked, DP itself AFAIK will run native even if some of your plugs require Rosetta.

Not sure what’s causing your issue but obviously something is not right.

[greg328]

The only way DP itself is in Rosetta 2 mode is if you do a Get Info on the DP application and check the box to open in Rosetta 2. If it’s not checked, DP itself AFAIK will run native even if some of your plugs require Rosetta.

Not sure what’s causing your issue but obviously something is not right.

Thanks James-so DP will not switch into Rosetta if I load an Intel plug-in? Obviously the plug-in has to run under Rosetta so can DP do that? Run DP under Apple silicon native while hosting plug-ins under Rosetta?

I am indeed getting horrible latency- last week I had an out of town singer in to sing to the tracks I had produced and we had a hard time getting an acceptable monitor mix.

Would welcome any suggestions to correct this- I meant to start a new thread but here we are!

Greg


Sent from my iPhone using Tapatalk

[James Steele]

The only way DP itself is in Rosetta 2 mode is if you do a Get Info on the DP application and check the box to open in Rosetta 2. If it’s not checked, DP itself AFAIK will run native even if some of your plugs require Rosetta.

Not sure what’s causing your issue but obviously something is not right.

Thanks James-so DP will not switch into Rosetta if I load an Intel plug-in? Obviously the plug-in has to run under Rosetta so can DP do that? Run DP under Apple silicon native while hosting plug-ins under Rosetta?

Thanks my understanding. DP has a way to run Intel plugs in Rosetta, but just those plugs... the app does not have to be running on Rosetta. AU's have no problem with this, but VST2 may not always work. I know that in either case, when I'm installing a new, non-native plug that I expect is going to prompt me for a serial number or license code to authorize it, I launch DP in Rosetta just to be on the safe side and get though the authorization.

I am indeed getting horrible latency- last week I had an out of town singer in to sing to the tracks I had produced and we had a hard time getting an acceptable monitor mix.

Would welcome any suggestions to correct this- I meant to start a new thread but here we are!

I'm the wrong person to help in some ways because I've only recently upgraded to a modern MOTU interface. Till only recently I was still using PCI MOTU hardware. But even then, you had to use CueMix to get low latency when monitoring. Depending on what interface you have, you may have to use the built in mixer that's inside a MOTU interface and set that up for monitoring inputs using the utility that MOTU gives you for that. There's a very (seemingly) complicated grid and settings for configuring this. I still have not figured it out. Hopefully someone on the board can give yo better advice, because there is a way to get acceptable monitoring.

[HCMarkus]

At the heart of the UAD system is the Apollo Console. This simple mixer application makes it easy to set-up monitor and cue mix routing, making it a cinch to build complex tracking chains - all with full recall.

Use this feature your interface and you won't have to worry about latency.

But there is still something going on that is awry; you should be getting low latency with small buffers on your Mac Studio.

[greg328]

Thanks yes, I’ve got Console and should be using it but don’t know it that well yet— last week I was just trying to move quickly to record my vocalist in a limited time window.

I was surmising that my latency was due to Rosetta, but now I’m doubting that. Is there any way to confirm Rosetta is active while DP is running? Perhaps using some Apple utility app?

Greg


Sent from my iPhone using Tapatalk

[cuttime]

I was surmising that my latency was due to Rosetta, but now I’m doubting that. Is there any way to confirm Rosetta is active while DP is running? Perhaps using some Apple utility app?

[HCMarkus]

https://www.thinkersnacks.com/as-pluginfo.html

This will tell you about all of your plugins. I encourage folks to buy thru App Store to support the developer.

[primeevolutionary]

Also, in the Activity Monitor if the app is showing as “Intel” it’s running on Rosetta 2. If it shows as "Apple", it's running native.

[greg328]

Thanks all- yes, I’m aware of the checkbox in the Get Info pane to start an app in Rosetta. Mine is of course unchecked. I was just wondering if after starting DP in native that it could somehow revert to Rosetta when loading Intel plug-ins.

I do indeed have the PlugInfo app— it’s proving invaluable for only a few bucks. Was able to confirm that my SSL native plugs are Intel-only.

By the way, regarding SSL, I sent them an email a few days ago, inquiry regarding a possible date when their plugs may be Apple ready—the response was very curt. A simple “no date set” response. I then returned another question of “is there a plan in place?” I received another curt response saying no date set. The support guy also said he was ending this support thread.

Sooooo- seems SSL does not want to be asked about their Apple Silicon readiness. Looks like they’re way behind.

Also— we all know that Native Instruments is wayyy behind as well. I use Guitar Rig 6 extensively in my productions That’s Intel-only.

So, the million dollar question is, when opening digital performer natively, and then loading an Intel plug-in, does that cause the host app to switch to Rosetta, or is just the plug-in running in Rosetta mode?

Good suggestion on checking out Activity Monitor, I’ll do that.

Greg


Sent from my iPhone using Tapatalk

[James Steele]

By the way, regarding SSL, I sent them an email a few days ago, inquiry regarding a possible date when their plugs may be Apple ready—the response was very curt. A simple “no date set” response. I then returned another question of “is there a plan in place?” I received another curt response saying no date set. The support guy also said he was ending this support thread.

Sooooo- seems SSL does not want to be asked about their Apple Silicon readiness. Looks like they’re way behind.

I notice they've been blowing out a lot of their plug-ins pretty cheap. I've bought quite a few on sale, but it does make me suspicious. I feel like maybe they're not going to be updated and they're squeezing every last bit of revenue out of them. Besides, without a firm commitment to make them Apple Silicon native, who would even THINK about buying their plugs at the normal price.

The other possibility is they'll do what McDSP did recently. I bought a bundle of 3 of their plugs for a great deal... I don't remember the name of the bundle... Maybe it was Retro? Anyway, I bought version 6 for the blowout price. Lo and behold... a couple weeks later version 7 drops that is native and there's no grace period. You have to pay something more substantial to bump up to the native versions. I think, honestly, many developers are going to *use* the demand for native plugs as an opportunity to charge upgrade fees. For many of us, that *feature* alone is enough to motivate us to pay the upgrade fee.

[HCMarkus]

So, the million dollar question is, when opening digital performer natively, and then loading an Intel plug-in, does that cause the host app to switch to Rosetta, or is just the plug-in running in Rosetta mode?

Quite certain DP is running Native; proof for me is the fact that some non-Native plugins (BFD and NI's FM8 among others) won't even OPEN in DP Native. They crash DP Native, but work fine in DP Rosetta2.

[greg328]

Yes but- I’m opening 100% Intel-only plugs inside DP opened natively. So, what’s going on? It’s certainly possible to do so.

And, back to my original concern, can this cause excessive latency?

I wouldn’t care about Rosetta or not, if it didn’t introduce excessive latency.

And james, yes, SSL’s recent blowout pricing on Intel-only plugs is rather suspicious indeed!

Greg


Sent from my iPhone using Tapatalk

[tremo]

Also— we all know that Native Instruments is wayyy behind as well. I use Guitar Rig 6 extensively in my productions That’s Intel-only.

Guitar Rig 6 is now Apple Silicon native -- just in the past day or two. Still waiting for Battery, Reaktor, and all the rest, but at least NI is creeping forward...

[greg328]

That's great news! I'm currently mixing a record where I use Guitar Rig 6 extensively---I'll get that update today!
Thanks for sharing-
Greg

Also— we all know that Native Instruments is wayyy behind as well. I use Guitar Rig 6 extensively in my productions That’s Intel-only.

Guitar Rig 6 is now Apple Silicon native -- just in the past day or two. Still waiting for Battery, Reaktor, and all the rest, but at least NI is creeping forward...

[HCMarkus]

Yes but- I’m opening 100% Intel-only plugs inside DP opened natively. So, what’s going on? It’s certainly possible to do so.

And, back to my original concern, can this cause excessive latency?

Along with the non-AS-Native plugins that WON'T run, I've tried many that DO run in DP-Native. And they do not cause any latency issues for me. Doesn't mean that one F'd up plugin might not screw up your system, but I have not experienced that.

I'm running DP Native during all my current sessions (except one resurrected project that requires BFD). Within DP Native, I've got multiple Altiverb instances (Altiverb is not AS-Native; to install Altiverb, one must run DP in Rosetta2 Mode; DP will then scan Altiverb and allow it to be used under DP Native.). I've run Ivory (requires same install procedure as Altiverb) without latency issues, but have been staying away lately as there have been some stability issues it introduces. I've installed and run Slate Drum Trigger without issue. I'm sure there have been others.

Unlikely, but just in case... You are not, by chance, running any mastering plugins...? Plugins with big look-aheads will, of course, cause massive latency, regardless of buffer size.