Making gain changes to a waveform

Hey Guys, I wonder if anyone can answer this one for me, either tell me what I'm doing wrong, or how to stop it...
This is not Splat. Started for me in X3, but still continues. If this has come up before, I apologise. I've done a search, but found nothing.
 
Today, I need to seriously attack a guitar track. Remove a lot of muted pick strokes, and dull the rest by using the gain. Mostly, I was splitting, then fading both backwards, and forwards, to reduce the attack and decay, and amplitude, of the unwanted pick muted clicks, but in sections when 3 or 4 such clicks were together, I use the gain function to reduce the gain by around 16db or so, so almost knocked out of the park. But, using the gain option, when zoomed in to the waveform, reducing the gain would cause the following waveform to suddenly jump sideways, by around 2 measures, out of place to the timeline, showing a section of zero amplitude in it's place. It still plays as if it is showing correctly, ie, music plays through the zero'd section. If you zoom back out, it magically puts everything back in it's rightful place. Zoom back in again, it goes back to being wrongly situated. The problem is, you can't work on the next bit of waveform, because there is nothing to select, where it should be. If you select the section that looks wrong and bounce to clip, it fixes it. Until you move onto the next section of the track to work on, and it all starts again. A long an painful process considering the track I was working on was something akin to Richie Blackmore doing his machine gun parts.
 
Like I said, for me, this has been since X3. I don't usually do this much work to a track, preferring to record it again, but on occasion, it's necessary, and it makes it extremely hard to focus on what your doing whilst being tripped up all the time. I know this can be done using Melo, but this should work too, and it's easier just to move along changing everything the way I want as I go.
 
I know I havn't explained this very well. I'm not at my studio at the moment, so can't take snapshots, but hopefully someone knows what I mean and might be able to lend a hand or know what the answer is.  cheers. Dave.

Whats wrong in using automation? 

John
Whats wrong in using automation? 

Too intricate John. Is possible of course, but not the answer for what I'm trying to achieve. I often use this process when 'clipping' bass takes as I call it. Makes it punchier, and you have complete control over every note. But, this has always been what happens to me. It only happens if zoomed in to each wave envelope. Interesting it doesn't happen to others then, so it must be something in my setup.
 
I'll get some shots up as soon as I get back home tomorrow.   cheers.

Thanks Basseman. That's exactly what happens. Yeh, I know you can get around it somewhat, but there is the odd occassion where it really does interfere with my work process. And to just re-affirm. I love Plat. Best version ever. Not bagging anything. Just making sure I'm not doing something wrong.
 
cheers
Dave.

I dont understand how updating the graphic drivers could fix this. It's not the video display that's gone haywire, just the view of the clip, and where it sits on the time line. Nothing else is affected. zoom out, and it's all good. It only happens if you apply an effect to a segment of the clip.

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.

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.

Basseman
@NebRanger
 
With 2 Clips side by side, zooming in the unchanged clip display correct, the changed clip does display false!
 
I don't think this is a driver problem!!
 
Bassman.
 

As is said, most likely Sonar is sending bad image data somewhere along the line, or (even more likely) ignoring waveform image generation randomly. Inconsistent bugs are hard to nail down.