If you don't have manufacturer-specific ASIO drivers for your device, see if WASAPI is available in the list of available drivers in Reaper. (edit)D'oh! Nizhny Tagil said this already!(/edit)Ĭhances are your latency is higher with ASIO4ALL than with any other driver choice available. Try a loopback test of your latency using something like this: The reported ~6ms of ASIO latency is practically meaningless. Since ASIO4ALL is a wrapper for a "normal driver", the latency of the other driver "wrapped" in ASIO4ALL needs to be added to that number. The latency reported for the ASIO4ALL driver in Reaper is only what the "ASIO part of the latency" is. If you don't have an audio interface with low latency ASIO drivers, I think that should help, too. You could record the MIDI monitoring through a different virtual instrument that doesn't add too much latency, like Kontakt, if it works for you, and then replacing it with EZ Drummer when you've recorded the part. If this is the problem, there are a few things you could do to avoid too much latency. It should also report if any plug-ins in the chain are adding latency, though it doesn't always do it. If that is it, I think it could be the plugin itself adding latency to the round-trip latency you already have, which as I said may be higher than what Reaper reports.Ĭheck under the FX box of the track where you have EZ Drummer, where Reaper reports the CPU usage of the plugins. (I am thinking of getting a focusrite scarlett 2i4).īy recording drums via EZ Drummer you mean using it as a virtual instrument, playing notes on a MIDI controller like a USB keyboard? I wonder if this could be a case of needing a new interface with lower latency after christmas. What I meant was that if I am recording drums via EZDrummer, there's definitely latency in the input (probably about 0.5s).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |