Bub


No sir. That's exactly what my Properties screen looks like.

Bub you will need to do an actual physical round trip latency check to get the real figures because it looks like some figures are not being reported to Sonar from the driver there.
 
Here's a simple way to get a fairly accurate figure. 
 
http://centrance.com/downloads/ltu/
 
Once you get the real figure you can add the extra to Sonar's ASIO reported latency and you'll get improved timing between different types of input into your DAW.
 
 

Bub


No sir. That's exactly what my Properties screen looks like.

I was just yankin yer chain.


However, how can your total rountrip samples be more than double mine but have less rountrip msec? That just does not make mathematical sense, unless I'm not understanding the relationship between the two.

craigb


Ooo... *Snap!*
       

*Crackle!* and *Pop!*?

Jonbouy

Bub


No sir. That's exactly what my Properties screen looks like.

Bub you will need to do an actual physical round trip latency check to get the real figures because it looks like some figures are not being reported to Sonar from the driver there.
 
Here's a simple way to get a fairly accurate figure. 
 
http://centrance.com/downloads/ltu/
 
Once you get the real figure you can add the extra to Sonar's ASIO reported latency and you'll get improved timing between different types of input into your DAW.
 
 

bapu

Bub


No sir. That's exactly what my Properties screen looks like.

I was just yankin yer chain.


However, how can your total rountrip samples be more than double mine but have less rountrip msec? That just does not make mathematical sense, unless I'm not understanding the relationship between the two.

Aha, now I see Jonbouy has a logical explanation.

bapu

Bub

No sir. That's exactly what my Properties screen looks like.

I was just yankin yer chain.

However, how can your total rountrip samples be more than double mine but have less rountrip msec? That just does not make mathematical sense, unless I'm not understanding the relationship between the two.

Well ... the trick is ... you have to set your Project Sample Rate to 384,000. Then click Apply. Then set it back to 44100. Then click on something else, like ... oh, I dunno, one of the Dim Solo Gain settings, that way the 44100 isn't highlighted blue. ;)



(IOW ... I'm messin' with ya.)

By the way ...... I just noticed something ........ Apparently my middle Dim Solo setting is measured in DE's, whatever the heck that is. LOL!

Bub

By the way ...... I just noticed something ........ Apparently my middle Dim Solo setting is measured in DE's, whatever the heck that is. LOL!

Screen resolution? Zoom?

Jonbouy

Bub

No sir. That's exactly what my Properties screen looks like.

Bub you will need to do an actual physical round trip latency check to get the real figures because it looks like some figures are not being reported to Sonar from the driver there.
 
Here's a simple way to get a fairly accurate figure. 
 
http://centrance.com/downloads/ltu/
 
Once you get the real figure you can add the extra to Sonar's ASIO reported latency and you'll get improved timing between different types of input into your DAW.

That's a handy tool to use, you mentioned it to me once a long time ago and I checked it out.

IIRC, it was almost dead on with what Sonar was reporting.

Danny Danzi

 
I can actually get down to 32 with that box, but there is no need as I notice no difference using 64 samples.


-Danny

This is the key factor for most of us, that getting down to that 'it makes no difference' low level is low enough. 
 
The big issue then becomes one of scalability once the round trip latency is low enough not to interfere with any tracking you might want to undertake through the app.
 
Scalability in this instance meaning how complex a project you can run without having to increase the buffer size so that you don't end up having to switch between settings when you are performing different tasks.
 
It's one thing getting world beating low latency scores for competitions sake but it's far more convenient if you can find a spot that allows for trouble free through the app. monitoring AND glitch free arranging and mixing capabilities at a single setting.
 
As ever Danny cuts to the meat of the issue.

bapu

Bub

By the way ...... I just noticed something ........ Apparently my middle Dim Solo setting is measured in DE's, whatever the heck that is. LOL!

Screen resolution? Zoom?

I don't know ... it's really weird isn't it?

I did go in and tweak some things such as font smoothing and that kind of thing. Maybe it's a result of that?

I see what you mean though, it does look like it's just the edge of the B cut off.

It's that way even when I view it, in other words, it's not an artifact of the screen shot.

Well ... the trick is ... you have to set your Project Sample Rate to 384,000. Then click Apply. Then set it back to 44100. Then click on something else, like ... oh, I dunno, one of the Dim Solo Gain settings, that way the 44100 isn't highlighted blue. ;)

 
Ya scoundrel!!!...
 
Post that figure upstairs by tomorrow you just know you'll have someone swearing he's beat you for real, because he's betterer at tweaking computers than anyone else...