neuticus wrote:TheOrganDoc wrote:Hi,
I quess if all else fails, you could use a inexpensive second computer, for the Music Display !
That is precisely how I solved the problem of page-turn-induced audio glitches on my Mac-based system.
Just to add some personal experience on this topic. For me, an Hauptwerk user since middle of 2015, I always shared a single tablet PC computer between the tasks of hosting Hauptwerk engine itself, operating it and reading/annotating PDF music files. It was never a 100% reliable combination, but glitch resilience became gradually worse since some Windows 10 updates, specially after CU release. DPC latency checks had rarely shown spikes, even during Hauptwerk meter spikes and/or audio glitches, second to some tests I did in the past. Turning all mobile battery-saving and performance-related features off in BIOS and Windows had not solved neither. I use Cantabile as a VST host, but the audio performance is the same with Reaper or Steinberg Cubase, or Hauptwerk-->ASIO interface direct output. The change that produced better results (but not 100% perfect) was to raise buffer size to 1024. But this, associated to Dirac Live own latency, turns the whole Hauptwerk setup intolerably laggy. One thing that occurred since my first Hauptwerk day among three different notebooks was HW CPU meter spikes, even when there's no load at all. Yesterday, looking for the cause and a possible solution for this, I tested a suggestion made by another user, to rise Hauptwerk process to realtime priority. Bingo. HW meter spikes disappeared. And the best thing was to come. All kind of audio glitches, even on some torture tests, in unreal situations, disappeared also. Now, I can even set buffer to 256 frames with a simple Steinberg or Focusrite USB audio interface, turn/jump/drag complex 2 or 4-page screen arrangements, changing opened PDF files, active pen annotating and switching application through touch movements (both operations cause sudden CPU usage increasing), nothing cause a single audio glitch anymore, even when done while playing the console or a recorded MIDI file. I did even a torture test, like streaming three audio/video sources while doing all those tasks. NO AUDIO PROBLEMS AT ALL!
I know this process priority changing is not encouraged nor supported by HW documentation or staff. Also, I do not know if there would be a hidden drawback in long run. But until now, this was the only thing the really and hugely increased resilience to audio glitches. Hauptwerk process priority change was made permanent using System Explorer (http://systemexplorer.net/).