slyman
 
FYI, as a bonus, Focusrite is offering a free XLN Audio Addictive Keys instrument licence in February.
 
 

Yes, the PlugIn Collective is a great Focusrite benefit. The interface kind of pays for itself if you use the free plug-ins. I thought of mentioning it before, but didn't want to cloud your judgement.
 
I'm glad you're liking it and getting good results.

I have to correct the info´s I gave about the latency of the UR 22 mk 2, 
knowing that the OP already made his decision
I managed to run the UR 22 with 4,7 ms rtl /64 samples on my laptop.
 
Sorry for the misinformation.
 
Pragi
 

Is that actual or driver-reported latency?

I take my RME out often.

I wouldn't even consider a cheap interface because I was afraid of damaging the RME. That thing travels great.

With a backpack of stuff I can make a great 8 channel recording. Mikes and cables take up the majority if my packing space.

When bringing copius gear, I have two plastic boxes full of Mics and cables, a 6u rack, and a backpack for the computer. I can catch sixteen tracks this way. I can add another eight channels bringing my Tascam 2488 and synching on SPIDF.

When planning to broadcast the recording while I catch it, I bring my studio cat computer... 4u... and my touch screen. The touch screen is nice because I can modify the mix silently.

Sanderxpander
Is that actual or driver-reported latency?

Don´t know what you reckon by saying  actual reported  latency,
 it´s 4,7 ms rtl  / 64 samples reported by Splat.
 

Actual latency (not "actual reported") is what you get by measuring it, because there can be errors (sometimes significant ones) in what the driver reports. E.g. driver reported latency usually doesn't include AD/DA conversion which for some interfaces adds a significant amount of time.

Sanderxpander
Actual latency (not "actual reported") is what you get by measuring it, because there can be errors (sometimes significant ones) in what the driver reports. E.g. driver reported latency usually doesn't include AD/DA conversion which for some interfaces adds a significant amount of time.

Ok,if you like to get the actual latency info you have to 
describe how to measure it.
Seems that you don´t believe that the ur 22 mk can manage that latency,
but this audio interface is recommended by many specialitsts cause of the
good rtl values, you know ?
regards
 
 

I'm fine with not knowing because I don't want to buy that card, it's just important to state if it's real latency or reported latency. If you want to know the real latency, play back a mono track (preferably something percussive) out of one of your outputs and record it (also mono) through one of your inputs (be careful to disable monitoring). Now put the tracks next to each other, zoom in and see how many samples the rerecorded one has shifted.

Sanderxpander
I'm fine with not knowing because I don't want to buy that card, it's just important to state if it's real latency or reported latency..

But you asked  in post  33 :
Is that actual or driver-reported latency?
 
So  ?
Is it for you just important to state if it´s real latency  ? or
Are you fine with not knowing because you don't want to buy that card ?
 
It still seems that you don´t believe that the ur 22 mk can manage that latency,
I´´m trusting the Splat reported 4,7 ms rtl ,don´t you ?
 
 
 
 
 
 
 
 

Sanderxpander
I'm fine with not knowing because I don't want to buy that card, it's just important to state if it's real latency or reported latency. If you want to know the real latency, play back a mono track (preferably something percussive) out of one of your outputs and record it (also mono) through one of your inputs (be careful to disable monitoring). Now put the tracks next to each other, zoom in and see how many samples the rerecorded one has shifted.

 
That is not testing RTL, that is testing Sonars Offset adjustment which is based on the driver reporting the RTL. Most good ASIO drivers will get this bang on and nothing to worry about, But this test with the same interface using WDM ,WASAPI or MME will result in the offset being out and sometimes by a lot. 
Almost any interface will report low RTL figures at 64  buffer,,,, but is your system stable? Do you get drop outs or crackles?  This is the big difference in quality drivers/ firmware of interfaces. And it certainly helps to be running a powerful optimized computer system.  And don't forget those "hidden" buffers most interfaces under $500 seem to sport. 
At what RTL is your system stable? Nothing else means diddly squat. I can get 3.4 ms with my Scarlett but it will result in drop outs. 
a Stable system @ 7ms is par for the course with the under $500 price point. 
 

 
And note that this test as shown above does not differ in results at ANY buffer setting. And for me it did not differ between both tmy Tascam and my Scarlett interfaces. But interestingly the Scarlett does not seem to support WDM or MME mode for me so I used the Tascam.