Questions & Answers

Anyone else noticing more crashing with the latest Studio One update (

+11 votes
asked Feb 3 in Studio One 4 by maximilliankeene (1,400 points)
I'm getting a bunch more crashes since the latest update of s1 pro  I had to go back to the previous version.  Super annoying to keep losing work.  Anyone else having problems?

I'm on Mac (late 2013 Mac Pro) OS 10.14.6

24 Answers

+2 votes
answered Feb 4 by aka_busker (6,550 points)
What are you doing when it (studio one v4 build 4.6) crashes?  Are you browsing files, dropping instruments, adding plug ins to tracks?

I don't want to presume, but if it's when using the browser, then it's a known bug (according to support) in build 4.6xx and is resolved by rolling back to a previous version like 4.5xxx.  The techs know and are working on it is what I heard last, a few weeks back.  

If that isn't how it's happening, a few more details as to what actions you take that causes the crash will help others to help you.

I hope that helps.
+1 vote
answered Feb 4 by maximilliankeene (1,400 points)
I'm still using 4.6 just the version before this latest update and that ones working fine.  

Its been happening when editing and adding plugins.  At least thats what I've noticed most.  Thanks for your answer - I didn't know about the browser bug but I'm happy they're working on it.
+1 vote
answered Feb 5 by lewpshekla (2,200 points)
Yes same Issues, when editing and loading plugins, saving while playing, not always but random times. Browser is broken for sure. & still a number of graphical glitches. Windows 7 SP1 16GB ram system
+2 votes
answered Feb 5 by justinrodgers2 (180 points)
Mine won't even start up. gets to the medolyne integration process and turns off
+1 vote
answered Feb 6 by lewpshekla (2,200 points)
Speaking of crashes, I've been experiencing quite a few lately, most while loading/creating songs from templates. I'm on a PC Windows 7 SP1.

And my Komplete Kontrol disconnects regularly, losing control of VIs and S1. Also Atom and my faderport loses connection. In the middle of sessions. Faderport & atom does not do this in any other daw I’ve tested. It’s a s1 problem since 4.6 update.
+1 vote
answered Feb 6 by robertgray3 (32,750 points)
I’m pretty sure that Komplete Kontrol thing is a NI issue, file a ticket there. I filed a ticket with them too, they pay more attention when multiple people bring it up.

I think Komplete Kontrol is ******** up the DAW control script, deleting it, then resetting the midi engine which causes the other devices to temporarily be disconnected.

I say that because on their website I’ve seen that same issue in multiple DAWs at different times. Seems they fix it in one then it comes up in another.
+2 votes
answered Feb 7 by mendyka (270 points)
Same... since latest update, S1 Pro has multiple issues!  It crashes on opening, freezes when exiting Studio One... lots of glitches.
+1 vote
answered Feb 7 by mciv (980 points)
It crashes when trying to change tempo in brand new scratchpad
+1 vote
answered Feb 7 by dominicklareu (190 points)
edited Feb 8 by dominicklareu


I have isolated one problem. 

Step to reproduce: 

1- I had an audio track with multiple sections in it and multiples vst added to the track. 

2- I transformed this track to audio - to merge everything and save CPU power  

3- I had to go back to the original audio so did the inverse process ad transfer back the audio track to it's original state.

4- The files created from the reverse conversion were multiples short clip overlapping each other on the same track. I did not notice at first. This track was causing S1 to crash. So I carefully cleaned the audio track of all the small duplicates overlapping each other and the crashes are gone...

Conclusion: many audio clips overlapping each other on one audio track will make S1 4.61 crash.


Original Message****

Same here,

I took an great deal of time creating a project template with complexe routing (Buses, effects sends, VCAs...) And I can't use it! I have started a new song using my template and it crashes every minute or so... I'm trying to go here:

To revert to and older version of S1 but the link os offline...

+1 vote
answered Feb 8 by robertgray3 (32,750 points)
Hey dominick if you find me on the forums and PM me that template i'll try to forward it to someone at Presonus who can take a look at it
+1 vote
answered Feb 9 by lewpshekla (2,200 points)
Good day!!! The dreaded 666 on my master bus meters is back,I’m getting this to at random times, random plugins I got to bypass all plugins until I find which one is causing the issue or restart and it’s working again. S1 is broken from 4.6 onwards. Windows 7 SP1 16GB i5 Skylake set up. I’m gutted and maybe need to upgrade my os. Or go back a few versions. Usually s1 runs silky smooth on my system  but these last updates something is up. I have not installed anything new other than the latest s1 update.
0 votes
answered Mar 12 by rayinreverse (200 points)
I have been noticing LOTS of issues with Studio 1 since installing the latest version. Crashes. Wont open sessions, particularly doesnt like 3rd party plugins.
Glitchy behavior all around. Im rolling back a version
0 votes
answered Mar 17 by markbeling (540 points)
MIne crashes when working in the inspector. feels extremely buggy and hangs , then crashes.....Hardly any plugins are in the session when that happens ... just got back to studio One after two months in Cubase only to horrified at this constant, ..and i mean constant crashing. gonna uninstall and rollback to 4.5

Cmon used top be a pleasure to work in Studio One

Im running a Mac Pro late 2013

6 core

16 gig ram

0 votes
answered Mar 27 by davidjenkins3 (180 points)
edited Mar 27 by davidjenkins3
I also just updated to that version and have experienced crashing.  It occured about 4 times while I was using fat channel and some editing.  I made sure all my plugins were downloaded and properly registered.  There was 2 plugins that weren't downloaded.  I then restarted my computer.   After this I have not had a crash.  I'm using windows 10 diy pc i7 16 gb ram.  I think there is an issue with the plugins and this update.  I think the engineers at  Presonus need to really take a look and see what'g going on because I value stability in my daw.

edit:  I should say that I went to Presonus hub and saw that I had two plugins in the Purchased Items tray that were not installed.  I installed them and so far I have been having smooth operation.
0 votes
answered Apr 3 by lanschuetz (450 points)
Add me too to the list of random crashes and instability. Worst it's ever been in a decade. Ruled out plugins as they no longer show up in the crash files. Sometimes right after start. Sometimes opening one song, but not others. Sometimes can open one song but not the next. Sometimes when I select the Insert to add a plugin. I've sent in yet another crash file to help get this sorted. There's no simple rhyme nor reason as far as I can tell (and I'm religious about removing unused files just to keep the clutter down).

