Jeffiphone
Max Output Level: -87 dBFS
- Total Posts : 173
- Joined: 2014/09/27 19:58:17
- Location: Santa Rosa, CA
- Status: offline
I/O Buffers and "Use Reported Latency"
Just a quick question for the forum...... I read in the help guide that the default for the I/O buffers is 128. I'm just trying to optimize my system to avoid the nightmares I encountered last week. I'm not running huge projects, but normal, like 30 tracks or so. Do most folks raise the level of the I/O buffers to 256 or greater? Also, should the number in my I/O buffers be the same as the number of my ASIO level of my Focusrite interface? Meaning if I change one, should I change both settings? And one more......can someone explain what the "Use Reported Latency" box is? And should this be altered in some way? Thanks so much for the help. ~Jeff
Acer with i7 processer - Sonar Platinum 64bit - Windows 10 64 bit - Focusrite Scarlett 2i2 (2nd Gen) -
|
JonD
Max Output Level: -39 dBFS
- Total Posts : 3617
- Joined: 2003/12/09 11:09:10
- Location: East of Santa Monica
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/13 11:41:08
(permalink)
For tracking, 128 is a good starting point. Of course, it comes down to your interface drivers and system (Some interfaces can comfortably go lower - 64 or even 32 - and still work glitch-free!). Ideally you want to work in your "sweet spot" -- low enough so there's no noticeable lag-time, but not so much that your system can't handle it without glitching. An easy formula for this is to go the lowest setting your system will handle, then bump it up one setting. For mixing, you don't need super fast response time. Bump it up to 1024 or higher to ease the strain on your system.
SonarPlat/CWbBL, Win 10 Pro, i7 2600K, Asus P8Z68 Deluxe, 16GB DDR3, Radeon HD5450, TC Electronic Impact Twin, Kawai MP11 Piano, Event ALP Monitors, Beyerdynamic DT770 Pro, Too Many Plugins, My lucky hat.
|
chuckebaby
Max Output Level: 0 dBFS
- Total Posts : 13146
- Joined: 2011/01/04 14:55:28
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/13 11:46:59
(permalink)
I run my Focusrite latency at 4-6 when tracking. if I have a large project and im trying to save resources then I will lower it while im mixing. I have a fast processor so I don't have that problem as much anymore as I did when I used a slower machine. (which was still pretty fast) an AMD Bulldozer.
Windows 8.1 X64 Sonar Platinum x64 Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GBFocusrite Saffire 18I8 - Mackie Control
|
Jeffiphone
Max Output Level: -87 dBFS
- Total Posts : 173
- Joined: 2014/09/27 19:58:17
- Location: Santa Rosa, CA
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/13 14:28:56
(permalink)
JonD For tracking, 128 is a good starting point. Of course, it comes down to your interface drivers and system (Some interfaces can comfortably go lower - 64 or even 32 - and still work glitch-free!). Ideally you want to work in your "sweet spot" -- low enough so there's no noticeable lag-time, but not so much that your system can't handle it without glitching. An easy formula for this is to go the lowest setting your system will handle, then bump it up one setting. For mixing, you don't need super fast response time. Bump it up to 1024 or higher to ease the strain on your system.
Thanks. Anyone help me with questions #2 and #3 of my OP?
Acer with i7 processer - Sonar Platinum 64bit - Windows 10 64 bit - Focusrite Scarlett 2i2 (2nd Gen) -
|
microapp
Max Output Level: -77 dBFS
- Total Posts : 653
- Joined: 2013/10/31 12:21:31
- Location: Wondervu, CO
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/13 16:24:02
(permalink)
Jeffiphone Just a quick question for the forum...... I read in the help guide that the default for the I/O buffers is 128. I'm just trying to optimize my system to avoid the nightmares I encountered last week. I'm not running huge projects, but normal, like 30 tracks or so. Do most folks raise the level of the I/O buffers to 256 or greater? Also, should the number in my I/O buffers be the same as the number of my ASIO level of my Focusrite interface? Meaning if I change one, should I change both settings? And one more......can someone explain what the "Use Reported Latency" box is? And should this be altered in some way? Thanks so much for the help. ~Jeff
#2 For the 4 or 5 interfaces I have used with Sonar I cannot adjust the buffer settings from within Sonar while using ASIO. They are greyed out. Sonar picks up the setting from hardware so you have to use the ASIO control panel provided with the hardware. Not saying this is 100% true but in my experience it is. #3 AFAIK, "Use reported latency" does not do anything. PDC uses the latency reported by individual plugins to force plugins to sync.
Sonar Platinum, Cubase Pro 8.5, Reaper 5, Studio One 2Melodyne Studio 4, Finale 2012I7-5820K 4.5GHz, 32 GB DDR4-2800,3 monitors,Win 10 ProToshiba P75-A7100,l7-4900 2.4 Ghz/8MB Win 8.1 ProTascam FW-1884, Emu 0404USB, CMC-AI,Axiom 61Yamaha HS-50's, Sony SA-W2500, Sennheiser RS170's, ATH-M50Ibanez Jem7VWH, RG-1570Jackson DK2-S(Sustainiac),Les Paul CustomDigitech Valve-FX, GFX-1,TSR-24,RP-90
|
Jeffiphone
Max Output Level: -87 dBFS
- Total Posts : 173
- Joined: 2014/09/27 19:58:17
- Location: Santa Rosa, CA
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/13 17:15:28
(permalink)
microapp
Jeffiphone Just a quick question for the forum...... I read in the help guide that the default for the I/O buffers is 128. I'm just trying to optimize my system to avoid the nightmares I encountered last week. I'm not running huge projects, but normal, like 30 tracks or so. Do most folks raise the level of the I/O buffers to 256 or greater? Also, should the number in my I/O buffers be the same as the number of my ASIO level of my Focusrite interface? Meaning if I change one, should I change both settings? And one more......can someone explain what the "Use Reported Latency" box is? And should this be altered in some way? Thanks so much for the help. ~Jeff
#2 For the 4 or 5 interfaces I have used with Sonar I cannot adjust the buffer settings from within Sonar while using ASIO. They are greyed out. Sonar picks up the setting from hardware so you have to use the ASIO control panel provided with the hardware. Not saying this is 100% true but in my experience it is. #3 AFAIK, "Use reported latency" does not do anything. PDC uses the latency reported by individual plugins to force plugins to sync.
Thanks Micro. I think what I'm asking is......should the setting on my ASIO Panel (256, for instance) match the I/O buffer settings in Preferences (e.g. 256)? Forgive my ignorance on this, but I'm just trying to get the settings most people use. Thanks.
Acer with i7 processer - Sonar Platinum 64bit - Windows 10 64 bit - Focusrite Scarlett 2i2 (2nd Gen) -
|
microapp
Max Output Level: -77 dBFS
- Total Posts : 653
- Joined: 2013/10/31 12:21:31
- Location: Wondervu, CO
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/13 17:55:31
(permalink)
Thanks Micro. I think what I'm asking is......should the setting on my ASIO Panel (256, for instance) match the I/O buffer settings in Preferences (e.g. 256)?
Yes, Sonar should use the settings in ASIO Panel. If recording (say... guitar) while listening to previous tracks, make the buffer size as small as possible without dropouts etc, so there is minimal delay in the guitar track. I try to keep the roundtrip latency < 10ms. If the latency is > 15ms or 20ms, you will begin to hear the guitar track delayed. If your interface has direct monitoring, use this instead since you will hear the guitar before it goes into the DAW and eliminate at least the input latency. For mixing, the latency is not important since there are no external instruments involved and all the tracks are already recorded (or generated from MIDI) so use a bigger buffer setting to allow more tracks/effects before dropouts. You will notice a delay from pressing PLAY to hearing audio but that is about it. You can think of the I/O buffers as little delay lines on the in and out of the DAW.
Sonar Platinum, Cubase Pro 8.5, Reaper 5, Studio One 2Melodyne Studio 4, Finale 2012I7-5820K 4.5GHz, 32 GB DDR4-2800,3 monitors,Win 10 ProToshiba P75-A7100,l7-4900 2.4 Ghz/8MB Win 8.1 ProTascam FW-1884, Emu 0404USB, CMC-AI,Axiom 61Yamaha HS-50's, Sony SA-W2500, Sennheiser RS170's, ATH-M50Ibanez Jem7VWH, RG-1570Jackson DK2-S(Sustainiac),Les Paul CustomDigitech Valve-FX, GFX-1,TSR-24,RP-90
|
Jeffiphone
Max Output Level: -87 dBFS
- Total Posts : 173
- Joined: 2014/09/27 19:58:17
- Location: Santa Rosa, CA
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/13 18:01:05
(permalink)
microapp
Thanks Micro. I think what I'm asking is......should the setting on my ASIO Panel (256, for instance) match the I/O buffer settings in Preferences (e.g. 256)?
Yes, Sonar should use the settings in ASIO Panel. If recording (say... guitar) while listening to previous tracks, make the buffer size as small as possible without dropouts etc, so there is minimal delay in the guitar track. I try to keep the roundtrip latency < 10ms. If the latency is > 15ms or 20ms, you will begin to hear the guitar track delayed. If your interface has direct monitoring, use this instead since you will hear the guitar before it goes into the DAW and eliminate at least the input latency. For mixing, the latency is not important since there are no external instruments involved and all the tracks are already recorded (or generated from MIDI) so use a bigger buffer setting to allow more tracks/effects before dropouts. You will notice a delay from pressing PLAY to hearing audio but that is about it. You can think of the I/O buffers as little delay lines on the in and out of the DAW.
Right on. Thanks bro. I'm familiar with the latency issues and when to lower/raise the level. But I was just wondering if the two settings should match. And I think you answered that question. So when I want to record, I'll adjust the ASIO Panel, AND adjust the I/O settings in Preferences to be the same number. Same for raising the level when mixing. Easy enough. Thanks everyone. ~Jeff
Acer with i7 processer - Sonar Platinum 64bit - Windows 10 64 bit - Focusrite Scarlett 2i2 (2nd Gen) -
|
microapp
Max Output Level: -77 dBFS
- Total Posts : 653
- Joined: 2013/10/31 12:21:31
- Location: Wondervu, CO
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/13 18:01:21
(permalink)
☄ Helpfulby Thedoccal 2016/07/14 05:21:30
Sonar Platinum, Cubase Pro 8.5, Reaper 5, Studio One 2Melodyne Studio 4, Finale 2012I7-5820K 4.5GHz, 32 GB DDR4-2800,3 monitors,Win 10 ProToshiba P75-A7100,l7-4900 2.4 Ghz/8MB Win 8.1 ProTascam FW-1884, Emu 0404USB, CMC-AI,Axiom 61Yamaha HS-50's, Sony SA-W2500, Sennheiser RS170's, ATH-M50Ibanez Jem7VWH, RG-1570Jackson DK2-S(Sustainiac),Les Paul CustomDigitech Valve-FX, GFX-1,TSR-24,RP-90
|
tlw
Max Output Level: -49.5 dBFS
- Total Posts : 2567
- Joined: 2008/10/11 22:06:32
- Location: West Midlands, UK
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/13 19:22:00
(permalink)
"Use reported latency" allows you to correct for interface drivers and/or plugins that don't accurately report the correct layency back to Sonar.
An example is that some interfaces have a hidden 'safety buffer' that may or may not be mentioned in its specifications, is always active and can't be reduced or changed. If the driver only reports to the DAW the latency set in the driver then that 'safety buffer' won't be compensated for. The best way to find out what your audio latency actually is is to measure it using a loop-back through the interface.
Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board, ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre. Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
|
Thedoccal
Max Output Level: -85 dBFS
- Total Posts : 290
- Joined: 2014/10/12 16:43:08
- Location: Joshua Tree, CA
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/14 04:30:33
(permalink)
2. "Also, should the number in my I/O buffers be the same as the number of my ASIO level of my Focusrite interface? Meaning if I change one, should I change both settings?" I would think the answer to this would be yes, the two should match. If it was me, I would change the settings on the Focusrite first, and then see if Sonar settings change when you click "apply". I don't know if they will match exactly, but if the settings in sonar change, I would leave them. sonar could be reading your sound card settings and making some adjustments... If you can change Sonar's buffer or samples settings independent of your soundcard (I cannot do this with mine), and sonar's settings don't change when you apply the Soundcard's changed settings...then my first inclination would be to match them both (manually). (edited) BTW that video posted two posts up was very enlightening.
post edited by Thedoccal - 2016/07/14 05:33:04
http://www.catastrophelounge.comThe NeckDive Strap - NEW^^Sonar: Platinum Lifetime/Computer: i7-870, 16GB RAM, AMD R9 380 graphics, Windows 10 (Pro x64)/500gb SSD C:, Barracuda sample(3T) and projects(1T) drives/3 Display Monitors (2&3 split)/Audio Interface: Behringer UFX1604 USB/Firewire/USB Stick/MIDI: Roland A-800Pro, Keystation Pro 88, Roland UM-3G:/Hardware Synths: Korg M3, Yamaha MOX6, Roland TD-8
|
Klaus
Max Output Level: -84 dBFS
- Total Posts : 320
- Joined: 2009/07/14 07:34:02
- Location: Cologne, Germany
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/14 06:11:12
(permalink)
Maybe I don't understand your question right, but if you're referring to the I/O Playback and Recording Buffers, these settings are not related to the audio driver settings and therefore don't have to match.
I/O Buffer Size determines the buffers which are necessary to write to and read from your hard disk without getting dropouts.
In projects with many audio tracks, where a lot of audio files play simultaneously, raising the I/O Buffers from default 128 to 256 or 512 (KB) is often needed to avoid dropouts, even if your audio device driver settings are already set to a higher latency setting of 1028 samples.
For projects with a moderate audio track count, the default setting of 128 KB I/O Buffer Size should be fine.
SONAR Platinum ∞RME HDSPe AIO - Windows 10 64bit - Intel i7 2600K - 16 GB RAM
|
DeeringAmps
Max Output Level: -49 dBFS
- Total Posts : 2614
- Joined: 2005/10/03 10:29:25
- Location: Seattle area
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2016/07/14 07:25:12
(permalink)
"Use reported latency" insures all audio tracks are in sync. YES you want that checked. You can check, as has already been suggested, with a "loop back" test. Sonar will have it spot on, you don't have to worry about it.
Tom Deering Tascam FW-1884 User Resources Page Firewire "Legacy" Tutorial, Service Manual, Schematic, and Service Bulletins Win10x64 StudioCat Pro Studio Coffee Lake 8086k 32gb RAM RME UFX (Audio) Tascam FW-1884 (Control) in Win 10x64 Pro
|
D Wreck
Max Output Level: -90 dBFS
- Total Posts : 3
- Joined: 2015/01/25 05:28:38
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2017/09/04 21:47:14
(permalink)
if you increase the sample rate in your ASIO panel with a track open it speeds it up to ridiculous proportions. XD
|
D Wreck
Max Output Level: -90 dBFS
- Total Posts : 3
- Joined: 2015/01/25 05:28:38
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2017/09/04 21:47:18
(permalink)
i was having fun with this the other night
|
D Wreck
Max Output Level: -90 dBFS
- Total Posts : 3
- Joined: 2015/01/25 05:28:38
- Status: offline
Re: I/O Buffers and "Use Reported Latency"
2017/09/04 21:47:19
(permalink)
|