![]() ![]() I have been in touch with support and they assured me that the problem wasn't common and it all related to macOS 10.13.2 - the strange thing is when my system was using macOS 10.13.2 I didn't get any problems with clicks and pops using Logic Pro etc. The only way I could stop it from happening was to downgrade macOS to 10.13.1 - this cured all the pops and clicked etc. I'm on macOS and as soon as I updated to macOS 10.13.2 the clicks and pops started happening, and the CPU meter was showing 15 % average usage when using virtual instruments. I've had to put all my projects on hold until I can figure out why this is now occurring. It's not CPU, Low latency monitoring, block size, drop out protection, etc. As soon as I updated I began getting these "random" artifacts in the VI signal. Have you still had success with this not returning? I am once again being plagued by pops/clicks with VI's inside 3.5.4. The only thing I do also remember is that I did a reboot of my computer - perhaps that did something, as I was getting the constant glitches / crackling, then at some point I decided to reboot, and since then everything has been fine. I also wonder if something has changed with Windows 10 and/or my audio drivers as well perhaps. I thought that might be it, but it seems fine. In the meantime I have investigated my usb ports in use (using software to view USB devices and by connection), and all my usb devices are on their own ports / hubs so to speak, it showed no usb device was sharing a hub with any other device. I hope to try and track down whatever it is. Yes, I don't know what is going on, it is a concern. I am going to roll back S1 to an earlier version just to see if I can get an older version of S1 V3 that is fine, and I will post back here. ![]() I noticed the "Dropout Protection" setting - it was set to minimum, so I tried a few other settings with no improvement there either, although I did see the CPU usage go from 1 to 4% as I increased the Dropout Protection.Īlso, the "Enable low latency monitoring for instruments" is checked, and I cannot un-check it, as the option is greyed out with no way to de-select it. I normally have it set to 1024 (buffer size) as I don't need low latency, so I tried it at 5 - no improvement at all. I have played around with my soundcard latency as well, no improvement. I am also running my system entirely on SSD's, I have a 1TB and a 2TB SSD. I checked CPU usage, and it is stable at the time of the crackling at around 1-2% or less, ram usage (I have 16GB) is low as well. So far I have tried about 20 kontakt instruments as well as light and heavy omnisphere 2 patches, and everything is making random crackling / clicks or pops. I can't work on an iPad so if this interface does not work with Windows I'll need to return it.I just upgraded to S1 3.5.1 just now, and every virtual instrument I have tried has random, regular crackling, clicks / pops - artifacts basically. The PC does not have any antivirus other than Windows DefenderĤ) Setting power plan to high performanceĦ) Using Process Lasso to set Windows Audio process as High PriorityĨ) Creating new song in Studio One or other DAWsġ0) Restarted PC and Interface many many times. Studio One and Universal Control with Latest Drivers ![]() Windows 11 updated to the latest drivers ![]() I am not using any VST or processing while recording With the Presonus Interface it happens with Studio One or any DAW I use. Also it's something from Presonus because with my older interface this did not happen even on this Windows laptop. The issue happens mostly on Windows, because while software monitoring on an iPad it did not happen. The crackling cannot be heard when direct monitoring, only software. I get crackling while monitoring, but even worse, it gets recorded and can be heard afterwise so the recording is useless. It's a Lenovo Laptop with Core i7 and 16GB of RAM so no resources issue. Hi there, I am using a Studio 68c to record on a Windows 11 PC. ![]()
0 Comments
Leave a Reply. |