I’m afraid that the ASIO handling code is extremely delicate, so I’m not sure this will be easy to fix. We follow (almost) exactly the same procedure as the Steinberg ASIO SDK documentation, and if we deviate slightly we can break compatibility with a lot of drivers that currently work. This is very likely to be a problem with driver manufacturers doing non-standard stuff, rather than anything “wrong” with JUCE.