-
Notifications
You must be signed in to change notification settings - Fork 70
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
6 bar delay #211
Comments
It is not entirely clear to me if you are having issue with the latency being too high, or that FlexASIO is not reporting the correct latency to Ableton. In any case, you might want to read this FAQ and the next one if you haven't already. |
I went from the system working really well to a delay that goes way beyond "latency". We're talking 20 seconds. Clearly something fundamental is wrong but I just can't find it. I tried uninstalling the GUI, perhaps I should uninstall flexasio as well and reinstall.
Sent from AOL on Android
On Sun, Jan 21, 2024 at 11:02 AM, Etienne ***@***.***> wrote:
It is not entirely clear to me if you are having issue with the latency being too high, or that FlexASIO is not reporting the correct latency to Ableton.
In any case, you might want to read this FAQ and the next one if you haven't already.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please help me: Ableton Live11, Windows 10, Behringer UCA222, yesterday I was getting crunchies on playback, so I opened the GUI and fiddled around with the buffer size. Crunchies gone (tracks were virtual). Opened a song I am writing, and the MIDI tracks going to my K2700 are delayed six bars (measures). My brain is bleeding. ASIO 4ALL didn't work with my setup, so I installed flexASIO and the flexasio gui. Everything was working fine until yesterday. Now I am troubleshooting instead of making music... I am back to MME.
The text was updated successfully, but these errors were encountered: