MME sure runs really fast but I can't do VSTi monitoring. #Mme vs wdm drivers#Have you checked you have the latest version of the driver installed?Īlso you say that swicthing drivers to MME and back to ASIO cures the latency problem, is that correct? Have you tried just changing ASIO buffer size instead? What buffer size do you normally run? Conflict can be possible also with output devices. This can give excellent low latency performance (if the ASIO drivers are written well) but it also explains why they tend not to be multi-client: the idea is that the DAW completely takes over the interface, which means only one app at a time.ĪSIO is still the standard on Windows for audio production, so I would suggest trying to solve your ASIO driver issues before resorting to a different type. Since Windows allows managing audio device with several interfaces (MME, WASAPI, KS, Direct-X), user needs to avoid audio device conflict: for example using the same recording device on input1 and input2 is possible with different interface (WDM on input 1, KS on input2). This is equivalent to Core Audio on the mac, except that Core Audio allows lower latencies than MME or WDM (not sure about WASAPI: I gather this is much better but I've not tried to use it for audio production)ĪSIO works differently as it allows the DAW to commmunicate directly with the interface, without the OS as intermediary. If you select any of these types your audio is passed to the OS which then hands it on to the interface.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |