MacFurse
Not how it works. Video is not 3d. If it was a total zooming error then I would have been a sus to my graphics card or driver, but this is merely the picture being 'sent' by Sonar, not how is being processed.
With all due respect, I'm going to have to say this isn't entirely correct.
EVERYTHING under Windows sends image data in batches to Direct3D, regardless of whether it's two-dimensional or not, before it is displayed on screen. Different programs implement this differently, so it's entirely possible Sonar is rendering its vector image data in layers before it sends to D3D (everything is vector before it gets rasterised by D3D on the GPU), and somewhere between D3D and the completed render data is getting fudged by the rasteriser. It happens more than I'm comfortable with.
This is also why updating GPU drivers would fix (or hide) the problem--every driver update makes changes to the way Direct3D and OpenGL interact with Windows and the GPU. Rendering chain on any given system is usually application -> driver -> Direct3D / OpenGL on GPU -> output. Change one element and everything after it is affected.
TL;DR: Either Sonar itself is sending bad data (most likely cause), which is being corrected in the driver, or the older driver was misinterpreting vector data sent by Sonar before sending it to the GPU to rasterise. Would also explain how audio is playing through the "zeroed" tracks. Believe me, I've experienced this too, and it's pretty weird.