Using MacBook M1 With Studio One and Presonus Audiobox USB96

[Low Commotion]

I'm interested in upgrading from my Windows 10 system to a MacBook M1, and I have some concerns using my existing PreSonus Audiobox USB 96 audio interface and Studio One DAW.

I've done some research and it looks like I can use a Thunderbolt-USB adapter to connect the Audiobox interface to the MacBook. So that concern seems to be covered.

I can use Rosetta 2 app so my Studio One will work on the MacBook M1. That concern seems to be covered.

But I haven't been able to find out how well these two fixes will work with the Mac M1. Are there any MacBook M1 users that are using the PreSonus Audiobox USB 96 audio interface and Studio One DAW? Any concerns? Anything I should be aware of? I don't really want to change either.

 

[silky smoove]

Have you checked the Presonus site for their notes on M1 and Big Sur compatibility? That will be the final answer.

Does Studio One still require Rosetta to run on an M1? That’s surprising if so.

 

[Low Commotion]

Have you checked the Presonus site for their notes on M1 and Big Sur compatibility? That will be the final answer.

Does Studio One still require Rosetta to run on an M1? That’s surprising if so.

Thanks for this. I did check the Presonus site and they recommended the Thunderbolt-USB adapter. And they suggested Rosetta. I was just curious if users had issues. I will probably get one of the MacBooks.

 

[silky smoove]

I did check the Presonus site and they recommended the Thunderbolt-USB adapter.

The Thunderbolt to USB-C adapter will work just fine. I've done that on past devices without issue.

And they suggested Rosetta.

That's surprising. Lots of device manufacturers have their products running natively with the M1s and no longer need to operate in the Rosetta environment. I've never used Rosetta myself but I know many users on Gearspace are doing it without issue. I'm sure there's some loss of efficiency, but a USB-C device on an M1 machine should be powerful enough to deal with that loss of efficiency without screwing up a session, provided you're good at managing files, DSP, etc. when you're working, in particular when tracking.

 

[Geri O]

Presonus is still working on a native M1 version of Studio One that doesn’t require Rosetta to run. As for the various interfaces, it’s best to check with the manufacturers’ website.

I love the idea of the M1 versions of the Apple computers, but I bought an Intel Mac almost a year ago and our studio just bought a 2019 Intel Mac Mini. While the M1 Macs are great, I was afraid of various vendors taking a while to get up to speed with the M1 machines. And the Intel Macs will still be viable for another few years.

 

[Funky40]

i run a M1mac.
Rosetta is nothing to worry about. You don´t know it, you don´t feel it.

What IS kind of an "isssue", ...if you want it so:
if you want to run a DAW or a VST Host on aplle silicon native, should you really avoid to mix it with plugins that do NOT run native on apple silicon. Thats all.
If you need to run non aple ready plugins, load your Host under rosetta too.
Thats not something that feels like it would breake the power anything down.



additional, AND looong:
i thought studio One is now M1 ready, also natively........installed the small one a few weeks back, since i´ve not upgraded the big version so far.

i run ALOTS of plugins, and finally also quite many Audio apps in the whole, and quasi everything is working fine.
Even plugins, that tell you on the respective web-page, that they are not M1 ready.
I had solely two plugins creating some troubles.
Well, a upcoming small "issue" is, that some plugins would only be accepted on a rescan of the plugins, when your security settings are "unlocked" and set to "not aple shop only".
......there is this small thing that is nerving !
also on forst startup, or with some after an update: head to security settings and "unlock" it first.....its nerving, but managable.


M1macs are awesome for audiowork !!
for some few users, with very specific software needs might a M1mac not be a ideal solution for now, but in the whole, would i guess will everybody else be super happy.
I mean, its a thing everybody can check vs. their specific apllications.


ahh wait, one thing:
some users have had alots of troubles with screens connected thru USB-C.
no clue if this is solved.
And some have alots of troubles with external HD/SSD Drives that would be spit out randomly.
Some folks report HD crashes based on that.
And then there is same problem, but related to send your M1 mac into sleep mode.
.....so, external drives are in my opinion a problem, respecivly an issue !


but not, dealing with software and Rosetta.
You do not want to deal with an intel mac ever again, after you touched a M1.
its a fantastic experience, and all these every minute small tasks are a tiny bit faster.
Makes for a difference in how your computer feels. granted.

also for folks heading for near no-latency setups is a M1mac a big thing.
go for 16GB or RAM if funds allow. i do all i need with 8GB. but running many audio apps at the same time, is it a bit small on RAM weight

 

[Geri O]

Here's the latest from Presonus on M1 compatibility....

Invalid Link Removed

 

[Funky40]

Here's the latest from Presonus on M1 compatibility....

Invalid Link Removed

i run a presonus Quantum2626, which is rated as apple silicon ready. ...a TB3 AI.
It allows for supersmall latencys, but in my M1 is it NOT spikes free.