Also failed to start a MIDI device until I did 2 shutdowns and restarts. Been using that device for about 3 years. After getting it to add the device, system crashed on next startup. Next time was fine.

It's literally so **** random that I clench my stomach every time I go to start a song. I have done a re-install, but it made no change.
0 votes
answered Apr 11 by anirudhgonsalves (210 points)

Hey, my studio one used to crash on intense projects... as I was working on them a bunch of times. Then I restarted to computer, now the project and other old intensive (I produce drum n bass, IDM music, along with orchestral film scores) projects started crashing (quitting studio one entirely) as the plugins start to load.

everytime the crash report ends with this code...   

 0x7fff5efc6000 -     0x7fff5eff5fff  libxpc.dylib (1336.261.2) <7DEE2300-6D8E-3C00-9C63-E3E80D56B0C4> /usr/lib/system/libxpc.dylib

which refers to a Segmentation fault.

my Version is 4.6.1, with mac OS: 10.14.6 [Macbook Pro (2018)]

and initially I blamed it on plugins like Melda and Waves but then I tested by uninstallng newer versions of plugins to older..... then tested by opening fresh new project and lesser intensive (one or two tracks with few plugins, loads smoothly)...and putting all these plugins one by one.. saving it, quiting and re-opening... IE; the plugins load up fine.

Help presonus Help!
+1 vote
answered Apr 11 by anirudhgonsalves (210 points)
Found a short term solution! create a new project file and import tracks from the old project! see if it works!
+1 vote
answered Apr 25 by anatolyshiryayev (600 points)
I’m having random crashes all the time. I have a lot of plugins from famous brands and my songs are complex with a lot of virtual instruments and plugins. I have failed to isolate a problem - it looks like a combination of certain plugins make S1 crash. Crashes happen when closing song, reloading the same song, rolling back to earlier song version. Also It looks like VST2, VST3 and AU plugin versions also behave differently in this respect. This crash problem is so irritating when a big song loads up 20-30 seconds, then crash and you are in a crash loop until you go to so gs folder and get your version manually.

How can it be that other DAWs I have don’t crash this often? With my love to Studio One this situatuin really makes me think of searching for more stable working environment.
0 votes
answered Apr 30 by markferrizzi (540 points)
Absolutely! Instantiating plugs mainly so I dropped back down especially after I read the latest update was geared towards support for presonus mixer console and gear users nothing in there for me as far as I know but crashes
+1 vote
answered May 2 by Rasi (380 points)
Yeah, it's been long enough now dealing with plugins ( I believe ) tanking my entire S1, that I'm looking at switching to another DAW entirely. Maybe Presonus will figure out sandboxing eventually...

I notice S1 crashes often when using high web-traffic plugins like Noiiz. With intense synths like Avenger, MSoundFactory, etc. it crashes. It crashes when I open a large Kontakt immediately after editing a different Kontakt instance. Come to think of it, Studio One will die at the slightest whiff of anything serious!

I use a mid-2017 iMac. My PC is not an issue here. I own all my software. Cubase, Ableton, etc. work... What's going on Presonus?
+1 vote
answered May 10 by michaelcorbett1 (230 points)
I just purchased S1 yesterday. I've come over from Logic, I just fancied a change.

So far its crashed on me 3 times when doing normal stuff.

Instances of Omnisphere will sometimes not make sound even though receiving MIDI notes.

I have changed an envelope setting in Impact on a particular pad ( the attack setting on a hihat). Ive recorded some MIDI notes and a pattern playing from this instance of Impact. It keeps resetting the attack envelope to its default.

The whole thing is frankly unworkable. the reviews seemed so great, I like the UI and color, and the sampler record feature and drag n drop all make me want this DAW, but I can't get anything done. It feels like beta testing. Reading these forum posts are pretty disturbing. Should I hang on? from what some of you are saying it seems like 4.5 was more stable? Any hints on whats happening in Impact? Sorry for hijacking the thread but I am gutted
+1 vote
answered May 13 by russellsmith4 (160 points)
I recently started using Studio One (past 6 weeks.. Have been using Reason and Pro Tools for years. Yesterday working I asked myself a question..."Why am I being so tolerant of this software CONSTANTLY CRASHING?"

I work on 2019 Mac mini... lots of horsepower, wanted to utilize some of the features that were not available in othe DAWs I was using. The sound of S1 is actually very nice... and the browser is a great feature... but I am losing valuable productivity rebooting this DAW. Studio One just gets stupid ocassionally, playing recorded audio out of sync, failing to record occasionally, crashing when dragging in a plug in. I mean the list is just too long to keep track of. Has this DAW always been this flaky?
0 votes
answered May 20 by faragher (390 points)
I’m in the same boat as many others here - recent convert to S1 from Logic. Absolutely love working in this DAW but the crashes are driving me crazy. I installed the latest Logic X incarnation yesterday and it can only be a matter of time until I return unless there is an update to address this instability. I’m clinging on in the knowledge that S1 has been stable in the past (it has, hasn’t it?) and in the hope that it will be fixed very soon!
0 votes
answered May 24 by jasonwilmans (720 points)
Don't know if it's related, but I exoerience crashes since this specific update as well. It seems to happen shortly after changing routing options. Like creating aside chain, switching Bus Outputs and stuff like that. Sometimes it doesn't crash but still does weird things like ignoring sidechain input or playing sounds on wrong busses.