-
VP 18, 19, 20 (Trial)–Stuttering, Freezing, Wrong Clip in Preview
After getting back to editing a few days ago after a few months’ hiatus, I observed that in VP 19 Build 651 after working on the timeline for a few minutes the video begins to stutter, freeze, darken and then the screen starts showing the wrong clip. While continuing to play the clip it is evident that clip A should be playing but clip B is what I see. If I close VP 19 and open it again, everything is fine for a minute or two and then this anomaly reappears. I tested this project and a few others in VP 18 and VP 20 Trial. VP 20 Trial gives the same results, while VP 18 works fine for about 5 minutes before it also exhibits this problem. Has anyone else ever experienced these problems? WEIRD!!
HELP!
Up to date on my NVIDIA 2060 Super video studio driver and Win 11, and considering the problem, I’m thinking that it may be a cache or buffer issue. If so, I believe there is a way to load either of these VP versions to set everything to default. Not wanting to lose my settings across the board, if I load VP 19 this way will it also affect VP 18, or will I be able to load VP 18 with all of my saved preferences, which I don’t want to give up?
So exactly how do I flush the cache/buffers, if this is in fact the problem?
Any help on these issues will be most appreciated, as I need to get back to work NOW! As it is, I currently only can work for a few minutes in either of these VP versions before I have to close and reopen the app–this is the only way it works, but will cause me HOURS of extra time to edit.
Thanks in advance!
-
5 Replies
-
1. Does this happen with all kinds of footage across the board? All formats affected equally?
2. Have you looked at the performance tab of your Task Manager when this happens? Especially at what’s happening with your GPU? And RAM?
3. Are you working with 4K+ footage? In that case might be worth a try to use proxies if you aren’t already.I’m fairly certain this stems from some GPU/memory issue or maybe some compatibility problem.
Could try and change some File I/O settings, see if it makes a difference. Options -> Preferences -> File I/O -> Enabling/disabling legacy decoding and changing RAW/Hardware processors in use. Don’t think I can recommend the “right” ones – it’ll be down to experimentation. -
I have made no changes since my last successful editing session a few months ago. So before I do a full reset it was suggested that I manually delete all of the cached files, but I do not know where they reside for VP 18 and VP 19. Does anyone here know where I can find the cached files for both of these versions?
-
The temp files folder you can find by going to Options -> Preferences -> General and at the bottom you’ll see Temporary Files Folder path. You can delete everything in the version folder or move it to another folder if you want to be safer.
-
FINALLY, AN APPARENT RESOLUTION!!! WE HAVE BEEN BARKING UP THE WRONG TREE AND HAVE LED OURSELVES ON A WILD GOOSE CHASE!!!
For some reason, the New Blue Color Fixer Pro plugin has caused all of the anomalies that I reported experiencing when used in ANY version of Magix Vegas Pro in which I tried it (VP 18, VP 19 and VP 20). Having stumbled upon this as a possible source of the problem, I substituted a similar Boris Effects Plugin in the place of Color Fixer Pro and have not experienced any problems whatsoever! Eliminating Color Fixer Pro apparently has resolved the issue!
I have regained FULL use of my graphics card and set the RAM Preview at 50% of my installed RAM. No problems editing or rendering (at full speed) during the past half dozen or so editing sessions!! Knock on wood (LOL)!
Thanks again to everyone who chimed in to try to help, and I’m sorry that you all wracked your brains out. So the moral of the story is ALSO to check out if plugins may be the culprit when such anomalies arise BEFORE jumping through all of the hoops that I had to go through! What an educational and learning experience, though!!
Thanks again!!!!
-
Hahaha, sometimes the problem really is right in front of you, glad it’s resolved!
Something to take away then – when testing such issues, need to minimize the amount of variables in the test cases.
Reply to this Discussion! Login or Sign Up