![]() ![]() Windows can be quite picky on the configuration settings (“Sound” in Settings, and sometimes you also need to know your way around the “More Sound Settings” in the “Sound” tab). On top of that, many of the audio devices are really sophisticated and can demand that the user really understands how they work (audio flow) and how the various Windows audio software works and interfaces with these external devices. In other words, when software, especially drivers which run at low kernel levels, run up against these new security initiatives, various problems can be expected unless they were written specifically for the new computing initiative. All of the new equipment I tested - as in released in the past 2 years - had no issues whatsoever. In my case, a lot of testing with my legacy products, even if new stock (but developed and released to market 12 years ago for example), had problems or just didn’t work. You can tell what a pickle this is when you go to a manufacture’s support page, they supposedly have a new driver available which was release this year but the operating system support only goes up to W8.1 or similar. In many cases their attempts to update their drivers for older equipment leave much to be desired. One of the effects was a change in Driver signing enforcement which broke many of the existing drivers that were in use, including audio drivers that our favorite audio hardware companies had developed and released for their products over the years. I guess I will add my long winded 2-cents worth as I have recently been through something similar to your experience and have done a lot of testing with some surprising (to me) results.įirst and foremost, with one of the late Windows 10 builds and everything with Windows 11, Microsoft moved to enforcing compliance with the TPM (Trusted Platform Module) and Secure Boot for UEFI firmware requirements. When you introduce network streaming into the equation you’re introducing another potential source of glitches. If that’s the problem, the I’d: 1) check that the windows audio sample rate and the rate you have set in GP are the same 2) raise the sample buffer size to something like 512 to see if it helps 3) instead of YouTube try a source like an MP3 stored locally and played with Windows Media Player or something like that. Putting those issues aside, if the issue you’re having is the clicks and pops only start happening when you try to play both GP and YouTube at the same time then there could be a number of different things causing that problem. It really hasn’t been supported for a long time, and different Firewire chipsets may work better or worse than others under newer versions of Windows. Unfortunately, Firewire on Windows tends to be problematic even if you get recent drivers installed. If you can get that installed, I wouldn’t use ASIO 4 All. ![]() Do you have the latest Presonus driver for it? Looks like the last update was 2016 ( FireBox | Downloads | PreSonus ) and you have to select Windows 7 to get a download option. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |