ASIO4All is hardly an optimization point. It's main function is to allow entry level audio interfaces that don't have OEM ASIO driver support to "possibly" be able to appear to the system as an ASIO capable interface. It's always used as a last resort for someone needing ASIO support for a specific application and doesn't always work as expected. ASIO4All is pretty much always LESS efficient than proper ASIO drivers provided by the interface OEM.

Of course there's always going to be hardware OEM's that just never get the driver part of the equation right. In that case switching to a better class of interface is warranted. Many folks think that hardware alone makes a good interface, but the hardware is only 1/2 of a winning combination for a good efficient audio interface. The drivers are the second half of that combo.

 

Last edited: Nov 10, 2024 at 12:11 AM

I wanted to know the answer to that too.

 

Well, CS is born (few months ago) for creators-oriented optimizations, so it aims to be more stable than gamers ones in this specific field.

We've discussed (and are of course open to further suggestions) about system mods to port/implement in it here:
https://github.com/mewostick/Creosynth/discussions/1

You can find more in-depth (technical too) explainations in the official wiki:
https://github.com/mewostick/Creosynth/wiki

Thanks in advance to anyone that will contribute (in any way) to it.

 

Last edited: Nov 11, 2024 at 9:37 AM