• 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!

Crackles and pops on two different Macs with Studio Pro 8

O

OFS

Member
Hello. I've been trying a few v7 sessions since yesterday and many that worked perfectly in s v7 are now constantly causing clicks and pops on playback and sometimes even when stopped.

I see no red light warnings on the CPU meters

Happening in two Macs, a M5 Pro and a Mac Studio M2 Max.

Anyone experiencing this behavior?

Thanks!
Miguel Barrosa
 
Yes, happens here too.
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
This advice only applies to the Mac. OFS, according to your sig, you're not on the latest version of 7. IF that's the case, something that happened (IIRC) after that release is that Studio One allowed the use of efficiency cores, which is settable by a new pref (can't remember where) and defaults to ON. In my case, I all of a sudden ended up with spikes like you describe. I turned that pref to off, and all returned to normal. I'm sure the same "Enable efficiency cores" default would be set in Studio Pro 8.

Running Studio One on the efficiency cores that are shared by virtually all other apps isn't necessarily a good strategy if you're using low latencies, and you have a sufficiently powerful machine. For others who want more processing for plugins and are willing to deal with bigger latencies, using efficiency cores can help.

Of course, none of this would apply to the Risen, and may have nothing to do with your Mac issue...
 
I get this exact same issue. On all sessions, disabling FG-Stress resolved this. 7.2.3 however it works perfectly.
 
I’m experiencing the same issue. It happens with Slate Virtual Tape Machine. When I turn it off, everything sounds normal, but the program still crashes after a few seconds. I also experience crashes when I try to do anything with Superior Drummer 3 and Sonarworks SoundID Reference.
 
I think I may have found a solution, and Virtual Tape Machine seems to be the cause of everything. It’s not enough to just turn off or bypass the plugin. It has to be blacklisted so it doesn’t load at all when Studio One starts.
 
Good spot! Slate FG-Stress (which i've seen is the cause in my case) however is an important plugin for my template so really do not want to have to block it/replace it. I'll stick with 7.2.3 in the meantime until theres a resolution
 
FMN-Music said:
Yes, happens here too.
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
Click to expand...
Hey @FMN-Music thanks for the feedback.

If you recall this thread https://studiooneforum.com/threads/...ivating-a-sidechain-on-a-plugin.430/post-3705 , you gave me a workaround for the problem where activating sidechain on plugins created out of sync audio playback in certain sessions.

The first thing I tried with v8 was to open a test session which had those sync problems (which I've sent to tech support a long time ago) and I was ecstatic that they've fixed that problem! Activating the sidechain on the plugin in my session had no ill effect whatsoever in the synchronisation of the audio.

However my enthusiasm went down really quickly since then because many of my perfectly working sessions from v7 are now crashing on opening or having cracks and pops in the audio. It's a pity and let's hope it's just x.0 blues at play.

But as it stands now unfortunately, at least for older sessions, this version is practically unusable.
 
js1 said:
This advice only applies to the Mac. OFS, according to your sig, you're not on the latest version of 7. IF that's the case, something that happened (IIRC) after that release is that Studio One allowed the use of efficiency cores, which is settable by a new pref (can't remember where) and defaults to ON. In my case, I all of a sudden ended up with spikes like you describe. I turned that pref to off, and all returned to normal. I'm sure the same "Enable efficiency cores" default would be set in Studio Pro 8.

Running Studio One on the efficiency cores that are shared by virtually all other apps isn't necessarily a good strategy if you're using low latencies, and you have a sufficiently powerful machine. For others who want more processing for plugins and are willing to deal with bigger latencies, using efficiency cores can help.

Of course, none of this would apply to the Risen, and may have nothing to do with your Mac issue...
Click to expand...
Thanks for the reply. My signature was out of date but the software (DAW's and plugins) are all fully up to date. I'm pretty OCD about regularly checking and installing updated plugins.

I tried disabling the efficiency cores but I'm unable to open the session, it just crashes on opening...

As for the Slate thing, I'm not using FG Stress. I don't use any of their plugins except for Trigger 2.
 
OFS said:
The first thing I tried with v8 was to open a test session which had those sync problems (which I've sent to tech support a long time ago) and I was ecstatic that they've fixed that problem! Activating the sidechain on the plugin in my session had no ill effect whatsoever in the synchronisation of the audio.
Click to expand...
Yes, there seems to be an improvement. It's not out of sync after loading a song anymore.. But I can still get the sync to fail by moving latency-inducing plugins around on the Bus with the Sidechain Comp on it. It fixes itself after turning plugins off and on again, though.
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
FMN-Music said:
Yes, there seems to be an improvement. It's not out of sync after loading a song anymore.. But I can still get the sync to fail by moving latency-inducing plugins around on the Bus with the Sidechain Comp on it. It fixes itself after turning plugins off and on again, though.
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
Click to expand...
Wow that’s a really clear demonstration of the issue! If you have time and patience I’d suggest sending that session file to PreSonus …sorry, Fender tech support. I think they’d like to know about it
 
That's a battle to be fought by someone else.
In my experience they'd rather not know about latency compensation issues. :-)
 
FMN-Music said:
That's a battle to be fought by someone else.
In my experience they'd rather not know about latency compensation issues. :-)
Click to expand...
I understand. This type of stuff is probably hard to fix. I would like to believe they would be willing to tackle the problem though...
 
You must log in or register to reply here.
Back
Top