![]() If so, then I think we can conclude it's indeed a driver issue. ![]() I'm going to test a few other interfaces today on OSX and see if Reaper reports improved latency. If nothing else, you'll be armed with hard facts and numbers for any tech support call. ![]() You're aiming to do live sound work at low latencies that are under human perception so it's always a good idea to shake down your system and get a baseline for what the hardware can do. You can experiment and run your loopback test at every sample rate (and determine the lowest block size that still works). I suggest 48k because it's usually the most efficient (easiest to achieve lowest latency for the system). Further make sure the interfaces clock is set to 'internal'. If your interface has its own control panel app, check this and make sure the sample rate has been set by Reaper. Verify on your interface (indicator light) that it's set to that sample rate. Make sure the sample rate is set intentionally in Reaper Preferences/Audio/Device page (check the box next to it). Make sure the sample rate is set intentionally in File (menu) > Project Settings (check the box next to it). (You can run the hardware at different clock rates vs. Reaper lets you make some very wild settings for this stuff. Make sure you're not converting on the fly or anything. Try 48k and see what you get when you run a loopback test. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |