![]() Plugging it back in works fine untill changing sample rate, but it's not a 100% crash on change. ^ Gives a crash on launch after selecting a new rate until interface is removed from the machine entirely, and a new one can be selected. The same settings in W10 give nothing but artifacts, pushing up to 8-10ms clears artifacts, but round trip then hits 20+~ms and monitoring is no longer posible for anything above 60bpm.Ĭhanging sample rate via the driver and then hitting apply now also throws and error most times. In Win 7 on the same machine I was getting a round trip of around 12~ms on my Focusrite 2i2 and the buffers set for 6ms in driver and sample rates of 96k for an entirely un-noticable latency. I7 3770k, 8Gb RAM, Z77 Chipset running on an SSD for all recording files and a WD black 7200 for everything else, Interface doesn't matter, all three I have access to can no longer achieve "low latency". Las razones por las que unos auriculares no funcionan en Windows 10 pueden ser muy variadas. Coming from W7 onto a newly upgraded W10, spending the last day or so making sure all drivers are current and W10 compatible and trimming out all the unneeded services and background processes, I've lost all "acceptable" ASIO performance.
0 Comments
Leave a Reply. |