![]() ![]() Thanks so much that answers my question beautifully. ![]() WASAPI exclusive can potentially have the same latency as ASIO depending on the driver itself. As far as WASAPI having less latency than ASIO, I think its very unlikely since ASIO is a very thin layer around the driver. We have no means to report that higher value using WASAPI. SONAR will stream to the device at 3 msec but the effective latency is likely much higher (maybe around 200 msec) because of the bluetooth stack. As an extreme example, consider a bluetooth device. A driver could hypothetically go lower than 3 msec but I haven't seen many. WASAPI gives us a min/max buffer size and that is what the latency slider reports. It doesn't take into account any additional external latencies that are inherent in the driver/hardware itself because there is no way for us to query WASAPI for that data. ![]() I understand that WASAPI does not have "any way to query the system for its.latency unlike ASIO", but this fact seems to beg the question (especially given the fact that the effort made to minimize the latency of the OS to a bare minimum): shouldn't WASAPI, then, have less latency than ASIO? Is the latency of 3.0 ms an estimate? Is the issue really (and that for which I'm not accounting) the total roundtrip of 6.5 ms in ASIO? 3 msec is the buffer size that SONAR uses when streaming audio via WASAPI. But if I may ask what very well may be a thoroughly bone-headed question: I am enclosing my ASIO latency and WASAPI latency estimates from the Driver Settings window in Preferences. Noel Borthwick outland144k Hi Noel, Thanks for the above your note does really help. Outland144k Hi Noel, Thanks for the above your note does really help. I understand that WASAPI does not have "any way to query the system for its.latency unlike ASIO", but this fact seems to beg the question (especially given the fact that the effort made to minimize the latency of the OS to a bare minimum): shouldn't WASAPI, then, have less latency than ASIO? Is the latency of 3.0 ms an estimate? Is the issue really (and that for which I'm not accounting) the total roundtrip of 6.5 ms in ASIO? ASIO Latency Hi Noel, Thanks for the above your note does really help. For most practical use cases you don't need to bother with this. As such SONAR has no way to account for this other than the user manually entering an offset. " Regarding syncing audio, WASAPI doesn't have any way to query the system for its input and output latency unlike ASIO. Without any driver changes, all applications in Windows 10 will have 4.5-16ms lower latency. One of the main reasons we did the updates to WASAPI is because of the enhancements in Win10 as documented here: "In Windows 10 we minimized the latency of the OS to a bare minimum. WASAPI is the modern Windows API to communicate with audio drivers. The diagram below shows how WASAPI communicates with the driver. Noel Borthwick Again WASAPI is not a driver in itself and technically neither is ASIO. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |