• Hardware
  • Lets all TEST our Interface driver for offset (p.5)
2015/03/11 00:10:33
Grem
Splat
Please check my sig.
Cheers:)


What if I'm on a mobile device and I can't "see" your sig? Any conversation based on what ever is in your sig is lost to me and others on mobile devices.
2015/03/11 00:36:50
Splat
Splat
Please check my sig.
Cheers:)


Grem
What if I'm on a mobile device and I can't "see" your sig? Any conversation based on what ever is in your sig is lost to me and others on mobile devices.


What if I can't see my sig as I'm on a mobile device ;)

Maybe somebody could tell me what my settings are ;)
2015/03/11 01:18:54
RobertB
Grem, Splat is showing this:
@48/24 & 128 buffers latency is 367 with offset of 38.
I know what you mean about the mobile version, as I use it to check in while I am at work.
2015/03/11 01:58:55
Grem
Splat

What if I can't see my sig as I'm on a mobile device ;)

Maybe somebody could tell me what my settings are ;)



Oh what a burn!! ;) LOL

I didn't think you were on a mobile device!!

Thank you Robert. What interface is it?
2015/03/11 04:39:11
Splat
Thanks Robert. It's a Saffire Pro 40.
2015/03/12 16:38:31
mettelus
I finally installed Platinum and revisited this since it occurred to me that I slide clips around without giving it a second thought (just considered it part of the work-flow). Internally I could care less about offset since I am rarely synching that to anything, but then it occurred to me that the delta on my Saffire may be from it sending the "expected internal" offset rather than the "expected external" offset to SONAR (or possibly that it sends both and SONAR is using the wrong one).
 
Anyway... I also found another "non-intuitive" thing in SONAR... since I was 76 samples late, I inserted a manual offset of "-76" and it ended up doubling it! Changed it to "+76" and the loopback was sample accurate. This is actually a very cool thread and is something anyone should consider trying.
 
I also wanted to point out another thing I would "judge" an audio interface by... simple engineering definitions of "precision" and "accuracy"... Thinking in gun shooting terms, "accuracy" is how all-over-the-map one gets shooting at center... "precision" is putting a bullet through the same hole in the paper each time regardless of accuracy. When precision never wanders, accuracy is a simple sight (offset) correction... but when precision wanders, you are pretty much screwed. That said, my Saffire is 100% precise, which offset will correct accuracy on... but a few of the examples above show "walking precision" which makes them "highly inadvisable" for an audio interface.
2015/03/12 17:59:14
DeeringAmps
Just got an RME BabyFace for the office rig.
1 sample early with Buffers 48 to 2048.
Some screen shots:


"Spot On" with the added +1 Manual Offset: 48 to 2048.
I did some editing at 48 samples on a fairly simple project (11 audio tracks).
Lots of ProChannel; EQ, Concrete Limiter, Breverb, Tape emulation.
Never a "hiccup".
This on a little Win7x86 i3 4 gbs ram.
Maybe I'll go back and throw some Console emulation just for S&G.
Gotta love them RME drivers...
T
2015/03/12 18:11:48
pentimentosound
Wow! Thanks Tom. That ought to make me go right out and buy one! LOL Actually, I'm waiting for a reply on a FF800 (though I'd need a FW PCIe card, too). I talked a buddy into getting one and wonder why I never did! SHEESH Using Budget as a rationalization is always bad! LOL
 
Michael
2015/03/12 18:33:23
DeeringAmps
Checkout Jim's thread, the MOTU Ultralite AVB does even better; 4.9msec at 64 samples.
http://forum.cakewalk.com/MOTU-Ultralite-AVB-m3190029.aspx
Are we approaching mental telepathy?
T
2015/03/13 01:32:25
Cactus Music
I guess we should all bite the bullet and get RME or Motu and be done with it. But we knew that before I started this thread. What I'm stil after is those el cheepo interfaces.
 
So getting back to el cheepo interfaces.. ( tascam us1641 $199  with Cubase LE 5)  
 
A bit of a surprise today. in my first post I originally tested my Tascam us1641 and the results were less than stellar. 400 samples early.. That's around 10 ms @ 44.1.  I never thought that the performance of a driver should be much different from computer to computer but I just found out this is not true. The computer must make a big difference. 
I originally tested the Tascam on a new machine I built as an office computer. It's good stuff but with a wimpy processor.  But the rest is not a heck of a lot different than my DAW. 
DAW= Gigabyte Z97X-SOC-  SSD- 16 Gigs RAM - Intel Core i5 I5-4460 Haswell 3.2GHZ Processor 
 
Office = ASRock H97 PRO4  -7200 HD- 8 Gigs RAM - Intel Pentium G3220 Dual Core 3.0GHZ 
 
Both are the same OS windows 8.1 and all tweaking was the same. 
I have a 4 piece  Jazz combo coming in next Monday so will have to use the Tascam as I need 8 channels. So I installed the new drivers from Dec 2014 on my DAW  and fired it up. On a whim I did the loop back test and what the heck? It's only about 16 samples early? This is  a big improvement over the 400 samples on the office computer. So now I'm seeing a new aspect to the building of a DAW.... I wonder what will happen if I test the Tascam on a top of the line i7??  
So this is good news for Tascam owners, if these new drivers they are writing in house are much better. 16 samples seem to be close to what most are reporting. So now I will test the Scarlett on the office build and see if it performs is worse. 
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account