A few days on and I’m still not properly up and running. My attempts to use USB for the MOTU was, as I mentioned, not terrifically successful, with the Mac and various DAWs seemingly only occasionally able to connect to the interface. A Presonus 1824c was only marginally better, often emitting rather annoying white noise out of its main outputs on start up until the internal clock was switched and then switched back using the supplied control software. Today I will pull a Focusrite Solo I use with my “art” computer and try that one. If it works, I might order an 18i20 to act as a temporary solution.
At this point, I am quite frustrated and seriously considering sending the M1 back to Apple and getting another Intel. Too bad, because the M1 is a really fast computer, but it (or the interface manufacturers) don’t seem to have all of the wrinkles ironed out.
That’s good to know. Thanks. I’m pulling out what little hair I have left trying to get something stable and consistent going here. I really don’t want to send this Mac back to Apple. The Solo should give me a clue as to whether the Focusrite stuff will give me any issue. If not, I’ll order an 18i20.
Sorry to hear that’s not working out. I was considering getting a MOTU ultralite mk5 as an upgrade to my Audient EVO8. Maybe I should hold off.
I’ve used the DT, an Apogee One, HX Stomp, and an EVO8 as audio interfaces without problems on the M1 (I use all of these as an aggregate device). I know these are not in the same league as studio interfaces, but maybe I should just be happy that they work and just use them vs dreaming of a better interface #NGNY
My experiences may not be the usual, I don’t know. I would think that there would be more people than just myself and @senor-bling talking about this problem if it was endemic to either the platform or MOTU. I’ve now seemingly gotten the Presonus working properly via USB, but I’ll keep experimenting with the MOTU, as I’d rather be using that.
Thanks for the heads up. According to the release notes the kernel panic leading to a restart is among the issues they fixed.
EDIT…
Half an hour and three successful shutdowns later it looks like it works. Only tried a few things, like starting Logic, playing back and recording a short segment, changing interface sample rate, creating an aggregate device. Nice to see something as basic as a shutdown work as expected Snark aside, glad it got fixed. And since MOTU don’t seem to be alone in having Thunderbolt+M1 related issues, kudos to their devs and support team for issuing updated drivers.
Indeed. I’ve had no issues with spontaneous reboots since installing, and I shut it down maybe six or seven times, each after trying out stuff in Cubase and Bitwig. I am feeling quite optimistic about this now. I was on the verge of sending this computer back to Apple (only a few days left on that 14 day return window).
I’m having trouble in studio one with native mode. I had a track almost finished, then all of a sudden two plugins didn’t render correctly. The automation was totally off in the render. Then it lost a bunch of plugin settings while saving, which reset them to default.
Guess I’ll still stay in Rosetta for another while.
So far, so good. I didn’t shut it down more than once or twice today, but it was fine both times, and it was fine during numerous shut-down tests yesterday. I’ve just done light MIDI work so far, but tomorrow I will begin tracking in earnest, so that’ll really tell the tale. I’ll report back with the results. I’m feeling pretty good about it now.
I just installed the beta m1 versions of liquisonics seventh heaven and soundtoys bundle. Solves some minor issues I had. Just in case somebody else has some issues
Try updating Monterey , I think there was another update very recently.
I can’t remember if it was loudspeaker or headphone , it may be worth trying each too
Fundamentally it shouldn’t have had any glitchy audio for decades.
