![]() ![]() Your comments will be addressed in individual support tickets for an in-depth investigation and possible solutions to it. Decent progress has been made for this issue on Mac (hopefully a potential fix will be tested soon), and alternative functionality options are available on Windows. But new cases still keep appearing, and a lot of them are unique (cannot be bulk-solved). ![]() A lot of fixes and additional functionality has been put in place to deal with this, so there a lot of users out there for whom the problem is successfully fixed. We are, however, making some very good progress for these cases. In other words, it is quite a challenge to get this right. Even after collecting the debug information from the users, oftentimes we are getting stuck, simply because the issue can not be reproduced in-house, despite having a ton of interface/machine/driver combinations available for testing (which prevents us from implementing fixes successfully and efficiently). There are many third-party components involved here, each with its own flaws, problematic driver updates, bugs - countless potential conflicts between that component union and other production software clashing with the output device driver control, etc. The marriage between the operating system audio engine, the Systemwide driver, and the final output device driver has to be close to flawless in order for all of it to work smoothly. The place in the signal chain where the Systemwide app is located is a troublesome place to be. Thank you for your comments and issue reports! Our sincerest apologies for the lag in the post/response time here! It's been a challenging year for the support team and the entire company, and unfortunately, we've been falling short of the moderating here and other important tasks :( I'll try to address the general state of this issue and its context first, for a better understanding: Was hoping maybe someone here had a solution before I do all sorts of reinstalling, etc. I haven't done a ton of other experimenting yet. The only change in my rig is that there was a recent Windows update. All of a sudden it started up a few days ago. I had been running this same setup for the last 6 months with no problems. The strange thing is that this is completely new behavior. Reminds me of what it sounds like when bit rate is mismatched. ![]() My audio from Pro Tools is absolutely fine, w no problems with the Sonarworks plugin, but audio from any other source, like youtube, iTunes, Vegas Movie Maker Platinum, is full of warbles and stutters. My Reference 4 software is up to date (4.4.5.51). I'm running Windows 10 on a Sweetwater CS, Pro Tools 11.3, interface is a Presonus 16.4.2 AI. Having similar problems (Karlis, I sent you an email before I saw this thread, so feel free to respond here). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |