Studio One 7 issues

[Yluko]

I joined this forum cause I am running into a few issues, for me studio one has been fairly stable since I started using it, version four. In seven I’ve had allot more crashes in general. I’ve switched to a new computer m1 to m4, changed sound cards from ssl big six to rme, I heard they have more stable drivers. Updated all my plugins. It’s random what crashes it, I can’t point to one thing. My clients all use studio one and they have different hardware more simple then me and they also complain about it crashing allot, all different sound cards all on Mac’s. Many of them with less plugins than me. It can crash doing nothing leaving it on, dragging a plugin to load, doesn’t matter what plugin. Just random playback. Anyone else have such issues? I’d average 15 -30 crashes a week I’d say.

 

[Lukas]

Hi Yluko, welcome to the forum!

The 7.2.2 thread is almost 2 months old, also your discussion is not related to Studio One 7.2.2. Please create new threads for new discussions. I'm going to move this post to a new thread.

 

[Lukas]

According to the best practices here in the forum, please add your specs to your signature. Otherwise, we don’t know which version and OS you are using.

Crash issues are tricky. If Studio One does not tell you which plug-in caused the crash at the next start-up, you will need to find out yourself by removing some plug-ins from your song and seeing if the problem persists. (Make a copy of your song for this. It's important that you really entirely remove the plug-in from your song. Bypassing or disabling is not enough, the plug-in will still be running.)

Also: Do you use AU versions of your plug-ins? The common recommendation is to avoid using AU plug-ins in Studio One.

 

[lokeyfly]

Also, after adding your specs to your sig (important), please add useful details/specifics.

....It’s random what crashes it, I can’t point to one thing.

Knowing what your adding and how, can be vitally important. i.e, what effect or instrument? Is it VST2, VST3, AU, or other? It can potentially matter.

My clients all use studio one and they have different hardware more simple then me and they also complain about it crashing allot, all different sound cards all on Mac’s. Many of them with less plugins than me.

Useless information. Particularly when a good number of users here have Macs of many different types without a problem. So how does that information bolster your issue? It doesn't.

It can crash doing nothing leaving it on, dragging a plugin to load, doesn’t matter what plugin. Just random playback.

So far, what youre dealing with sounds highly unstable. So providing your specs, and actual details by line item will greatly help getting your system, and the Studio One experience to be much more rock solid. For all we know, you're dragging in wrong file types. You may not be, but we don't yet know a single clear description.
Then afterwards, you would benefit by giving your clients solid advice. Or suggest to them to use this forum for their own issues.

Anyone else have such issues? I’d average 15 -30 crashes a week I’d say.

Again, no indication of what is specifically crashing. "Such issues" really won't be the norm for most others. So feel free to keep (your) issues short, separate, and specific. We'd be glad to help you.
Thx.

 

[Vocalpoint]

Anyone else have such issues? I’d average 15 -30 crashes a week I’d say.

Have had 3 crashes since 2011. All due to plugins. As noted Studio One is VERY stable if you give it the proper playground.

I do not use a Mac but I am a devoted RME fan (since 2008). My specs are below...

But 20-30 crashes per week? Sounds like either a very dodgy set of plugins (most likely AU) or something hardware related.

Do not for a moment rule out your hardware - just because Apple built it - does not make it bulletproof.

VP

 

[CoolName]

I joined this forum cause I am running into a few issues, for me studio one has been fairly stable since I started using it, version four. In seven I’ve had allot more crashes in general. I’ve switched to a new computer m1 to m4, changed sound cards from ssl big six to rme, I heard they have more stable drivers. Updated all my plugins. It’s random what crashes it, I can’t point to one thing. My clients all use studio one and they have different hardware more simple then me and they also complain about it crashing allot, all different sound cards all on Mac’s. Many of them with less plugins than me. It can crash doing nothing leaving it on, dragging a plugin to load, doesn’t matter what plugin. Just random playback. Anyone else have such issues? I’d average 15 -30 crashes a week I’d say.

I really have no idea but I know for sure that Studio One absolutely does not like some GPU cards. I'm just chucking that out there.

 

[Yluko]

Added my signature. Mac M4 max, I only use AU except a few times when clients bring over stuff with AU. It crashes whether I have AU plugins or not. It is never the same plugin. The Soundtoys ones tends to crash more than others. It even crashes when I close my sessions sometimes. I am also using console 1 by Softube. I had crashes on my laptop just as often as I did on the new Mac. I thought that would fix it, same with different sound cards. In general I just have the typical plugins most people use Soundtoys, Arturia,Softube and plugin alliance bundles. I can be dragging a plugin and have it crash, I can be playing back the song and doing nothing and having it crash. I have stopped it, got up and 10 seconds later while its not even playing just crash. Somedays I can have 6 crashes other days none. One thing that will almost guarantee a crash is if I am playing with a hardware synth. novation bass station 2, Moog sub 37, Mopho x5, prophet10. I was using the plugins on the first ones but I just got the prophet a few days ago and instead of using any plugin. I am just playing some midi back tweaking a knob on the actual keyboard not recording any midi and within 5-10 minutes it will crash. Happened 5 times today. So in this specific case I am guessing it some kind of midi loop. Seems to happen whether local control on the device is on or off.

I also use a cal digit Ts4 docking station if that might make any difference

Thanks for any insight

 

[Yluko]

Just to bring up a report, I loaded my synth, turned my attack knob for about 5 seconds and it crashed. here is the first part of the report. I downloaded midi monitor to see if there was any midi loop but I din't see one.

Process: Studio One [1022]
Path: /Applications/Studio One 7.app/Contents/MacOS/Studio One
Identifier: com.presonus.studioone2
Version: 7.2.2 Build 107056 (107056)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2025-10-12 19:33:37.6633 -0400
OS Version: macOS 15.6.1 (24G90)
Report Version: 12
Anonymous UUID: AFCCDB71-2047-143E-50F8-A5CC75813800


Time Awake Since Boot: 2800 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

VM Region Info: 0 is not in any region. Bytes before following region: 4295344128
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT (graphics) 10005c000-101898000 [ 24.2M] r-x/r-x SM=COW /Applications/Studio One 7.app/Contents/MacOS/Studio One

Application Specific Information:
abort() called

 

[js1]

Couple of suggestions...

Check to see if any of your plugins are running using Rosetta. There's a utility called Pluginfo (on the Mac App store, $3) which will identify any plugins that are not Apple Native. Strongly suggest you give them up. I had some that caused crashes.

Second, I strongly suggest that you move to VST3. Softube officially advises against using AU with Console One. And though Studio One supports AU, I have personally seen instability at times when I used AU.

I'm on an M4 Mini Pro with Seqouia, and I run large projects with a wide range of plugins from PA, UAD, Softube, Isotope, NI and Waves. I won't say that I never see crashes, but they are rare and almost always on exit after I've already saved.

 

[Yluko]

Thanks, I just bought it. I am guessing the ones that are just intel 64 only are rosetta ones? My Softube stuff is all vst3, the only AU stuff I am using is just fabfilter pro q 3, old sessions from a client. If all Rosetta plugins are gone does it just load without Rosetta mode? What about the plugins labeled apple and intel 64. I see a few rossetta ones on vst I can uninstall but they weren't running in my sessions that were crashing, maybe some but I know for sure not most, the only few I have are like battery, massive and massive X

 

[Yluko]

I checked, studio one was never in Rossetta mode. I just made blank project, two plugins, but I actually just used my monitor which shows up as a sound card, so no audio actually passing through you can hear, I just had a two tracks one a midi one going to the prophet. I was tweaking knobs on the prophet things seemed good for a bit, about 2 minutes in it crashed. The audio wasn't being sent in to studio one, I was just monitoring the synth from its headphones output.

Don't know if this means anything, first part of the crash info

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

VM Region Info: 0 is not in any region. Bytes before following region: 4329832448
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 102140000-10397c000 [ 24.2M] r-x/r-x SM=COW /Applications/Studio One 7.app/Contents/MacOS/Studio One

Application Specific Information:
abort() called


Kernel Triage:
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter

 

[OutrageProductions]

Eliminate S1 as any possible point of failure.
You should find and run a serious stress test on your system functions, you may have bad RAM.

 

[js1]

Yeah, that's not good. You have something out of the ordinary going on. I hesitate to blame hardware, but with that kind of error, it's not out of the question. Running Apple Diagnostics is easy to do: https://support.apple.com/en-ca/102550. That doesn't detect all errors (if you take your computer to Apple, they'll run an overnight stress test). There may be other test suites available on line.

One other thing to try is to repair disk permissions on your drives. Apparently disk permissions are a common enough issue for Pro Tools that it's standard practice anytime problems are encountered.

Assuming the hardware and disk permissions gets a clean bill of health, there are a bunch of things you do to help narrow down the problem. BUT, with that kind of crash log, I'd open a ticket with Presonus.

 

[Sebastian Holtzer]

I really have no idea but I know for sure that Studio One absolutely does not like some GPU cards. I'm just chucking that out there.

Agree. Seems to have Problems with AMD Drivers and HDR on startup here from time to time.

 

[Vocalpoint]

Added my signature. Mac M4 max, I only use AU except a few times when clients bring over stuff with AU. Thanks for any insight

The "insight" that I need to understand is the sentence above.

After suggesting straight up to NEVER use AU in Studio One - you tell us that you ONLY use AU in Studio One.

One more time - never use AU in Studio One and only use VST3 in Studio One.

You will dramatically reduce your crash potential.

And given the technical complexity of these logs you are posting - this is a job for Presonus support. Pretty sure none of us in here will be able to solve this in this user to user forum.

VP

 

[Yluko]

Thanks for all the replies, ran apple diagnostics, no issues, I mistyped above, I meant I almost never use au. I have on client who used to use it and sends me sessions, so his old sessions some I still am working on have them, so some are installed, but these crashes happen no matter if there are au plugins in a session or not, the one I did yesterday had only a single vst in it and I could make it crash easy enough by turning my hardware synth knobs.

 

[Vocalpoint]

Thanks for all the replies, ran apple diagnostics, no issues, I mistyped above, I meant I almost never use au. I have on client who used to use it and sends me sessions, so his old sessions some I still am working on have them, so some are installed, but these crashes happen no matter if there are au plugins in a session or not, the one I did yesterday had only a single vst in it and I could make it crash easy enough by turning my hardware synth knobs.

This is all pointing to hardware for me. You need to kick this up to support for a possible resolution.

Clearly something is not playing nice - and given this is a Mac - it could end being very hard to trace without professional analysis.

VP

 

[tpittman]

Thanks for all the replies, ran apple diagnostics, no issues, I mistyped above, I meant I almost never use au. I have on client who used to use it and sends me sessions, so his old sessions some I still am working on have them, so some are installed, but these crashes happen no matter if there are au plugins in a session or not, the one I did yesterday had only a single vst in it and I could make it crash easy enough by turning my hardware synth knobs.

I assume you have tried a session without any plugs or virtual Instruments? If so, do you get the same thing happen?
I think for me I would just drag in some loops into a new session (no plugs or virtual instruments)
and see what happens. If all good, then open new session with your actual audio files without any plugs
or virtual Instruments and see what happens. If all good start adding your most used plugs one by one to
try to make discovery. Hope you find something out.

I agree with the others here that Support is likely needed but sometimes that takes time. In the old
Presonus Forum there was a Thread about Crashing and Plugs being the culprit along with nice
Instructions how to find the offending culprit. I used it one time and found it was indeed a plug.
I don't remember how the process was done and what plug it was. It was some time ago.

Good luck, hope it get it fixed soon. it's very frustrating for sure

 

[ianaeillo]

I have confirmed a bug with the developer of my interface that exists on the apple side; something with the ethernet card shipped with the last few years of Macs. It can cause daily crashes, sometimes multiple times a day if audio is being sent over ethernet under certain conditions. I have learned how to navigate it and stop it from happening but the problem still exists in the wild. Are you sending audio over ethernet?

 

[Yluko]

Nope, trinnov is controlled over a network connection but no audio. I switched to a nicer usb hub and I have less crashes for sure. Though I still can’t figure out the synth, it doesn’t crash if I use the synth whole studio one is open but if I use an editor app it crashes, same for all synths some kind of midi loop, but local control off on the synth doesn’t fix it. I think the newer softube updates for console 1 made things more stable as well,