Hi folks. Up and running with Windows 10 sonar Platinum and v700. How low do any of you set the ASIO buffers?

I'll do a little trial and error but curious as to what others are doing.

i7 4820 @ 3.70 gh 16 ram.

Cheers
WSS

I have my MOTU 896mk3 Hybrid and a Roland Octa-Capture both set at 64.  Both working reliably for me at 64.
The MOTU Latency is:  Input 2.7ms, Output 3.3 ms, Total Roundtrip 6.1ms. (2.7 plus 3.3 equals 6 but 6.1 is what is reported).
The Octa-Capture is: Input 4.8 ms, Output 2.8 ms, Total Roundtrip 7.6ms.
 
Win 10 latency is better than Win 7 or 8, at least with the Octa-Capture.  The Input latency was 6.2 with 64 samples on both Win 7 and 8.1.  Don't remember the output latency but total was up around 11 or 12 ms.
 
 
 
 
 

Workable (no crackles/droputs) ASIO buffer size depends on the hardware in the PC, PCI-bus dpc latency, power savong settings and how loaded the DAW is.

I can get a buffer of 32 samples, and record monitoring through Sonar.

Once there's a heavy enough plugin load in Sonar then the buffer may need to be increased a bit.

If I try running wireless networking then the buffer needs to be 1 second+.

Only trial and error can tell you what will work as every Windows PC is different, even ones mass produced as the same "model" may be different to each other if any of the card/MB components have been changed by the hardware manufacturers,

Westside Steve Simmons
Hi folks. Up and running with Windows 10 sonar Platinum and v700. How low do any of you set the ASIO buffers?

My RME UFX is often left at the smallest 48-sample ASIO buffer size.
If I'm working with a more dense project, I'll raise that to 64 or 128-sample ASIO buffer size.
Almost never need to go above 128-sample ASIO buffer size...

It really is trial and error depending on your sound card and computer and i don't mean just whether or not it is an i7 or an i5 or which build the processor is or what speed or what speed your memory is or how much you have.  it also highly depends on the architechture of the USB bus/firewire bus/PCIe bus or whichever one you're using to connect your soundcard to the computer.
 
having said that - the only time I set my MOTU's buffers down to 128 or 64 is when I'm using a MIDI controller and trying to record MIDI using a softsynth inserted into sonar as the output.  and I don't always have to do that!
 
I mostly use hardware I/O so that I don't have to worry about low latency on the computer/soundcard setup.  I use an external mixer so I can route output from sonar to several headphones for tracking while recording audio and sometimes I'll even use a hardware synth with audio output to a monitor or keyboard amp and just record the midi into sonar while I listen to the audio output from the keyboard.  that way I don't need low latency and I can change the softsynth to anything I want later.
 
the other thing you need low latency for is for when you want to use an amp sim for guitar while recording.  but again, I prefer not to do that.  I can either record clean guitar and appy an amp sim after recording, or I can use hardware instead and monitor directly.

tlw
Workable (no crackles/droputs) ASIO buffer size depends on the hardware in the PC, PCI-bus dpc latency, power savong settings and how loaded the DAW is.

I can get a buffer of 32 samples, and record monitoring through Sonar.

Once there's a heavy enough plugin load in Sonar then the buffer may need to be increased a bit.

If I try running wireless networking then the buffer needs to be 1 second+.

Only trial and error can tell you what will work as every Windows PC is different, even ones mass produced as the same "model" may be different to each other if any of the card/MB components have been changed by the hardware manufacturers,

Jim can you tell us how beefy of a computer you're using. I know RME has great drivers but how much
does your computer set and tweaks come into play

InstrEd
Jim can you tell us how beefy of a computer you're using. I know RME has great drivers but how much
does your computer set and tweaks come into play

• 6700k at 4.5GHz
• Z170x motherboard
• 32GB RAM
• Numerous SSDs (including PCIe x4)

 
To effectively work at small ASIO buffer sizes... you need a well-configured machine (top to bottom).
The smaller the ASIO buffer size, the more critical all the details.
You need a machine that can sustain heavy loads (indefinitely)... with no hiccups in data-flow.
A general-purpose user wouldn't notice a few ms hiccup in data-flow (high DPC Latency)... but for us that's a glitch or (worse) a drop-out.
 
Heavy audio projects can be very demanding.
Video and especially 3D rendering/animation make audio look *super* lightweight.
Video is where audio was about 15 years ago...

Thanks for sharing.

Westside Steve Simmons
Hi folks. Up and running with Windows 10 sonar Platinum and v700. How low do any of you set the ASIO buffers?

I'll do a little trial and error but curious as to what others are doing.

i7 4820 @ 3.70 gh 16 ram.

Cheers
WSS

 
Hi Steve,
 
I also run with Windows 10 sonar Platinum and vs700 - I get same performance as under win 7 i.e. I can run the ASIO buffer as low as VS700 ASIO setting = 3 (64 samples @ 44.1KHz, 128 samples @ 96 kHz) for very stable audio tracking and typical soft synth use ... than hike it up to ASIO setting = 6 (256 samples@ 44.1KHz, 512 samples @ 96 kHz) for heavy mixing duty ...
 
Something interesting I never spotted before ...

• when simply changing the project sample rate in Sonar preferences (without changing settings on VS700 front knob + power cycling), reported buffer size is wrong i.e. when switching from 44.1 kHz to 96 kHz, the VS700 ASIO dialog reports use of same number of samples as buffer, thus reporting half the latency (as you would expect: higher sampling rate => lower latency)
• however, when done as required (with changing settings on VS700 front knob + power cycling), ASIO buffer for same VS700 setting doubles; i.e. ASIO = 3 is now 128 samples @ 96 kHz instead of 64 (as previously reported); thus latency gets only a minor improvement (from 9.4 ms @ 44.1 kHz to 8.1 ms @ 96 kHz)

Do I see a VW-like cheat to suggest better performance than actually implemented ...???

Jim Roseberry
To effectively work at small ASIO buffer sizes... you need a well-configured machine (top to bottom).
The smaller the ASIO buffer size, the more critical all the details.
You need a machine that can sustain heavy loads (indefinitely)... with no hiccups in data-flow.
A general-purpose user wouldn't notice a few ms hiccup in data-flow (high DPC Latency)... but for us that's a glitch or (worse) a drop-out.
 
Heavy audio projects can be very demanding.
Video and especially 3D rendering/animation make audio look *super* lightweight.
Video is where audio was about 15 years ago...

Hi Jim,
Do you still employ a lot of system tweaks for win10 to get a "well-configured" machine ?
 
 

Hi Rob,
 
We certainly tweak things in Win10... as well as the BIOS.