12-27-2020, 11:34 PM
On the contrary Stuart, it may well be that the JK client needs to do something differently with ASIO and it's just luck that some drivers are not affected as drastically. Other drivers might also be unknowingly forced to a default buffer size but one that happens to be large enough not to cause audio distress. For instance, if the PreSonus, Behringer, and Focsurite defaulted to a buffer size of 128 most people would not notice.
PreSonus, Behringer, Focsurite all have this problem. All of these are major manufacturers and sell thousands of units. I suspect there are brands experiencing this as well. It is possible that It appears that JK's method of initialization causes them to reset to a default buffer size. Other programs (DAWs, etc,) don't do this so it is quite possible and feasible that the method JK employs needs to enhanced. It's unlikely that all 3 of these brands (and possibly others) are in the wrong.
The story is most likely in the code. It requires a developer to take a look and also look at the ASIO SDK and make sure everything is being done properly. Then he/she can answer yay/nay. Remember - code omissions are just as problematic as code errors. JK has issued dozens of (or more) releases just to address errors so it's clear mistakes can make it into the wild.
Screwy workarounds or suggesting that users dump their major brand equipment for something else are not the answer.
I'm betting that some of the crackling people are hearing could be rectified by larger buffers if they could only be set and retained.
PreSonus, Behringer, Focsurite all have this problem. All of these are major manufacturers and sell thousands of units. I suspect there are brands experiencing this as well. It is possible that It appears that JK's method of initialization causes them to reset to a default buffer size. Other programs (DAWs, etc,) don't do this so it is quite possible and feasible that the method JK employs needs to enhanced. It's unlikely that all 3 of these brands (and possibly others) are in the wrong.
The story is most likely in the code. It requires a developer to take a look and also look at the ASIO SDK and make sure everything is being done properly. Then he/she can answer yay/nay. Remember - code omissions are just as problematic as code errors. JK has issued dozens of (or more) releases just to address errors so it's clear mistakes can make it into the wild.
Screwy workarounds or suggesting that users dump their major brand equipment for something else are not the answer.
I'm betting that some of the crackling people are hearing could be rectified by larger buffers if they could only be set and retained.