-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to set latency? #19
Comments
Okay, so if I understand correctly, you're saying that some ASIO host applications (here, Ableton) do not let you customize the buffer size and only use the "preferred size" reported by the ASIO driver. In that case, yes, it makes perfect sense to make the preferred buffer size customizable as a configuration option; I'll do that as soon as the configuration infrastructure in #6 is in place. Regarding latency: you should not assume that buffer size and latency are the same. That might be (mostly) true for most hardware ASIO drivers (or universal ASIO drivers that go directly to the hardware, such as ASIO4ALL), but it is not true with FlexASIO currently because it uses WASAPI Shared mode, which is not direct hardware access and typically incurs additional buffering, which adds additional latency on top of the ASIO buffer itself. Therefore, there are multiple separate issues here:
|
In addition to making the buffer size configurable, I suspect there might also be ways to make FlexASIO more useful when it comes to suggesting optimal buffer sizes. Filed #20 about that. |
The new |
When using FlexASIO with a DAW (such as Ableton Live or any other), we currently don't have any option to change the latency / buffer size. The usual worflow with other ASIO drivers - such as ASIO4ALL and my soundcards' ASIO drivers - is to click on the small
Hardware setup
button (see screenshot below) and then a Control Panel GUI is displayed, allowing to change the device latency. This is probably not needed for FlexASIO at this early stage - GUI design is always long to do. Just a simpleflexasio.ini
configuration file:would be enough.
Also the
Buffer size
displayed in Ableton (1024 samples) doesn't match the one automatically selected internally by FlexASIO (3072 samples = 69.7 milliseconds), as it can be seen in the log below (see in particular the parts in bold in the log).Question: how to manually force an output latency of 1024 or 512 samples?
The text was updated successfully, but these errors were encountered: