I think, through trial and error, I've narrowed down my latency issue to Reaper specifically. Here's the results of my 'testing' (obviously not super scientific but fairly conclusive). - - - - - Overview: The TASCAM US-1200 will produce very low latency on an XP Laptop on an old Pentium Dual Core @ 2ghz with 2GB RAM.

6.5ms round trip (Reaper report which can be optimistic). Playing with a click track with a digital piano monitored both via Reaper and directly through the US-1200 Using Reaper 4 on OSX 10.10.4 with Core 2 Duo 2.2 (2010 MacBook Pro), 8GB RAM, SSD is 87ms. With buffers dropped to 32 you can get 76ms. This is using the Core Audio driver (not bit accurate which won't work). Drivers were uninstalled and re-installed. Reaper was reinstalled. Using Garageband on OSX with the same specs above, you get no perceptible latency with core audio or bit accurate drivers.

The US-1200 is designed to clearly translate expressive performances to a DAW 6 Analog inputs for Multi-Channel Recording The US-1200 is loaded with 4 XLR connectors supplying +48V phantom power and 2 TRS balanced inputs. Jul 27, 2015 - Reaper Latency with TASCAM US-1200 REAPER for macOS X. This is using the Core Audio driver (not bit accurate which won't work).

In conclusion, TASCAM's hardware and driver seem solid. Reaper for OSX has some issues with this hardware. It sounds like you have identified a bug in their OSX driver. Normally Reaper in OSX is the most stable (and stable at the lowest latencies) DAW system there is. Just to rule out any obvious operator error. Can you confirm that you have the box checked for 'block size' on the Reaper Preferences/Audio/Device page and (after checking the box) you have entered the value in samples?

There are a few more options available here in OSX. Not checking that box for example, tells Reaper to give control of this parameter to another app or control panel and any value entered would be ignored. Thanks so much for your time.

Yes, I've messed around with block size a lot. I suspected that's where the fix would be. It does fix it. -10ms @ block size of 64 to 76ms total. So the fix just isn't enough. Quick question: Why do you suspect the drivers, particularly given solid hardware performance in other DAWs?

Seems if there's a fundamental driver flaw it would appear in all DAWs. That said, the sample set is pathetic - 1 DAW (Garageband). I have Logic but am not keen on loading it just to get an absolute latency number.

I've tried two. I've let the hardware decide and I've manually set 44.1.

RPCS3 is an open-source Sony PlayStation 3 emulator and debugger written in C++ for Windows and Linux. RPCS3 is an experimental open-source Sony PlayStation 3 emulator and debugger written in C++ for Windows and Linux. RPCS3 began development in May of 2011 by its founders, DH and Hykem. Rpcs3 emulator mac.

And I think you're right about a quality interface. You get what you pay for. And this Tascam unit really does 80% of what I want (track rehearsals, latency a non-issue).

But my inner computer nerd is saying, 'WAIT! There's something wrong. I hate that inner compute nerd sometimes. $118 for six channels and 4 preamps? Something's got to give. Although that's not quite fair because Tascam and Reaper tick along quite nicely on an XP laptop.

I'm going to test a few other interfaces today on OSX and see if Reaper reports improved latency. If so, then I think we can conclude it's indeed a driver issue. Tascam may have tested their drivers with Apple apps, ProTools, etc. But not anything else. I've tried two. I've let the hardware decide That.

Doesn't work that way. You set the hardware to run at the sample rate of your choosing (44.1k, 48k, 88.2k, 96k, or 192k). With multiple hardware units, you further choose which one to use as the master sample rate clock and sync any other units to the master. The fact that you're passing audio without mad clicks and pops suggests that the single interface likely defaults to something (probably to 44.1k). Just saying - this is user selectable.

And it's the heart of a DAW system - not exactly trivial. .and I've manually set 44.1. Try 48k and see what you get when you run a loopback test. Make sure you're not converting on the fly or anything. Reaper lets you make some very wild settings for this stuff. (You can run the hardware at different clock rates vs.

The project, etc, etc, etc.) Make sure the sample rate is set intentionally in File (menu) > Project Settings (check the box next to it). Make sure the sample rate is set intentionally in Reaper Preferences/Audio/Device page (check the box next to it). Verify on your interface (indicator light) that it's set to that sample rate.

If your interface has its own control panel app, check this and make sure the sample rate has been set by Reaper. Further make sure the interfaces clock is set to 'internal'. I suggest 48k because it's usually the most efficient (easiest to achieve lowest latency for the system).