so, there is "running" and "running". So be aware that not everything is running as supposed to do........
Aynthing USB class compliant worked perfectly fine on my M1mac.
even the 35€ Behringer unit. Just: these all had/have higher latencys.
good enough for me, for playing with VST instruments.
Playing a Bass roundtrip is a small latency VERY welcome.
Also, since some type of plugins would induce noticeable latencys too.
My PA AMP sims do, and anything FFT based is doing also, for example.


heading for super small latencys would i suggest to take a Thunderbolt AI !
just, as sayed, presonus is here not where it should be, vs. what i have to experience.
another persons experience might vary, though.

 

[Aloe]

i run a presonus Quantum2626, which is rated as apple silicon ready. ...a TB3 AI.
It allows for supersmall latencys, but in my M1 is it NOT spikes free.

this is sad. it might be: the Quantum's driver, the Big Sur, Mac's firmware or whatever else. maybe you'll have a chance to try out another TB interface from other vendor (except of UAD that has tons of latency) and that would point, if that's PreSonus or Apple's fault.

I'm actually somewhat in your shoes -- thinking of M1 machine to run my Thunderbolt Claretts (I usually run them at 3ms RTT, 24/96 and three cue mixes with some effects like limiters). Intel Macbooks have been stable for me, but sound like a rocket jet. Windows PCs don't, but are not totally spike-free. I hoped, the M1 Macs would get the strengths of both, but it seems like not yet.

 

[Aloe]

But I haven't been able to find out how well these two fixes will work with the Mac M1. Are there any MacBook M1 users that are using the PreSonus Audiobox USB 96 audio interface and Studio One DAW?

there's an a recent thread on PreSonus forums on M1 Macs and one of the users reported his M1 MBP to be stable enough with his Presonus ioStation interface and Studio One. he also reported the performance due to Rosetta for S1 is on par with a laptop i7 processor.

that is: currently it looks like M1 Mac won't be a significant improvement to you, unless you're facing bad problems with your current setup (like unexpected dropouts) or run antique hardware. later, when S1 will support Apple Silicon natively, it might be better. but there's also a chance that Apple would come with a more powerful CPU in this year.

 

[Aloe]

Does Studio One still require Rosetta to run on an M1? That’s surprising if so.

well, there're a few DAWs and a few plugins that natively support M1 (without Rosetta). there're some DAWs and plugins that don't support M1 even with Rosetta yet. so yes, most of DAW people having an M1 extensively use Rosetta.

this is somewhat understandable, as M1 Macs are only half a year since hitting the market. and this will improve. but not yet.

 

[silky smoove]

well, there're a few DAWs and a few plugins that natively support M1 (without Rosetta). there're some DAWs and plugins that don't support M1 even with Rosetta yet. so yes, most of DAW people having an M1 extensively use Rosetta.

this is somewhat understandable, as M1 Macs are only half a year since hitting the market. and this will improve. but not yet.

I don't know that I would describe it as "most" people. It's still a mixed bag of platforms that support M1 natively vs Rosetta vs not at all. My comment about being surprised was based on Presonus announcing previously that they offered a custom device driver for their Quantum line of devices that supposedly allowed them to operate natively on an M1 Mac without the need for Rosetta. They said they were ready, but by this account it sounds like they're not. That's surprising.

 

[Aloe]

My comment about being surprised was based on Presonus announcing previously that they offered a custom device driver for their Quantum line of devices that supposedly allowed them to operate natively on an M1 Mac without the need for Rosetta. They said they were ready, but by this account it sounds like they're not.

the driver for Quantum is native, drivers (kexts) don’t work through Rosetta.

but Studio One DAW is only Intel for now, but supported for use with Rosetta.

hope that clears some things up

 

[silky smoove]

but Studio One DAW is only Intel for now, but supported for use with Rosetta.

Yeah, I see that now. I assumed that if their hardware was good to go natively on M1 that their software would be also, but evidently not.

 

[Funky40]

i don´t see why Rosetta would be even a topic.
Things run, and they run fine ! i have my M1mac mini since end November.
so i was quite early. Things were from day one good vs. my audio Software

Ableton Live 11 seems to suck alots of force.
I could imagine that with such a app, a noticeable jump could occour .
My main app, a VST Host, felt not different when i made a arm native only patch.
But it was something simple, and i was nowhere near high CPU loads.

vs. my quantum2626 problems.
i know from another forum that there is a guy who claims that he has no such problems.
I bought a good TB cable (delock, iirc) , and its just 1meter long. But who knows, maybe i had to test another......its at least a possible factor too.
I finally run two AIs allways in parallel, so i can switch at any time if i´d need spike free action. But with the bass i really want the smaller latencys. It IS a difference ( and the quantum has the better sound than my NI kore6 )