#Presonus studio one 3 pro keygen windows

Unfortunately, I don't really have the time to make repros/tickets for the constant bugs I encounter when making a new song. really? No Markdown? (ok still joking I'll stop ) Does S1 need to be re-written in a memory safe language like Rust? (joking but man wouldn't that be sweeeet).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), UNKNOWN_0xD at 0x0000000000000000).Is there a stable version I should be using?.

#Presonus studio one 3 pro keygen windows

Is this because I'm on Mac? Is S1 more stable on Windows or Linux?.

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).

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. Crash when breathing too heavily / when cat sits on keyboard.Crash when inserting a midi note in the piano roll.Crash when moving a midi region with chord-track follow enabled.Desync between tracks and the mixer (muting a track in arrangement view does nothing until muted in the mixer window).Some examples of issues I'm dealing with today: Stability seems worse than the last time I tried a year ago. Revisiting S1 today to see if stability has improved, and in the past 4 hours, it has crashed 27 times.