Jump to content
Bruno de Souza Lino

Allow us to determine the block size in WASAPI Shared.

Recommended Posts

This is something that is possible to do in REAPER:
image.png.02a1ffec392a9a7751433c977e927573.png

On CbB, all you have is changing a DSP option in a external options file and that may not even do anything. While I can dial lower latencies with REAPER with WASAPI shared, on CbB, I seem to be stuck in 400ms with no provisions of changing it.

Share this post


Link to post
Share on other sites

on my system with a Behringer UB-802 on USB 2, i'm getting a reading of 10ms @ 480 samples. have you run the wave profiler on driver settings tab?

under audio sync and caching i believe you can make this adjustment which might help. 

image.png.c10213df004d987df7027e21f444505e.png

Share this post


Link to post
Share on other sites
On 1/30/2022 at 1:28 PM, Glenn Stanton said:

on my system with a Behringer UB-802 on USB 2, i'm getting a reading of 10ms @ 480 samples. have you run the wave profiler on driver settings tab?

10ms @ 480 samples seems to be the minimum latency figure you can get and that's roughly a 32th note off. While I could try to adjust the compensation thing on the settings (which would be a nightmare, since I don't know how many samples I should offset it by to get specific amounts of ms removed or added), that wouldn't do anything for monitoring and I would be ahead in the recordings if I compensate the latency.

Share this post


Link to post
Share on other sites

to be fair, my rack unit - UMC-1820 - i can get to about 2ms at 64 samples. not useful in practice when recording multiple tracks on my current systems, so i usually set to 6-8ms @ 128 samples with no FX when recording live instruments. for MIDI controller performance i'll go to 20-30ms @ 512 samples, and mixing, 100ms @ 4096 samples. if the monitoring is happening later in a mix cycle, and i need to add live instruments, i switch to direct monitoring of the new tracks and play to the mix level latency. then simple move the new tracks based on the samples #.  least amount of potential glitching and it's digital so moving tracks precisely is "normal" for me. maybe when i finally upgrade to a proper modern system, this approach will not be strictly necessary...

Share this post


Link to post
Share on other sites

You need to perform a loop back test to determine how many samples to adjust for none ASIO drivers timing offset. ASIO does this automatically but all other drivers will be late. And yes it’s going to be 1/32 or more so it does matter. I demonstrate how to do a loop back in this video 

 

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...