MP4 file works on in Vegas 20 but looks strange in 21 (Clip in post)

djrikki2 wrote on 7/21/2024, 7:10 PM

As per title ...

MP4 file from karting recorded on 1 year old Drift 4K Ghost helmet cam.

 

https://drive.google.com/file/d/1qc3JyUqssOYc4gXNFO1UNNBc--1Wb6bX/view?usp=sharing

(Link to video clip here)


Loaded it into Vegas 21 and it looks like this ^

 

Pull it into Vegas 20 and it loads and displays fine.

Any ideas on this one folks?

 

Thanks!

 

Rikki

 

Comments

john_dennis wrote on 7/21/2024, 8:51 PM

The video works OK on the machine in my signature using Vegas Pro 21-315.

There's nothing remarkable about your camera file. Tell us about your:

Vegas Pro build

Video Card Type

Gid wrote on 7/21/2024, 9:03 PM

@djrikki2 Yep same here, plays at full fps no problem

Vegas Pro 18 - 22
Vegas Pro/Post 19
Boris Continuum & Sapphire, 
Silhouette Standalone + Plugin, 
Mocha Pro Standalone + Plugin, 
Boris Optics,
NewBlue TotalFX
Desktop PC Microsoft Windows 10 Pro - 64-Bit
ASUS PRO WS WRX80E-SAGE SE WIFI AMD Motherboard
AMD Ryzen Threadripper PRO 3975WX 3.5GHz 32 Core
Corsair iCUE H150i RGB PRO XT 360mm All-in-One Liquid CPU Cooler
RAM 256GB ( 8x Micron 32GB (1x 32GB) 2666MHz DDR4 RAM )
2x Western Digital Black SN850 2TB M.2-2280 SSD, 7000MB/s Read, 5100MB/s Write
(programs on one, project files on the other)
Graphics MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU
ASUS ROG Thor 1200W Semi-Modular 80+ Platinum PSU 
Fractal Design Define 7 XL Dark TG Case with 3 Fans
Dell SE3223Q 31.5 Inch 4K UHD (3840x2160) Monitor, 60Hz, & an Acer 24" monitor.

At the moment my filming is done with a Samsung Galaxy S23 Ultra 5G & a GoPro Hero11 Black

I've been a Joiner/Carpenter for 40yrs, apprentice trained time served, I don't have an apprentice of my own so to share my knowledge I put videos on YouTube.

YouTube videos - https://www.youtube.com/c/Gidjoiner

 

RogerS wrote on 7/21/2024, 11:11 PM

I've seen similar issues with build 315 and NVDEC decoding, especially with my NVIDIA GTX GPU. I see it occasionally on my RTX 2080 GPU but wasn't able to get it to glitch with this footage, even when splitting and moving it around.

Build 300/314 were worse than 315.

As John asked, what is your GPU?

RogerS wrote on 7/22/2024, 6:02 AM

Update: I wasn't able to replicate decoding issues on my GTX 1050 despite repeated playbacks, splitting the events, overlapping them, playing it backwards, etc.

djrikki2 wrote on 7/22/2024, 7:30 AM

Thank you folks!

It's build 300 - I saw the firestorm on the update after 300 and didnt upgrade because of it.

nVidia 2070 Super with latest drivers on Windows 10

I'll download the latest update to 21 and give it a bash! Thank you everyone :)

 

R

RogerS wrote on 7/22/2024, 7:58 AM

I think you misread the forum- it was 300 that had major problems.
314 addressed many of them (but there were issues left, esp. for AMD users if I recall). 315 is an improved version of 314. If none of these work for you try legacy AVC in preferences/ file io or go back to build 208.

As we both have similar GPUs my guess is 315 will work for you.

djrikki2 wrote on 7/22/2024, 10:55 AM

I think you misread the forum- it was 300 that had major problems.
314 addressed many of them (but there were issues left, esp. for AMD users if I recall). 315 is an improved version of 314. If none of these work for you try legacy AVC in preferences/ file io or go back to build 208.

As we both have similar GPUs my guess is 315 will work for you.

"

gabgilson wrote on 5/15/2024, 4:21 PM

Fail here. Worked fine with new projects, but wouldn't open a project from v21 300 - crashed on opening every time. Tried reinstalling (and DLM). Tried cache reset, and reinstalled GPU driver, but still the same. Have reverted to v21 300 and it's opening fine again. Sorry, didn't manage to copy the crash report info, but have sent it to Magix."

It was the posts at the beginning of this thread that made me hang off and keep 300 as it was solid for me :)

Thank you, I'll give it a bash with things.

- R

RogerS wrote on 7/22/2024, 11:18 AM

The perils of making decisions based on the experience of a single user with a single project : )

There were LOTS of threads when 300 came out with a long list of problems as you'll see in the 314/315 changelog.