Bruno de Souza Lino Posted January 29, 2022 Share Posted January 29, 2022 This is something that is possible to do in REAPER: 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. Link to comment Share on other sites More sharing options...
Glenn Stanton Posted January 30, 2022 Share Posted January 30, 2022 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. Link to comment Share on other sites More sharing options...
Bruno de Souza Lino Posted February 1, 2022 Author Share Posted February 1, 2022 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. Link to comment Share on other sites More sharing options...
Glenn Stanton Posted February 1, 2022 Share Posted February 1, 2022 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... Link to comment Share on other sites More sharing options...
John Vere Posted February 6, 2022 Share Posted February 6, 2022 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 Link to comment Share on other sites More sharing options...
Bruno de Souza Lino Posted October 28, 2022 Author Share Posted October 28, 2022 On 2/6/2022 at 2:23 PM, Cactus Music said: 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 Sure, but I'm talking about WASAPI Shared here, not ASIO. My interface doesn't have native ASIO drivers. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now