Hello,
I'm experiencing some problems whenever I change the dropout protection from Medium to any higher value. The same happens if I change the buffer size of the interface, from 512 (my standard value) to any higher value. I hear clicks and pops that are quite annoying. Any ideas? I remember that some time ago this was not a problem and my setup is still the same.. Maybe some recent updates have caused some problems? Thanks
Presonus Featured Artist (Italy)
My Latest Feature Requests https://answers.presonus.com/73692/s1-essential-feature-plugin-racks https://answers.presonus.com/72506/zoom-to-selection-improvement-vote-if-you-agree Studio One Pro 6 Win10 - AMD Ryzen 9 5900X - 32gb ram DDR4 Gigabyte RTX 3060 Interface: Focusrite 18i20 3rd gen Prophet XL + KeyStep Pro Atom SQ Revelator |
Can anyone help? Thanks!
Presonus Featured Artist (Italy)
My Latest Feature Requests https://answers.presonus.com/73692/s1-essential-feature-plugin-racks https://answers.presonus.com/72506/zoom-to-selection-improvement-vote-if-you-agree Studio One Pro 6 Win10 - AMD Ryzen 9 5900X - 32gb ram DDR4 Gigabyte RTX 3060 Interface: Focusrite 18i20 3rd gen Prophet XL + KeyStep Pro Atom SQ Revelator |
Two things
1. Since it's just cropped up, look at your CPU meters individual activity by clicking on it. Select to view all plugins, and sort by clicking percentage column. See if any high percentage plugins or instruments are high. They might read 30% which is high for one instance. So proceed as necessary comparing individual items with highest percentages. If the overall CPU activity meter is at 70%+, that can be high. Such high readings can tax the audio interface or driver and cause clicks/pops. A remedy then if found to be high percentage is render to audio, consolidate as needed. 2. If the CPU meter is somewhat low, as below 50%, then you have to observe buffer settings, latest drivers updates, as well as tracing your audio signal which might have routing issues. Included in #2 is outside streaming, or background activity raising your CPU. Even (not to be ignored) your hard drive eventually being full to perhaps 80% to 90%. So check both your task manager system performance, RAM activity %, along with hard drive space remaining. Silly, but verify your audio is set to your Focusrite, and not accidentally to the internal PC audio or some background audio setting you may have recently set. Hey, it happens.
S1-6.2.1, HP Omen 17" i7 10th Gen, 32 GB,512 GB TLC M.2 (SSD),1 TB SSD. Win10 Pro, Audient iD14 MkII, Roland JV90, NI S49 MkII, Atom SQ, FP 8, Roland GR-50 & Octapad. MOTU MIDI Express XT. HR824, Yamaha HS-7, NS-1000M, Yamaha Promix 01, Rane HC-6, etc.
New song "Our Time" https://youtu.be/BqOZ4-0iY1w?si=_uwmgRBv3N4VwJlq Visit my You Tube Channel https://youtube.com/@jamesconraadtucker ... PA5dM01GF7 Latest song releases on Bandcamp - Latest albums on iTunes All works registered copyright ©️ |
Just to keep things in perspective, there is always a possibility that this is the fault of Studio One.
In which case, don't change the settings. And hope for a fix with the next release. [Drop out protection has been a bane for many people since it was introduced.]
Studio One Pro (v5) on i7 7700 win10 PC w16GB RAM and a Mac Pro Tower (w/RME & Focusrite interfaces.)
I use S1 as an author/musician/multi-media artist. My work includes the newly released: Clearing a Path to Joy (And finding contentment along the way) [AuroraSkyPublishing.com] and my upcoming music video, Too Big To Fail, which introduces Citizen Based Social Planning — "the next step in the evolution of democracy." You know...typical everyday stuff. |
kisnou wroteCan anyone help? Thanks! One hint I can offer is to remember that higher Dropout Protection means any track you are not actively monitoring is running on a higher buffer. Some plugins perform really poorly at high buffers. Not many, but some. A lot of times that poor performance won't show up on the CPU Activity meter because it's the plugin internally messing up. If it's not a specific plugin, then maybe look for something routing related. When they added Multi Instrument core-sharing there were some situations where Multi Instruments would make all kinds of terrible noises at high buffers. It didn't show up on the CPU Activity meter either. They fixed that bug, but I'm mentioning it as an example of places to look. |
Users browsing this forum: gregghart and 55 guests