PreSonus Forums

I already did. I can't reproduce this issue, so I can't report it for you.

I would just create a new support ticket, describe the issue briefly (don't forget details about your OS and other system specs) and give some steps to reproduce. Mention that disabling the ethernet adapter seems to help. And attach a video (screen capture) in your bug report.

jazzundso wroteI already did. I can't reproduce this issue, so I can't report it for you.

I would just create a new support ticket, describe the issue briefly (don't forget details about your OS and other system specs) and give some steps to reproduce. Mention that disabling the ethernet adapter seems to help. And attach a video (screen capture) in your bug report.

Thanks for your feedback.
Support ticket opened.

weswild wrotewhy does it crash so much ? i turned of auto save , my computer does nothing but studio one . plugins are up to date which took ages . windows i7 16gb ram no heavy processes just small projects but really random freezes . love this software so much but its the most buggy i have ever experienced . seems with every update it gets worse . frustration

Confirm I have had a couple of crashes when dragging an FX into a track during play back. I accept with only 4gb ram it might be expected but it never ever happened before. Anyone else noticing more freguent crashes with 5.5.2?

Quietly wroteConfirm I have had a couple of crashes when dragging an FX into a track during play back.

If the plug-in crashes when you open it, it's up to the plug-in developer to fix the crash.

jazzundso wrote

Quietly wroteConfirm I have had a couple of crashes when dragging an FX into a track during play back.

If the plug-in crashes when you open it, it's up to the plug-in developer to fix the crash.

Presonus FX plug-in not third party.

Does the crash also occur when you open the song without 3rd-party plug-ins? If not, it still seems to be a 3rd-party plug-in issue.

jazzundso wroteDoes the crash also occur when you open the song without 3rd-party plug-ins? If not, it still seems to be a 3rd-party plug-in issue.

No problems in opening song and my third party plug-ins such as Izotope have been running perfectly in S1 for years. The two recent crashes have occured when I have the mixer open with the song playing back and I have dragged a Presonus FX as in Pro EQ on one occaision and Room Reverb on another onto a track. Both times a complete freeze and required a reboot. Note this is not constant and therefore very hard to recreate if not impossible. Solution stop play back before dragging an fx across (Never had to do this before) and save frequently in case of freeze up and reboot being required.
By the way thank you for your interest its much appreciated.

NOTE: Since mentioning this and after updating Windows 10 latest update this has not happened again. Hush my lips as I hate tempting providence.

I had it freeze on me a few times and the cursor disappeared on me too. Going back to 5.5.1 in the meantime.

Hey guys- I need some advice. Revisiting S1 today to see if stability has improved, and in the past 4 hours, it has crashed 27 times. Stability seems worse than the last time I tried a year ago. Some examples of issues I'm dealing with today:

• Midi notes constantly getting stuck
• Undo history randomly dropping
• Desync between tracks and the mixer (muting a track in arrangement view does nothing until muted in the mixer window)
• Crash when moving a midi region with chord-track follow enabled
• Crash when closing a vst window
• Crash when inserting a midi note in the piano roll
• Crash when zooming in
• Crash when bypassing an audio effect
• Crash when breathing too heavily / when cat sits on keyboard

My plugins/OS are all up to date, work fine in other DAWs, my machine has 64GB ram and is quite beefy, and I've made sure to kill all other processes not related to S1 when debugging, etc. I suppose my questions would be:

1. Is this level of instablity common? Should I come back in a couple more years? (it has been hit-or-miss in my experience over the years)
2. Is this because I'm on Mac? Is S1 more stable on Windows or Linux?
3. Is there a stable version I should be using?
4. As an OSS developer, is there any way I can debug my constant issues / run devtools / run from cli with logs? Reading crash logs always shows the same malloc errors (EXC_BAD_ACCESS (SIGSEGV)[/b], [b]UNKNOWN_0xD at 0x0000000000000000)
5. Does S1 need to be re-written in a memory safe language like Rust? (joking but man wouldn't that be sweeeet)
6. BBCode... really? No Markdown? (ok still joking I'll stop )

Unfortunately, I don't really have the time to make repros/tickets for the constant bugs I encounter when making a new song. Not to mention, there seems to be no public bug tracker to avoid wasting time reporting known bugs (just open source S1 Presonus it's 2022 and you would become unstoppable ).

Studio One is, in my opinion, one of the most well-designed and feature-rich DAWs on the market. If I could actually use it, it would be my favorite by far, and I use them all. I suppose I'm just wondering if there is hope, and/or if there's something I'm missing / doing wrong to result in this kind of experience.

Anyways- ending my rant. I know a DAW like S1 is one of the most complex and difficult software engineering challenges, and I know Presonus is working hard. Hope I get to enjoy that hard work sometime in the future!

bewiggins5 wroteHey guys- I need some advice. Revisiting S1 today to see if stability has improved, and in the past 4 hours, it has crashed 27 times. Stability seems worse than the last time I tried a year ago. Some examples of issues I'm dealing with today:

• Midi notes constantly getting stuck
• Undo history randomly dropping
• Desync between tracks and the mixer (muting a track in arrangement view does nothing until muted in the mixer window)
• Crash when moving a midi region with chord-track follow enabled
• Crash when closing a vst window
• Crash when inserting a midi note in the piano roll
• Crash when zooming in
• Crash when bypassing an audio effect
• Crash when breathing too heavily / when cat sits on keyboard

My plugins/OS are all up to date, work fine in other DAWs, my machine has 64GB ram and is quite beefy, and I've made sure to kill all other processes not related to S1 when debugging, etc. I suppose my questions would be:

1. Is this level of instablity common? Should I come back in a couple more years? (it has been hit-or-miss in my experience over the years)
2. Is this because I'm on Mac? Is S1 more stable on Windows or Linux?
3. Is there a stable version I should be using?
4. As an OSS developer, is there any way I can debug my constant issues / run devtools / run from cli with logs? Reading crash logs always shows the same malloc errors (EXC_BAD_ACCESS (SIGSEGV)[/b], [b]UNKNOWN_0xD at 0x0000000000000000)
5. Does S1 need to be re-written in a memory safe language like Rust? (joking but man wouldn't that be sweeeet)
6. BBCode... really? No Markdown? (ok still joking I'll stop )

Unfortunately, I don't really have the time to make repros/tickets for the constant bugs I encounter when making a new song. Not to mention, there seems to be no public bug tracker to avoid wasting time reporting known bugs (just open source S1 Presonus it's 2022 and you would become unstoppable ).

Studio One is, in my opinion, one of the most well-designed and feature-rich DAWs on the market. If I could actually use it, it would be my favorite by far, and I use them all. I suppose I'm just wondering if there is hope, and/or if there's something I'm missing / doing wrong to result in this kind of experience.

Anyways- ending my rant. I know a DAW like S1 is one of the most complex and difficult software engineering challenges, and I know Presonus is working hard. Hope I get to enjoy that hard work sometime in the future!

I would say this is better off on your own new thread for troubleshooting or discussion, this thread could throw off in a different direction otherwise, please update your signature with full specs. Also please include your full error messages from the logs.

One thing I would say, not many are experiencing these issues otherwise there would be lots and lots of posts like this constantly. It's impossible really to tell what you issue is with this information, it could be for instance a permissions related issue. You may want to consider a full reinstall of your OS (it appears environmental, but that's just an out of the blue suggestion (a guess) with not much to go on)..another thing to try in a new project with blank template and see if you get issues with that.

As a developer you will appreciate any bugs cannot be quashed easily without full steps to repro and ruling out third party plugins.

Crash when moving a midi region with chord-track follow enabled
Crash when closing a vst window
Crash when inserting a midi note in the piano roll
Crash when zooming in
Crash when bypassing an audio effect
Crash when breathing too heavily / when cat sits on keyboard

There's something seriously wrong on your end. Studio One does not crash when closing a window, inserting a note or bypassing an effect. There must be either incompatible drivers or plug-ins involved.

My plugins/OS are all up to date, work fine in other DAWs, my machine has 64GB ram and is quite beefy

If they aren't compatible with Studio One and crash, then it does not matter if they are up to date and work fine in other DAWs.

But this requires more details. Which plug-ins do you use... which plug-in formats do you use? Do the same things happen if you don't have any 3rd-party plug-ins in your song?

You should really create a new thread for this.

Just one last tip: Do you use AU plug-ins? Don't use them in Studio One Use the VST 3 or VST 2 versions and see if that makes a difference. There are manufacturers that don't test their AU plug-ins in Studio One.

One thing I would say, not many are experiencing these issues otherwise there would be lots and lots of posts like this constantly.

There's something seriously wrong on your end. Studio One does not crash when closing a window, inserting a note or bypassing an effect. There must be either incompatible drivers or plug-ins involved.

This is what I was hoping to hear! I'm certainly not expecting anyone to diagnose my issues with the given information, just trying to paint a picture to see if it's just me or not. Though based on what you're saying, starting a thread to get to the bottom of my issue sounds like a good idea. Thanks!

Do you use AU plug-ins? Don't use them in Studio One Use the VST 3 or VST 2 versions and see if that makes a difference. There are manufacturers that don't test their AU plug-ins in Studio One.

Haha no AU's, I avoid those! Not being able to collab with artists on windows machines just because I clicked AU instead of VST is a mistake I made once.. never again. I try to stick with VST3 where possible.

Update: Nothing new here, but I've been working on editing some V-Drum tracks lately and it would appear that the stuck MIDI notes issue (BIGFOOT) is resolved, at least insofar as it affected me.

Scientific proof that prayer does work.

Not sure where to post this exactly but felt like I wanted to say it...

I recently got into music production, let's say on and off for about a year. For some reason I landed on Studio One as my first DAW.

Now, after having used a couple of versions I can say that on a fairly regular basis I am experiencing crashes, bugs and glitches.

I'm already struggling to produce/compose and learn a million things at once, yet I am spending at least 10% of my time trying to troubleshoot or fix problems that occur. Just recently I am opening a track and none of the MIDI as well as some, just SOME of the audio clips are not playing. Well, they are playing, and giving signals, but there is no sound.

It was working just fine yesterday, I made no changes or updates and now it just doesnt, it's things like this that really gets my goat.

Considering all this, even though it would be a MAJOR hassle to transition to another DAW, what with the songs and projects I already have and the things I need to learn again, I'm starting to think I will take my chances...

My creative juices are just too damn low from all this and although I really want to like Studio One, and I do when it works, I believe other DAWs are more stable in this regard.

I dont know, just wanted to vent a little and see if maybe someone else is experiencing similar issues.

Regards

ericstenstrm wroteNow, after having used a couple of versions I can say that on a fairly regular basis I am experiencing crashes

Sounds - as almost always - like a plug-in issue.

You don't provide any details about your system and 3rd-party plug-ins you use so it's hard to help you based on that information (I'm assuming, of course, that you're looking for help).

- Are you on Windows or Mac?

- Are all your 3rd-party plug-ins up to date?

- Do you experience the same crashes and glitches when you don't use any 3rd-party plug-in?

- If you're on Mac, do you use AU plug-ins? If so, you should replace the with the VST2 / VST3 variant.

- Did you submit a ticket to Tech Support so these issues can investigated further?

Well Im not sure if Im looking for help or just venting and wanting to see if I am the only one experiencing lots of bugs n crashes in general.

It's very possible I have made a major mess of my installation paths and search folders and whatnot. Very possible indeed. Still.. If you will kindly note this comment: "It was working just fine yesterday, I made no changes or updates and now it just doesn't, it's things like this that really gets my goat."

Its Windows 10, I don't know how to check if plugins are up to date. There's a whole lot of 'em though..

If you're just starting out and you don't really know what you're doing, you should just be working on the fundamentals of learning how to get a workflow happening and not trying to win the competition for who can amass the most plugins. "Oh look, this one's free, too...maybe I'll try it."

I'm assuming that you fell into the same trap that we all do at the start where "More means more!" In among all those plugins are usually a lot of poorly written ones that can be temperamental and unpredictable. Maybe this is the issue.

Also, do you have an audio interface or are you using whatever the system throws at you? That can be a weak point, too.

There are things about Studio One that can make it crash - it's usually a couple of known bugs that everybody then writes about on this forum. It sounds to me like you've got nothing but bugs and that's not the Studio One experience. If my system was crashing all the time, I'd become an investment banker and move on.

I believe your inexperience has led you to the edge of the abyss in terms of stressing your system. And unless you have the technical experience, you shouldn't just lash out and suggest that other systems would be more stable. That's just an emotional reaction not based on fact.

I'm often a hand holder, but in this case I think you need to retrace your steps. Probably reinstall Studio One and dump a lot of your broken, useless plugins that I'm assuming you picked up along the way.

If I'm wrong about this...it's your fault.

ericstenstrm wroteWell Im not sure if Im looking for help or just venting and wanting to see if I am the only one experiencing lots of bugs n crashes in general.

It's very possible I have made a major mess of my installation paths and search folders and whatnot. Very possible indeed. Still.. If you will kindly note this comment: "It was working just fine yesterday, I made no changes or updates and now it just doesn't, it's things like this that really gets my goat."

Its Windows 10, I don't know how to check if plugins are up to date. There's a whole lot of 'em though..

roland1 wroteIf you're just starting out and you don't really know what you're doing, you should just be working on the fundamentals of learning how to get a workflow happening and not trying to win the competition for who can amass the most plugins. "Oh look, this one's free, too...maybe I'll try it."

I'm assuming that you fell into the same trap that we all do at the start where "More means more!" In among all those plugins are usually a lot of poorly written ones that can be temperamental and unpredictable. Maybe this is the issue.

Also, do you have an audio interface or are you using whatever the system throws at you? That can be a weak point, too.

There are things about Studio One that can make it crash - it's usually a couple of known bugs that everybody then writes about on this forum. It sounds to me like you've got nothing but bugs and that's not the Studio One experience. If my system was crashing all the time, I'd become an investment banker and move on.

I believe your inexperience has led you to the edge of the abyss in terms of stressing your system. And unless you have the technical experience, you shouldn't just lash out and suggest that other systems would be more stable. That's just an emotional reaction not based on fact.

I'm often a hand holder, but in this case I think you need to retrace your steps. Probably reinstall Studio One and dump a lot of your broken, useless plugins that I'm assuming you picked up along the way.

If I'm wrong about this...it's your fault.

ericstenstrm wroteWell Im not sure if Im looking for help or just venting and wanting to see if I am the only one experiencing lots of bugs n crashes in general.

It's very possible I have made a major mess of my installation paths and search folders and whatnot. Very possible indeed. Still.. If you will kindly note this comment: "It was working just fine yesterday, I made no changes or updates and now it just doesn't, it's things like this that really gets my goat."

Its Windows 10, I don't know how to check if plugins are up to date. There's a whole lot of 'em though..

Absolutely this! It's amazing how many plug ins one can amass. In many times though, what it all comes down to is most of the time, you have plug ins upon plug ins that do the same thing as other plug ins you already have. Sure, they may have different or even better presets, but ultimately, they do about the same thing. Yes, some compressors sound better than others. Yes, some reverbs are better than others, but still...there are a LOT of plug ins that essentially do the same thing.

I have Waves Mercury. That's a lot of plug ins. I also have a good # of Izotope plug ins. Along with the Presonus built in plug ins, there probably isn't much I can't do. However, I find myself only using the same 5 or 6 plugins on a regular basis. Once in a great while, I pull up one that I don't use often, but honestly....I could probably get by on just the built in Presonus ones. (Though I really, REALLY love my CLA Plugins from Waves)

Quietly wrote

weswild wrotewhy does it crash so much ? i turned of auto save , my computer does nothing but studio one . plugins are up to date which took ages . windows i7 16gb ram no heavy processes just small projects but really random freezes . love this software so much but its the most buggy i have ever experienced . seems with every update it gets worse . frustration

Confirm I have had a couple of crashes when dragging an FX into a track during play back. I accept with only 4gb ram it might be expected but it never ever happened before. Anyone else noticing more freguent crashes with 5.5.2?

I can also confirm a lot more crashes. This can be reproduced with a 50/50 chance when I disable, and then enable an instrument track.