• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Solved Studio One Freezing - Presence MIDI Track

R

reginaldStjohn

New member
So this weekend I was recording some vocal takes with a friend. After he left I started to comp the takes and Studio one started freezing at times. The only way to get it back was to kill it with task manager.

I tried starting the projects with all options off ( no VST3, VST, windows audio ect) and it would still freeze.

I noticed that the freeze happened when I would scroll up where my midi tracks were (Kontakt and Presence)

Things got so bad at one time I couldn't even open up the project if the midi tracks were visible when last saved.

I found a version I could open, deleted presence and it midi tracks and then it would not freeze.

I have a support ticket in with Presonus but I doubt there going to have an answer for this one. Probably a corrupted project or install file somewhere.

Just checking if anyone has seen or experienced something like this.

-----------------------------------------------
Windows 11 Pro, Ryzen 5 CPU, 32 Gigs Ram, 2x1TB drives, Behringer x32 Producer Mixer/Interface, Studio One 7 Pro
 
Just an update for those who may at some time have a similiar experience. No solution yet. Support had me try to unistall my video driver, use the default windows one. No change. Seemed like a long shot anyway. Waiting to here back if they have some other suggestion for me.
 
Download, install and run the following program to see if your computer is suitable for processing real-time audio and other tasks.

LatencyMon
 
Trucky, Thanks for the suggestion. I have suggested this to many others as well.

I have run this many times and I keep my system in the green. On my last machine I had problems with latency and running Latency Monitor revealed it to be an NVidia driver issue. I could never fix it so I switched video cards to an AMD and the problem went away.
 
That's good that you've confirmed that it currently passes the LatencyMon test.

Are you having the same "freezing" issue with new songs?
Your signature lists "Studio One 7 Pro". I'd recommend updating to 7.1.1.
 
Ok, Updated my signature. Seems to be still freezing. Still working with Support.
 
No problems with new songs or even a "salvaged" version of the current song. As long as I was able to remove Presence and it associated midi tracks then it has worked fine. If I leave Presence in the song or the midi tracks then when I attempt to scroll or edit anything with those midi tracks visible it freezes. I have Kontakt in the project as well and it seems to be fine with those midi tracks.
 
OK. Sounds like the song is corrupted and nothing wrong with your computer.
 
That would be my guess.
 
Is your computer and audio gear connected to a conditioned power source with battery backup?
It's a real gamble and risk without it.
 
My computer is connected to conditioned and sequenced power (Carvin AC120S). It is not battery backed up. It is not on that much, just in the evenings when I am working on it. I do back my projects up nightly to an external NAS server.

Support is having me create a new song and then import song data from the corrupt one to see if I can tell anything more. At this point I already have a copied I recovered and works so I am just doing it to see if there is any Bug to be reported or if it is just a case of a random, unexplainable, corruption.
 
Glad to hear that you were able to locate a backup and that Support provided a workaround alternative to rebuild it.
 
I feel your pain. I am glad you got it going again.

I have had at least two tickets in for freezing issues and both times Support had me either reinstall Studio One or remove the "Studio One.settings" file. The latter is a little more palatable and usually fixes the problem. The freezing in my case has been a long-standing issue since v5 and on 3 different PC builds. My gut keeps telling me it related to memory management issues in Studio One but it is hard to tell exactly. The two facts that Studio One sits around in the Task Manager for so long after a crash, or takes so long to unload memory on a large session supports this gut feeling. My sessions are usually 15-30GB in RAM size (sample libs). Also until Studio One is fully unloaded from Task Manager, the "Studio One.settings" file is not written to. I find that if it crashes, it can sit in Task Manger for up to 3 minutes and is unkillable (I don't even attempt anymore). I'm not sure if the .settings file is open or not at that time, or if at the end of the process it gets opened, but for some reason, removing the file seems to work. It is just an XML file, so it is not like a binary where it would be harder to find the point of corruption; yet, comparing a "good" XML file to one that is causing the freezing file doesn't yield many clues.

Anyway, since I don't like losing settings, before I start a big project (like months long stuff), I make sure I backup a copy of the ENTIRE Studio One 6 (or 7?) folder located at: <user> -> AppData/Roaming/Presonus/Studio One 6. If I get the sort of freeze you describe, I either 1) just replace the Studio One.settings file in the root of that directory with my backup one, or failing that 2) replace the entire directory with the backup. This has gotten me out of a handful of binds.

-John
 
Thanks parityflux. I will look into that.
 
Sure! One anecdotal question: When you were recording those vocal takes, did you in any way, adjust your metronome (besides turning it on or off)?
 
You must log in or register to reply here.
Back
Top