Popular cams render buggy Vegas Pro 18 build373, still in Vegas 19

TTTT wrote on 11/9/2020, 12:50 PM

I was working on a video in Vegas Pro 18 and things were going as usual.

At some point I decide to update to the latest build (build 373).

At first I had to waste several minute, hide and then re-show the Video Preview in order to have it undocked (otherwise clicking on the tab was doing nothing at all).

Now that I try to preview my project, using "Preview (Auto)" quality setting, all I get is frame drops (not sure but I mean black frames, or image freezing (like not even starting though sound if playing), freezing and potentially crash of the all application.

Even simply moving the preview window or moving the cursor on the tracks seem "difficult" for the software.

Seems like start to read from certain tracks play fine for a bit, but as soon as another track/video event overlaps it's black preview or freeze. A 4K source file seem to cause problems quicker than the others (multicam, with different cam so different file formats).

I know that some settings are reset when updating, even with builds, ... but it's possible that I forgot about some configuration details where do you think I should look ? (Project is also using Ignite Pro plug-ins v4 but they don't seem to have to do with this problem. Well they are in the project but at this step they are actually all disabled.))

Some system info: Windows 10 Enterprise, GeForce GTX 1080 Ti (driver 457.09, very recent), Threadripper 2950x, 32 GB RAM ...

Also, I accidentally double clicks on a .veg file and this opened Vegas Pro 17. Version 17 had no problem previewing this project. Now thinking that I was maybe using Vegas Pro 17 from the start. (I mean I have Vegas Pro 18 in my task bar, but .veg file are still associated to Vegas Pro 17. Anyway ... I'd like to use Vegas Pro 18 but it's not usable in this state.

Back to post

Comments

RogerS wrote on 10/26/2021, 7:11 PM

Turn off the NVIDIA decoder on preferences, file io and see if it's more stable? I never had much luck with it.

Former user wrote on 10/26/2021, 8:57 PM

@TTTT
Can you do anything with my results?
Feedback would be appreciated

Vegas introduced a GPU decoder that supported Intel in VP15, followed by support for Nvidia and AMD GPU's in VP16. It's never worked properly, and never gets fixed. If you look at GPU decoder box you can see it stops decoding, it is most likely then using whatever it has in it's buffers/caches. I hasten the death of the decoder by going backwards and forwards but it also fails as you've described, but less predictably.

I tried rewraping to mp4, doesn't help. so that means having to re-encode your files I guess which you shouldn't have to. I'd be interested to see if people using Intel IGPU decoder have same problem

Former user wrote on 10/26/2021, 9:06 PM

Turn off the NVIDIA decoder on preferences, file io and see if it's more stable? I never had much luck with it.

It does work without a decoder, for me, and probably for this user also with an 8core cpu (from memory) although he may not be able to playback the last stage of the project at a reasonable frame rate. Most disappointingly the GPU decoder still breaks for these files in VP19 @RogerS

The bigger problem is for those that don't have a CPU that can take up all the slack due to the decoder not working for a given project

RogerS wrote on 10/26/2021, 11:50 PM

I'm on an Intel decoder (HD 630).

The second project plays back pretty much fine even moving clips around during playback if I keep it on preview/auto. Best/full is too much for 50fps.

The first project is slower with the initial stack of videos, especially during the fade-in. It take a few playthroughs to stabilize at 50FPS.

No black flicker or issues with P1000243.

The THCO0629 clip does show black frames/flicker here when I jump around. (If I jump around in Media Player Classic it also shows some glitches but it looks different in Vegas.) That was true at best/full, preview full and preview/auto. Setting dynamic ram preview to 0MB didn't help.

With the final test, no issues with cam 3. Cam 2 with THCO0629 is black when the cursor is over that track but plays back. Some glitches. I did a 1080p 50fps NVENC render and while it's a little confusing what is what given they are all maps, I appear to have all layers, no glitches. I realized dynamic ram preview was still at 0MB so put it back to 10%, changed the THC clip with a big hue shift so it's more visible, and retested. I see some glitches in the render on the THC layer.

So with an Intel decoder the only problematic clip is the Canon one for some reason. No crashes or freezes here, though, even jumping around, deleting clips during playback, etc.