PG Music Home Forums General Discussion Help! Tech S.O.S (Off topic) Studio One Randomly Freezes [Resolved]

Anyone else having freeze-up problems?

I have version 7.02 on Win 11 and out of the blue and randomly it freezes and won't play an audio file of a song I'm trying to learn. So the workspace is as simple as it gets with just an MP3 file dragged in. The mouse cursor changes to the circular activity icon and although I can execute commands from the menus, there is a long delay (a second or two) between clicking the item and it executing that item.

I'm thinking it may be related to it "phoning home". The last time it ocurred I popped over to my email tool and it took a few seconds to refresh it. But after refreshing I went back to S1 and it hadn't regained it's mind. It's as if whatever anomaly ocurred causes it to latch into an unresponsive state.

While in this unresponsive state, the Task Manager tells me that S1 is using between zero and 1% CPU.

Hmmm. Well, Presonus closed all of their forums(!!) a few weeks ago. Subsequently, a user community has started up here.

A quick scan only found some information about 13th and 14th generation Intel processors needing a BIOS update to prevent crashing.

A deeper look at the forum posts may be warranted, assuming you haven't already.

Know these can be frustrating, hope it resolves soonest. Good luck!

I have Studio One Pro 7.02 with Windows 11. I was playing around today with a song I am working on, but I have not come across anything wrong. I am also connected to the internet as well and there is no delay with my email.

I haven’t seen this.

My first thought reading your post was something running in the background, but that’s not it if your CPU usage stays that low.

The only thing I’ve read that comes closest is that it’s a malfunctioning plugin. Do you have any trial - unregistered plugins?

I have had Studio One 5 Pro freeze a couple of times, and that seemed to be related to plugins. I just downloaded 7 and have had no issues after using it ten or fifteen times.

The crashes were few and far between. Sonar used to crash once in a while.

As I remember some of these issues came shortly after a Windows update.

I have never come up with a solid reason. It has happened only perhaps three or four times in my total history with Studio One.

Only once did a crash occur when I was about thirty tracks into something. That taught me a lesson and I now save frequently.
None of my standalone music software like Toontracks or Guitar Rig Pro has ever crashed. Well, BIAB has crashed once or twice over the years.

I do not ever remember having any sort of crash soon after cleaning up my drives and getting rid of junk.

I assume doing good housekeeping helps to reduce these issues. I use third-party software to scan the register which has worked well for me.

My best guess is plugins/software. I have at least 400 gigs of NI/Toontracks/Melodyne/ AutoTune and other assorted software.

None of this may be related to your issue thumper. I don't have a rocket ship but i9-9900 3.60 32 gigs RAM good SSD water cooling ect, so I don't think any crashes I have had are due to inadequate system hardware.

I would go look at your event log and also do some housekeeping and see if that helps. I have had pretty good luck with CleanMyPC. (chkdsk c:) if I remember correctly( f switch to auto fix) Do a disk check at the command line. Take a good look at the physical USB connections. They sometimes get worn if you use them a lot and can cause a disconnect and reconnect. With the machine off/unpluged move them in and out to remove oxidation on the contacts.
The chkdsk Command should return something like this



C:\Windows\System32>chkdsk c:
The type of the file system is NTFS.
Volume label is DISK 2 970 EVO.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
1005824 file records processed.
File verification completed.
Phase duration (File record verification): 5.58 seconds.
33478 large file records processed.
Phase duration (Orphan file record recovery): 14.88 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.15 milliseconds.

Stage 2: Examining file name linkage ...
3052 reparse records processed.
1384476 index entries processed.
Index verification completed.
Phase duration (Index verification): 17.39 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 1.28 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.18 milliseconds.
3052 reparse records processed.
Phase duration (Reparse point and Object ID verification): 10.58 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 283.07 milliseconds.
189327 data files processed.
Phase duration (Data attribute verification): 0.95 milliseconds.
CHKDSK is verifying Usn Journal...
36820408 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 82.53 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

972383283 KB total disk space.
838133440 KB in 491202 files.
435888 KB in 189328 indexes.
0 KB in bad sectors.
1366571 KB in use by the system.
65536 KB occupied by the log file.
132447384 KB available on disk.

4096 bytes in each allocation unit.
243095820 total allocation units on disk.
33111846 allocation units available on disk.
Total duration: 24.66 seconds (24665 ms).

C:\Windows\System32>

The event viewer is a pretty deep rabbit hole. I have a CCIE friend to get to log on to my machine if I have real problems.

Happy Holidays,

Billy

Thanks to all that have replied.

Ron, The first thing I did was go out to the Presonus forum and it looked like the last post was from Aug; very strange. And now you confirm that they shut down their forum. What are they thinking??? Could this be my first real disappointment with Presonus?

But now after restarting my computer I'm getting a sample rate mismatch error message. Upon investigation I see that somehow the setting for the digital interface got changed from my Tascam to Realtek. I have no idea how this got changed. I certainly didn't change it. And I only got the sample rate error message this morning but my problem has existed for a few days. Thinking about this, it seems to make sense why no audio would play at all but that I did have very sluggish command response. I changed it back to my Tascam and things [so far] are working properly.

Brian, yeah, my issue is/was sporadic.

Matt, I have no trial plugins. Actually, as far as plugins go, I'm fairly "clean" with just 2 installed; Scaler and Ascension; neither of which were active in my workspace.

Billy, I haven't had time to read your post but I will.

So far, my system seems to be running stable but I am curious as to why and how the setting for my interface got changed and why it took S1 so long to give me a sample rate error. Maybe the root cause was a Windows update that somehow changed the setting.

As I continue to learn a new bass line later today, I'll be looping sections of that audio file which will further test its stability.

Hey Billy,
You provided quite a trove of info. Much appreciated.
Lo and behold I discovered "Event 1002" associated with S1.
My theory is that during the 7.0.2 upgrade, somehow my digital interface setting reverted to the default Realtek and that's what messed me up.

Now with my engineering hat on (us enginers maye nut be uble to spel but ulways loking to impruve thungs ) I'm thinking Microsoft should design a small, local and smart application that would monitor and digest the Event Log records and provide actionable info like:

"Steve, based on your recent download of Studio One 7.0.2, Event 1002 ocurred. System instability is expected and you should verify that your audio interface settings in Studio One are still valid."

To Microsoft: I'm available part time to provide consultation . . . but full disclosure, I'm mighty expensive.
To Presonus: Please restore your online forum ASAP.
To Billy: Happy Holidays to you too man and happy event logging.

BH.

when all is working well best to take pics of...

..win audio settings for rec and playback and advanced tab also.
..interface settings
..music apps driver settings eg bb or rb or another daw app.

less hassle that way.
(see my tips in tips forum...might be usefull.)

hth/merry x.

om

As far as utility programs go I used to use CC Cleaner for a long time but Microsoft now has its own tool called PC Manager that is free and does a fine job.
Microsoft PC Manager

Steve, I have had Window updates as well as Nvidia updates change my audio interface settings. Windows to Realtek and Nvidia to their audio. It can be a PITA. However just to be safe I would do a full anti-virus and a anti-malware scan.

Update and possible root cause.

My Studio One problem still exists and a thought came to me, could Guitar Pro be the problem. So I shut down GP and lo and behold, the circular activity mouse icon in Studio One changed back to the normal pointer and full functionality returned.

So then I queried my AI assistant and it gave me this.
Yes, Guitar Pro can sometimes cause issues with other programs that use the same digital interface. Users have reported that when Guitar Pro is open, it can interfere with other applications that use the audio driver, such as Skype, Zoom, or even YouTube. This is often due to how Guitar Pro handles audio drivers and its interaction with the system's sound settings.
Here are a few tips to mitigate these issues:
1. Use ASIO Drivers: If you're not already using ASIO drivers, consider installing them. ASIO4ALL is a popular choice that can help manage audio routing more effectively.
2. Check Audio Settings: In Guitar Pro, go to the "Audio/MIDI Devices" settings and ensure the device is set to "Standard" instead of "ASIO" if you're experiencing conflicts.
3. Virtual Audio Cable: Using a virtual audio cable program can help with routing audio between different applications.
4. Consistent Sample Rates: Ensure that all your audio applications are set to the same sample rate to avoid conflicts.
These steps should help you manage any potential conflicts between Guitar Pro and other programs using the same digital interface.

Item 2 may be relevant because that setting in GP is set to "ASIO" but I'm planning to change it to "Standard" as it suggests.

I'm not claiming victory quite yet, but I think I'm getting close. Either way, hopefully this thread will be of use to someone else in the future.

And holey mackrel! The more advanced technology becomes, the more advanced the problems!

AI diagnosed that? I need to pay more attention.

Let's hope the AI is correct. This is one of the really useful functions that AI could provide.

I have asked questions like that and it has returned plausible nonsense. But, it is also correct at other times.

Let us know if AI is on the right track.

Billy

Matt and Billy,
Yeah, on the one hand I'm quite impressed with what AI can produce, but on the other hand, if you or I had first hand and instant access to the TBs of info on the internet then we too could produce answers like it can. At sometime, a number of GP users complained on some message board that it can interfere with other software that uses the same digital interface. The LLM I'm using simply was trained on that scraped info.

A few weeks ago I saw a plot in a technical paper that showed how the gap between all the info the internet has (and will have) and the amount of info that LLMs have been trained on is rapidly narrowing. And for reasons I don't yet understand, computer scientists are concerned that they are running out of new training data.

Keep in mind, ChatGPT is not even 5 years old yet.

I say having no more new training data is a good thing because the LLM is complete. And completeness is good, but there must be more to the story.

BT.

whats your interface ??

are you running multi client asio drivers ?

see my multi client sound/interfaces that are MC... tips thread in tips forum for more info.
might be usefull.

merry x.

om

Studio One does have a "Release Audio Device In Background" checkbox. You might want to have a play around with that setting. Also do the sample rates of both programs match?
Also no matter which interface you're using, temporarily change to "Windows Audio", open the "Control Panel" and UN-check the "Exclusive Mode" check box.
Change your settings back to your interface and in most cases it will allow other apps to use the interface while S1 is open and/or playing audio.

I don't know if this will fix your issue but might be worth a try.

Good idea Brian. I remember that Studio One gives advice on that setting. I don’t remember now what it is, because I set it once and haven’t looked again. In years past, SONAR did the same thing

JAOM, I have a Tascam Series 208i that has served me well for years.

As for the tips forum, I don't know where that is located. You didn't supply a link.

And please take no offence, but if it lacks proper punctuation and capitalization, I can't read it.
Such writing litterally gives me a head ache after the 3rd sentence.

That said, I do believe I've reached a solution, with GP as the culprit.
A few more days of Studio One usage should tell me yes or no.

BT.

if your tascam is old i suspect its not multi client.

i'm surprised youve never seen the pg tips forum...

heres the pg tips forum...loads of neat tips from lots of pg users.

https://www.pgmusic.com/forums/ubbthreads.php?ubb=postlist&Board=31&page=1

and heres the usb interface/multi client thread...
lots of views so obviously some people read it.

https://www.pgmusic.com/forums/ubbthreads.php?ubb=showflat&Number=718708#Post718708

for example my audient usb interface is multi client asio.
see the thread for more info about multi client and pg users that use it.

if in doubt if an interface is multi client asio contact the manufacturer..
ie in this case tascam.

ps...lol...pg tips is a tea brand in uk.
om

I’m not sure exactly what you mean by “multi-client”. The website or user manual doesn’t seem to specifically mention “multi-client”.

But this little guy has all the ins and outs I need and can seamlessly move from playing a YouTube on headphones, to recording my instruments in Studio One while playing a backing track, to playing a Guitar Pro or BiaB file, to playing an audio file via a media player, to playing my keyboard thru monitor 1 while playing a backing track thru monitor 2. In short, this interface has handled virtually every audio task I’ve thrown at it. It can even receive a mic for recording. It’s a serious piece of gear and still available for purchase.

But like I say, Guitar Pro appears to be the root cause of my problem, not the interface.