Glitches from other places appearing in render

Kalvos wrote on 7/26/2021, 11:43 PM

Hello all,

Have been using Vegas Pro 16, and products all the way back to the 1990s from the same family (Sonic Foundry). A few small problems, but now I have a bad one -- and a deadline.

Info:
Vegas Pro 16 build 424
Windows 10 Pro 20H2 build 19042.1110
AMD Radeon R9 200 series
Approximately 300 still photos in JPG format (multiple cameras and scans, no video)
Stereo audio
Video time 11:30
Intended for a video for my mother-in-law's memorial service on Friday morning, July 30
Playback via any one of the media players available on Windows.

Image attached. Frames from elsewhere in the tracks are glitching into the rendered video (about 50 times in 11:30). In this screen capture, the intended image is the one of folks in front of the Leaning Tower of Pisa. The image with the hanging jugs is the next one on that track. The letter "e" and the oval streaks are a photo of the Arc de Triomphe from several images earlier on the track. And the fountains are from an image of the Eiffel Tower earlier than that. In other words, a frame with four different images.

The file has just five tracks: 1 text, 1 photo sequence video, 1 of solid backgrounds for images that don't fit the output aspect, and 2 audio.

It plays fine in Vegas itself. It's only the renders that are a problem, and you can see some of them happen in the preview screen as it's happening.

I'm at a loss. I've restarted Vegas and rebooted the computer. I've tried using a variety of codecs (usually I use AMD VCE HD 1080p, which worked flawlessly for all my renders; I used it for a four-camera, 80-minute ballet video, for example). I used all the Magix codecs, the MainConcept MPEG-2 (which really isn't good enough anyway), and the Video for Windows. I've turned the audio off because sometimes playing the audio will also pull bits from other places in the audio track. I've used draft lo-res mode for monitoring during render. Each codec causes glitches. Even though I haven't yet tried them all (still trying!), I need to get ahead of this before the memorial service.

From this info, can someone give me some ideas? Very, very grateful for anyone who has a solution.

Comments

RogerS wrote on 7/27/2021, 12:41 AM

I haven't used VCE but with NVIDIA cards solved this in VP 16 by setting dynamic ram preview to 0MB and disabling GPU acceleration in preferences. Worth a try. I'd try MagixAVC in VCE and Mainconcept and see if either work for you.

You can re-enable both after completing the render.

Still not working? You could pass frames to Voukoder and have it render using x.264. voukoder.org/

Reyfox wrote on 7/27/2021, 5:37 AM

I use AMD VCE a lot and never had that issue with using photos and videos in the same movies. Computer specs in signature.

A screen shot of your timeline, especially that part?

Kalvos wrote on 7/27/2021, 8:21 AM

I use AMD VCE a lot and never had that issue with using photos and videos in the same movies. Computer specs in signature.

A screen shot of your timeline, especially that part?

As I mentioned, this has never happened before. The only difference is the number of elements (nearly 500) and being made up entirely of stills. Screen shot of the section mentioned above. The first, second, and fifth images are mixed with the fourth one in the render -- but the glitch doesn't appear in the preview window.

Reyfox wrote on 7/27/2021, 8:28 AM

...and this is the only part of the video with this problem? Curiosity... what if you just rendered out that portion of the video and see if it renders correctly.

Kalvos wrote on 7/27/2021, 8:31 AM

...and this is the only part of the video with this problem?

The entire video shows the problem -- as noted in my OP, there are 50 glitches. The glitches are in different places depending on the codec used. This morning I finally found one that doesn't glitch (so far!) -- Sony AVC/MVC AVCHD 1920x1080-50i.

And I did render short sections just to test -- 30 renders, in fact. Codec A always glitches the same way but codec B has them in different places from codec C, etc..

Reyfox wrote on 7/27/2021, 8:40 AM

wow..... I have no solution or idea on how to solve this.....

RogerS wrote on 7/27/2021, 8:46 AM

Did you try the fixes I suggested above? I had similar issues with a slideshow and graphics overlaying a video glitching frequently along the timeline.

If that didn't work you can try Magix Intermediate (Apple ProRes) and use another program to turn it into h.264.

Or try Voukoder as I mentioned above.

Kalvos wrote on 7/27/2021, 8:51 AM

I haven't used VCE but with NVIDIA cards solved this in VP 16 by setting dynamic ram preview to 0MB and disabling GPU acceleration in preferences. Worth a try. I'd try MagixAVC in VCE and Mainconcept and see if either work for you.

You can re-enable both after completing the render.

Still not working? You could pass frames to Voukoder and have it render using x.264. voukoder.org/

RogerS, changing dynamic RAM preview to 0MB and disabling GPU acceleration seems to have worked for the Magix AVC AMD VCE HD 1080p that I normally use -- at least in test clips. I haven't done a full render yet, but this is promising.

Now that it's temporarily solved, do you have any idea why this would have happened? What would cause the render to grab chunks of images from elsewhere on the track? I always want to understand why something has happened!

Thanks so much!

RogerS wrote on 7/27/2021, 9:19 AM

Hi Kalvos, Vegas works in mysterious ways. Honestly, this is the same advice I got from tech support myself when I was doing a work project in VP 16 and so frustrated with these glitches appearing. It was in a 90 min. video, so tracking down the errors in each render was so painful.

Here's what I think is happening- I think something with the dynamic ram preview buffer is improperly interacting with GPU encoding. The GPU preview acceleration is also related as it is also processing those frames before it goes to the GPU. Why this is happening and exactly what is happening I don't know but the symptoms you describe and I experienced have been going on for a few years. Something's wrong with the preview buffer pipeline as it relates to GPU processing.

I don't see these errors much in VP 17/18 though, just occasional GPU out of memory errors if dynamic ram preview is > 0 with GPU encoding.

Here's hoping VP 19 solves the dynamic ram preview gremlins once and for all!

Reyfox wrote on 7/27/2021, 9:22 AM

What I find "curious" is that the timeline below was from VP16 and a video I did when I got back from Uganda. Tons of video and images with pan and crop, and upon rendering using Magix AVC/ACC MP4 AMD VCE 1080 50P, no issues at all.

Project properties, nothing special. 8bit, Best, blend fields, Disable resample.