Once you change any setting the latency offset changes wildly until you restart the application, which makes it return to 48 samples again.
#Bidule waves driver
The difference is quite exactly 48 samples, but only as long as you don't change any settings in the ASIO4ALL driver (like buffer size). I measured the difference between the roundtrip latency reported by the driver and the real latency via a loopback cable. I wonder which version of ASIO4ALL you are using? I installed the latest version 2.9 and get low latency playback in Ableton Live without any much problems. I'm still curious about what WDM nd kernel streaming is, and how it relates to the choices I'm seeing in Bidule. Only with my MBP's built-in audio does it suffer. When I used it with my EMI 26 audio interface, the latency was negligible (haven't reinstalled the EMI driver yet). I don't think Bidule is introducing the additional latency. When I play my midi keyboard, the sound is crystal-clear, but still comes out about 250-400ms after I press the key!! I set the buffers to 128 samples in Bidule AND ASIO4ALL, and when I choose ASIO4ALL as the output, I get a small info pane that says this:īidule runs with :128 samples (2.90249 ms) sized blocks
Here is what I see when I look at the available audio devices in Bidule:Īs you can see, nothing here about WDM or kernel streaming. You're correct about me being able to choose the output.
#Bidule waves windows
OK, I just reinstalled Windows (XP, SP2 BTW), Bidule and ASIO4ALL.
0 kommentar(er)
