I'm testing Studio One 3.1 on a win 7/64 system (32 Gb ram, inel i7), and as many of other user I'm experimenting many crashes. I don't know if they are caused by bad plugins (many of them worked fine under SO1 2.6 but some AudioUTOPiA were installed......), by other config problems, or by SO1 3.1 itself.
The really annoying thing is that after a crash the program becomes not responding, or it takes minutes and minutes to terminate process, even using task manager or similar task killing programs.
Obbiously, I cannot accept DAW instability, and the idea to test vsts one by one to find an (eventual) "responsible" drives me crazy (even if I have many doubts abot Omnisphere 2.....), above all coming from S1 2.6, the more stable DAW I worked with always; but waiting so much time after a crask or restarting the machine really pisses me off.
Any similar experience and suggestion?
Thanks in advance

 

On the same system as yours (i7(2014),32GB, W64, latest S1) everything runs fine, including the new melodyne which in older version could really easily crash S1 just by holding the melodyne note sound. Some of my projects require maximum latency buffer from my RME to run without dropouts and even those projects are totally stable with all recent Audioutopia plugins, Omnisphere2, U-HE, NI, 30 instances of Kontakt etc.

 

I read all the posts on Studio One 3, especially related to Windows 64bit and on fairly modern machines, and the vast majority are positive when referring to stability etc. This is highly likely plugin related. Finding the culprit plugin is frustrating, but has to been done if you want to carry on creating music with an up-to-date Studio One. Start with the plugins you suspect. Treat it as a learning-curve and you'll know how to advise others who'll, no doubt, have similar issues in the near future. Good luck.

 

Power-cycle Your audio-interface after a crash, this enables You to stop the process immediately with the task-manager.
Karl

 

It could work, but I think that this operation is not the best for the A/I hw life....maybe I could try to disconnect USB.....

 

If its that same Audioutopia plugin problem that S1v3 users have been experiencing (Audioutopia plugins crashed S1v3 on Windows 10, same plugins did NOT crash S1v2, happened to many of us including me) Then the solution is to run S1v3 in Windows 8 compatibility mode. That worked for me with no noticeable differences in speed or usage at all.

You're on windows 7, though...so yeah...

 

Have you overclocked your CPU? If so, don't. S1 does not like it on 64 bit systems. I had the same experience. I'm on I7 too and now it's working without any problems with any plugin. S1 is top notch and what is there still to come next week?
Cheers...

 

To be a bit creative, and possibly right, I will tell you to try running memtest86+ http://www.memtest.org/ for a few hours and see what you get. It might be RAM or your hard disk, too. First see if you can finish the memtest86+ and then try testing your hard disks and solid disks with the official tool from the manufacturer. You could also try testing the general stability of your computer with AIDA64 burn-in test: http://www.lavalys.com/products/everest-pc-diagnostics/ for a couple of hours. It's better to be sure about the hardware working properly first, and catch the dodgy hardware so you can get it replaced, or set up differently, before accusing the software.

I hope it helps!

edit: believe it or not, but in the majority of cases when I encountered stability problems with the DAW it was usually RAM, hard disk, solid disk, or even bad motherboard in a couple of cases. And I never overclock the CPU at least for the first month, just to be sure that all the hardware is working properly first.

 

Last edited: Feb 18, 2016

Thanks you all for the suggestions, but it seems I found (at least for the moment) a solution for the cracks; seeing the old thread " S.One 3 crashing every day" I followed the suggestion from Audiowolf:

..."I used to have constant crashes until I set "Internal Block Size" in audio settings back to 512 instead of higher".....
Don't ask me why it was setted to 256 but moving to 516 created a good stability (I repat, knocking on wood, till the next crash).

But the (second) main question remains.....how to kill in an acceptable time Studio One process and why this happens only with S1 crashes? tried with Reaper, it didn't take so much time using task manager....

 

ASIO buffer has to be set to 512 samples for stability?! Are they serious? What audio card are you using? Maybe ASIO driver is the problem.

As for the killing S1 process, maybe you can try to do it with this very useful program: https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx
or this one: http://tweaks.com/windows/39559/kill-processes-from-command-prompt/
Some more info here: https://stackoverflow.com/questions/49988/really-killing-a-process-in-windows

 

Last edited: Feb 19, 2016

What can I say, I agree with you....and I'm serious (not always, obviously). My audio card is a rock solid RME fireface UCX, really stable ASIO drivers. And I really didn't understand the technical reason further to audiowolf suggestion, I simply tried it....and it seems to work. But maybe yesterday was a Lucky day and I didn't touch anything critical during my 4 hours session

 

Found a good way.....if anybody interested
Win 7/64
Disconnect-------->reconnect
(almost 0 time needed)
And voilà, the app is killed