As some users of this forum will know, I have a digital music display on my central monitor. Occasionally in the past but becoming a bit more frequent to the point of being a nuisance, I am experiencing brief but annoying static sounds when I turn the page.
I use Adobe Acrobat to display music fullscreen, two pages at a time. The MIDI signal from the page advance piston is converted by Bome's MIDI translator into a key stroke sequence which in turn triggers an Autohotkey command to bring Acrobat into focus (if it isn't already) then advance the page. The static sound coincides with when I hit the piston.
Initially I thought it must be something to do with the slightly convoluted way of turning pages digitally that I devised, since Hauptwerk can't yet display pdf files in one of its windows (is that an enhancement request I hear you say?)
However, I can recreate the static sound without the need to press any pistons by doing the following sequence:
(i) displaying the Hauptwerk window across both the centre screen and one other screen;
(ii) opening an Acrobat pdf music file to fullscreen on the centre screen (which has the effect of covering the part of Hauptwerk that is showing on the centre screen);
(iii) clicking on the bit of the Hauptwerk window that is on the side screen to bring Hauptwerk back into focus across both the size screen and the central screen too;
(iv) start playing something;
(v) whilst playing, click on the centre screen to bring the fullscreen Adobe music pdf back into focus.
I am playing with the performance window open that shows RAM ployphony and processing activity. Let's say I am playing Salisbury, full Great and Pedal so have about a third of the stops drawn. RAM is showing as about half full, polyphony and processing power are barely registering one green bar. But at the precise moment that I click on the centre screen to bring Acrobat into focus and turn the page the processor activity bar briefly shoots into the red and then back down to nothing again.
So it seems that something is massively overworking the processor to switch the screen from showing Hauptwerk to showing a pdf file. Both images are pretty static so I can't see why there shold be a massive demand on the graphics card. I haven't tried with alternative pdf viewers like Foxit, though I might need to. But before going down that root (and rewriting a number of Autohotkey macros) I wanted to share the problem having found a way of reproducing it purely with Hauptwerk and Acrobat running in case it's something that can be ameliorated by changing settings in one or other program.
For the record I am running Windows 7 Professional, whatever the latest version of Acrobat is, I have 24GB RAM, an SSD hard drive, a six core i7 processor and two graphics cards so it's a fairly heavy duty machine, and not your average netbook. I would therefore have expected that switching focus between Acrobat and Hauptwerk should be child's play for it but clearly not!
Thanks for any help.
I use Adobe Acrobat to display music fullscreen, two pages at a time. The MIDI signal from the page advance piston is converted by Bome's MIDI translator into a key stroke sequence which in turn triggers an Autohotkey command to bring Acrobat into focus (if it isn't already) then advance the page. The static sound coincides with when I hit the piston.
Initially I thought it must be something to do with the slightly convoluted way of turning pages digitally that I devised, since Hauptwerk can't yet display pdf files in one of its windows (is that an enhancement request I hear you say?)
However, I can recreate the static sound without the need to press any pistons by doing the following sequence:
(i) displaying the Hauptwerk window across both the centre screen and one other screen;
(ii) opening an Acrobat pdf music file to fullscreen on the centre screen (which has the effect of covering the part of Hauptwerk that is showing on the centre screen);
(iii) clicking on the bit of the Hauptwerk window that is on the side screen to bring Hauptwerk back into focus across both the size screen and the central screen too;
(iv) start playing something;
(v) whilst playing, click on the centre screen to bring the fullscreen Adobe music pdf back into focus.
I am playing with the performance window open that shows RAM ployphony and processing activity. Let's say I am playing Salisbury, full Great and Pedal so have about a third of the stops drawn. RAM is showing as about half full, polyphony and processing power are barely registering one green bar. But at the precise moment that I click on the centre screen to bring Acrobat into focus and turn the page the processor activity bar briefly shoots into the red and then back down to nothing again.
So it seems that something is massively overworking the processor to switch the screen from showing Hauptwerk to showing a pdf file. Both images are pretty static so I can't see why there shold be a massive demand on the graphics card. I haven't tried with alternative pdf viewers like Foxit, though I might need to. But before going down that root (and rewriting a number of Autohotkey macros) I wanted to share the problem having found a way of reproducing it purely with Hauptwerk and Acrobat running in case it's something that can be ameliorated by changing settings in one or other program.
For the record I am running Windows 7 Professional, whatever the latest version of Acrobat is, I have 24GB RAM, an SSD hard drive, a six core i7 processor and two graphics cards so it's a fairly heavy duty machine, and not your average netbook. I would therefore have expected that switching focus between Acrobat and Hauptwerk should be child's play for it but clearly not!
Thanks for any help.