I don't get an error like that though, the renders complete and give me a finished file. Vegas seems to think it's done OK! But you can see the problem both on the preview screen as the render takes place and in the finished file.

I had real problems with rendering as well, some has gone away, some still there.

@David Johns

Blast from the past: when I see flickering, when rendering using nvidea with some plugins, I put dynamic ram preview max to 0 (in the video tab of preferences), that usually fixed it for me. Best to restart your PC after the change.

@bitman Cheers for that, I'd forgotten that tip because I've such odd results with changing that value in the past. It doesn't explain why VP16 can do the project without error but not VP17 though, unfortunately.

So far our experience with Vegas 17 has been pretty unstable overall. It's almost impossible to get through an a half hour of editing without at least one lock up. Haven't lost anything mind you, just end up having to shut down and re-load the project and carry on a half dozen times to get through it. I'm sure the Magix team is hard at work squashing bugs at the moment - hopefully we see a new release soon.

@mikelinton are you editing a complex project with lots of thumbs? That seems to be the main thing causing lockups while editing, from what I can tell by assisting users around here. If so, reducing the number of thumbs displayed or disabling them on the timeline (you can do this in the video tab of the preferences menu) helps sometimes. Other times, updating the GPU drivers has helped, especially for Nvidia users not using the new studio driver.

If this advice doesn't help, please make a new thread so we can continue to troubleshoot without derailing this topic.

Update. Having had a response from Magix, it will render if I turn "GPU acceleration of video processing" off and set preview RAM to zero (although weirdly, it wouldn't render to H264 but would to H265; have me a stream error on h264).

Unfortunately, turning the GPU off makes for a very slow render so it's not really a viable "solution" :-(

I found a very fundamental difference with the AMD Vega 64 card when rendering.

4k rendering to Magix AVC and HEVC is absolutely stable !!!!!!!
No black windows, error messages, incomplete rendering.

With the Nvidia GTX970 card I had to set DRAM to 0, change the number of threads, render with CPU only, reboot Vegas before rendering ......

With an AMD card I have a DRAM 2000, the number of threads per processor.

And everything works perfectly !!!

As a transfer from Trabant to Ferari. :-)

Please can someone create a poll with a question "what card do you have a problem with rendering? AMD or Nvidia?

In regards to the OP, if I had to guess, I'd say "The main footage is colour tweaked via a parent track which has Magic Bullet Looks 4 on it." has something to do with it... maybe there is an incompatibility between it and 17. My reasoning is, haven't heard of similar issues from anyone else using that codec, or using any of the text generators. Maybe not the most educated guess, but can you try to remove MBL from the project, just as a test, and see if it renders out ok? Also, try to remove the parent track completely if removing MBL alone doesn't work, to further try to isolate the cause.

You're right - it's Magic Bullet. Don't know why I didn't think of that, duh. As soon as I disable that effect, it will render correctly even with GPU acceleration on etc. I have made sure I have the latest version of Looks (4.0.6) but no luck.

Very odd that it affects the rendering of other elements on other tracks like the jpg logo and legacy text but they were fine as soon as I disabled Looks. Also odd that it works fine on the timeline and only faulty on render.

I've submitted a support request to Red Giant.

In the mean time, use that new color grading panel! You can create your own magic looks with it very quickly, then save them as a LUT file that you can apply as a preset, or a "look", to any of your projects, or you can even send your LUT files to other people to use in other NLE applications (or even still image apps like Photoshop). I have a collection of hundreds of LUT files, it's like having my own custom Magic Bullet Looks that I can tweak or create anew anytime I like.

In regards to the OP, if I had to guess, I'd say "The main footage is colour tweaked via a parent track which has Magic Bullet Looks 4 on it." has something to do with it... maybe there is an incompatibility between it and 17. My reasoning is, haven't heard of similar issues from anyone else using that codec, or using any of the text generators. Maybe not the most educated guess, but can you try to remove MBL from the project, just as a test, and see if it renders out ok? Also, try to remove the parent track completely if removing MBL alone doesn't work, to further try to isolate the cause.

Yes, well, I was thinking about this. My timeline loads but, once first loaded, won't vertically scroll with out stopping, re-calculating, then jerking, then I can scroll again, but not to the top, one more re-calc stop..jerk...maddening. I do use a fair amount of tracks, maybe 10 to 15, but it is a short project, about a minute, and yes thumbz, but not hundreds. Even if I load the program and give it time to "settle in." (I'm on a z420 workstation, 6 Core Xeon E5-1660 v.2 - 3.70 Ghz, stock Quadro 2000 card) Now, after that, then I can scroll.....but with 64 gigs of ECC Ram, I would think some of this would not be an issue.

You would think a modern computer in 2019, with tons of RAM, would not have a problem with thumbs, for cripes sake.

I sort of wish, (oh never mind 'sort of' - I wish) that Vegas would re-write its code, same program, with fresh coding. Is that ever done? It seems to me this is a "long in the tooth" problem that one sees with older, legacy programs. I'm not a programmer, so I don't actually know what I'm talking about, but this is a pattern that is pretty clear, at least in my experience. Correct me, please, if I'm off base here.

It seems like Magix is slowly doing that, component by component, by writing new decoder DLLs and such, while keeping some of the old code base intact. Throwing the baby out with the bathwater and rewriting the engine from scratch would take some serious time, maybe a year or two, and they wouldn't be able to add a single feature. It makes it hard to sell a new product when all you can offer is "we rewrote the old software so it runs faster!", people want new features to justify the purchase. So, Magix seems stuck trying to slowly rebuild the old code, piece by piece, until they've modernized it. Considering how far we've come in 4 years, I'd say they're doing great.

They're aware of the thumb loading bug, we've been talking about it for a while now. I've told them it's the most widespread bug that consistently affects Vegas 17 performance, and suggested they put it first and foremost on the bugs-to-squash list, so hopefully when this first update drops, it'll be a thing of the past. In the mean time, since I never use them anyway, I just completely disabled thumb display on the timeline.

I would call that process anything but "throwing the baby out with the bathwater." You could, I suppose, copy back in certain things that work (again, I'm not a coder)....but put the thing on a more modern, solid coding foundation. It's not hard to rebuild the house if you have all the parts and know where everything goes. You get a better house, and without a more solid base, the old one just falls over eventually. Yes, it would take time. I don't think one serious Vegas user would balk at buying that UPGRADE without new, and sometimes clunky, crash evoking, not ready for prime time "bells and whistles" features. Seriously, i don't think there would be a single guy or gal that wouldn't PRE ORDER that version.