When I used to edit projects with the segmented clips straight from my cameras, I would occasionally see issues like that at some points where clips abutted. I thought that was probably a buffering issue too. Have not seen the issue since I started joining the segmented camera clips before pulling them into Vegas. Another related issue I've seen on occasion has to do with the length-times in the metadata of some clips causing the 1st frame to repeat at the end if loop is enabled for the clip in Vegas... my workaround for that was to set the switch to HOLD LAST FRAME or TRIM EVENT for all clips instead of LOOP.

Maybe it helps you to use the latest build 187 of V21 and the latest Nvidia driver 546.01 notebookdriver

Thanks, I'll try 187 as soon as I can finish my current project.

Be sure to turn on Snapping and Quantize to Frames before adding any files to your NEW project.

Any project files created with those settings unchecked are possibly fubar.

When I used to edit projects with the segmented clips straight from my cameras, I would occasionally see issues like that at some points where clips abutted. I thought that was probably a buffering issue too. Have not seen the issue since I started joining the segmented camera clips before pulling them into Vegas. Another related issue I've seen on occasion has to do with the length-times in the metadata of some clips causing the 1st frame to repeat at the end if loop is enabled for the clip in Vegas... my workaround for that was to set the switch to HOLD LAST FRAME or TRIM EVENT for all clips instead of LOOP.

Thanks for your reply! There is a setting on the Preferences | Editing tab that is called "Enable looping on events by default". Is that the one you are referring to?

@TMTV Hi, I don't know if it will fix your problem but 'Nvidia graphics driver v-537.42' is the Game Ready Driver, try swapping to the Studio driver.

Thanks for your reply! There is a setting on the Preferences | Editing tab that is called "Enable looping on events by default". Is that the one you are referring to?

@TMTV Yes, but that only affects the default used when you create a new project and I think also when new clips are dropped onto a timeline of an exiting project. To change the setting for a bunch of exiting clips in an exiting project, I select them all, right-click, and use Switches in the context menu. Properties also has the setting in Project Media but only affects one thing at a time.

Thanks to everyone for the great tips. I have tried them all except changing the graphics driver. I did disable the GPU decoding on the video tab and also the hardware decoding however. I have also tried using the File / Close and then File / New function, to clear the timeline before loading another project. However the intermittent problem remains. I have some new information however, If a project file exhibits the problem, I have tried closing that and creating a New project and manually loading the source file. The manually loaded source file, which is an MOV container filled with video from a v210 codec, exhibits the same problem. If Vegas is then closed and reopened, the problem is gone from both-- for awhile. After restarting Vegas, it *seems* the problem only starts occurring again after some edits have been made on the timeline-- on the first or subsequent file after reloading. After that first file, the second, third or fourth subsequent file loaded will usually exhibit the flash frames, usually toward the beginning of the clip. In addition the audio track may also be affected (but not 100% of the time). That is, say for example if there are bars and tone laid down at the head, one may see still frames from the previously edited file interspersed with the color bars and the tone may go in and out, in sync with the flash frames. Interestingly when that happens, the tone disappears from under the color bars and remains under the flash frames-- the opposite of what I would expect.

Still welcoming suggestions if anyone has any. Otherwise, I'll slog through to the end of this project and then install the latest Vegas update to see if it solves that problem. A couple things I'm wondering about but haven't had a chance to investigate yet are 1> If the MOV container could be giving Vegas a fit. I usually use (with prior versions of Vegas) V210 source files in an AVI container instead of the MOV in use this time (due to equipment availability issues). When I ran the test I mentioned above by substituting an existing project with a new empty project and then adding the source file, I originally added the *same* MOV file used in that project that was substituted out. As a test, I also tried substituting a rendered-out, v210 AVI file instead of the MOV and the problem was not present. That is not a perfect test however as the AVI file had been edited in length so the frames were not in the exact same place as the original MOV. I need to take the time to transcode the *original source* file to AVI for that test to really mean anything. 2> Another potential issue that I haven't had time to test yet is using a different drive for the source file, to see if some strange buffering or caching is taking place. I will try to do those tests as soon as I can and report the results. Thanks again to all for lending an ear and for your suggestions! /RB