I am testing this on a machine with the latest generation i7 CPU and usually I have more than enough CPU power for anything music-related. I tried everything you mentioned and what happened was that i clicked record in the track and in the mixer and it didnt even record, same for both ASIO and WASAPI.Īnd i went to change system sounds and it was 24bit and 44100hz and i did it also in reaper and still nothing. It sounds like it cant sync to ASIO buffer no matter which buffer size, which leads me to believe it is some kind of a bug, rather than underwhelmed real-time CPU cycles. * Side note: With the default sample rate and buffer size settings, Direct sound has a latency of 185 ms and WASAPI has 10 ms. Or using WASAPI (instead of, for instance, Direct Sound) *.Or connecting the TASCAM to a different USB port. If the problem with ASIO persists, try: Restarting the computer to see if this makes any difference. Or connecting the TASCAM to a different USB port In general, the recommended audio systems under Windows are primarily ASIO or WASAPI.Restarting the computer to see if this makes any difference.In general, the recommended audio systems under Windows are primarily ASIO or WASAPI. If you're using the TASCAM also as default audio device in Windows, make sure to use the same sample rate and bit depth settings in both Reaper and Windows (to avoid a possible sample rate mismatch): I bumped it down to 512 and tried opening Pro Tools again and it worked like a charm I recommend checking the audio hardware buffer size and if its high Id say bring it down and see if Pro Tools will load properly.

I'm assuming that this is a typo and should read 'Error initializing ASIO drivers'. The ASIO Buffer Size had gotten set all the way up to 2048 somehow.

Sar error initializing asio buffers