- WIN10 RS4 update will fix the problem (February 2018) !?!.- All memory used in a real time process must be Virtual Locked !?!.Then we got 2x information in the same time: The result is pretty clear: the Page Fault interruption system process is just blocking our memcopy operation for an eternity. So I made the same test with WASAPI Render thread (instead of ASIO Callback) to be able to send a 100% Microsoft incident in WIN10 Feedback HUB. Then we posted a first subject in Microsoft Social Forum: "WIN10 Major Issue for Audio Processing (OS special mode for small buffer)" and on wdmaudiodev mailing list as well.įortunately there is one guy at Microsoft who cares about audio: Matthew van Eerde asked for a trace to see what could happen. We found a possible explanation in the Microsoft Document called " Low Latency Audio", suggesting that Microsoft changed something in memory management for small buffer used in audio stack.
But without virtual memory (no paging file) we did not understand why memory access could produce such interruption. The sure point was that the incident was occurring during memory operation.
The interruption was occurring on a simple buffer copy (that we call “BUS copy”) where we were just copying 128 audio buffers from a BUS to another, so we searched for memory management problem or memory access penalty… At this time we had reproduced the problem on several WIN10 configurations, with different ASIO drivers, and by removing maximum Windows options and services (no virtual memory, no onedrive, no win update, no visual effect, power management to max, no firewall, no defender…).
0 kommentar(er)
