I have been able to test on my Windows 7 machine at work today. And it didn’t show the problem either. So this problem remains a bit of a mystery
Two differences between my “main” machine, which shows the problem, and the other two (laptop + machine at work), which do not show the problem, are: The “main” machine has two screens with “full hd” resolution, while my laptop and my machine at work have only a single screen each (and with lower resolution). Furthermore, my “main” machine uses a dedicated graphics card (GeForce GTX 660 Ti), while the other two use Intel “on board” graphics.
Unfortunately, I have no other machine that has a dedicated graphics card and is connected with two “full hd” screens…
When Audacity draws the waveform, the image data is temporarily stored in memory so that it can be retrieved quickly with minimal load on the processor. The waveform is therefore only redrawn when necessary, thus improving overall performance. If the audio data is changed, then the waveform has to be redrawn (often this takes as much time as processing the audio, which is why redrawing is avoided when possible).
Another case where the waveform is redrawn is when there is a substantial change in the zoom level.
When zoomed out a long way, the waveform is drawn based on calculations that take an appropriate amount of detail.
When zooming in much closer, the waveform needs to be redrawn so as to show extra detail. In this case Audacity will probably not draw the entire waveform, just a bit more than shows on screen.
What I guess is happening, is that your high performance dedicated graphics card is also doing its own caching. (Running two Hi Def monitors requires a huge amount of data). Unfortunately it seems that your graphics card is not quite “smart enough”, and can be tricked (by rapid scrolling) to hold old cache data longer than it should, and so sometimes display low resolution (pixelated) waveform data rather than the most recent waveform data. A driver update for your graphics card (if available) may solve the problem, or making less demands on the card (for example, running only one monitor, or using lower definition, or a lower refresh rate).
I think it would be kind of extraordinary if this problem shows up only in Audacity, while all other applications work absolutely flawlessly - many of which are much more demanding for the graphics card.
Until I spot a similar problem in another application, which I have not (so far), I have to suspect that it must be a problem on Audacity’s side. Triggered only under certain conditions…
As mentioned above, I already use the latest WHQL drivers.
For LCD screens you don’t have much alternative to running on the “native” resolution (anything else will be interpolated to the “native” resolution by the screen anyway). And you certainly wouldn’t want that
Same about the refresh rate. Pretty much all LCD screens run at 60 Hz. Some of those fancy new “4K” screens can do only 30 Hz (because of a bandwidth limitation of the DVI connection) and the result is that the mouse cursor doesn’t move smoothly anymore.
Yes but you are describing a very specific problem involving cached data.
Except that your other machines with the same version of Audacity do not produce the problem, my machine does not produce the problem, none of the Audacity developer’s machines produce the problem, none of the thousands of forum users have reported the problem, and none of the millions of other Audacity users worldwide have reported the problem, which would lead me to think that it is something to do with your machine.
I have once come across a similar issue (about three years ago), and that turned out to be a problem with the video drivers.