Transfering Motion Data completely disrupts the project

steve_ua wrote on 5/31/2024, 8:33 AM

Hello colleagues!

I've been editing in Vegas for almost 10 years now, my last version was Vegas 17 that I used for 4 years. This month I decided to step out of my comfort zone and bought the latest 21st version (Build 315).

I spent the last couple of weeks exploring every new feature and also revisiting old ones. When I tried the new Mocha tracking tool and transferred the tracking data to another file it didn't work and the project preview screen turned black. I loaded my last save and tried it again - the result was the same.

After this annoying glitch I made a new project and decided to use other tracking options like vegas tracking regions (through bezier mask FX). The whole tracking process was pretty quick and easy, but, again, when I tried transfering the motion data (experimenting with both location and picture-in-picture FX transfer methods) the project becomes fully glitched. Changing preview options or disabling FXs does not help. It only gets fixed once you load up the last save that did not include transfer procedure.

Any tips on what I could do to fix this glitch?

Operating System - Windows 11
GPU - RTX 3080 (latest drivers)
CPU - Intel i9 12900
32GB RAM
K-Lite advanced codec pack installed
Continuum installed
All vegas files stored on SSD in dedicaded folders

Comments

mark-y wrote on 5/31/2024, 8:58 AM

K-Lite advanced codec pack installed

Not sure if that relates to your problem; however, doing so may have replaced Windows 11 System Codecs that Vegas needs with generic aftermarket versions, and if a deep scan with Revo won't work, you may need to reinstall Windows 11 OS from a cleanly formatted disc in order to get all that stuff out of your registry.

Personally, I consider K-Lite right up there with bedbugs.

 

steve_ua wrote on 5/31/2024, 9:01 AM

Update:
Made another project with 16:9 aspect ratio and motion transferred successfully, the project seems to run smoothly and there is no visual glitches present,but I haven't tried Mocha tracking yet.

Could it be that motion transfer doesn't like weird aspect ratios? Could someone check this for me please?

steve_ua wrote on 5/31/2024, 9:02 AM

K-Lite advanced codec pack installed

Not sure if that relates to your problem; however, doing so may have replaced Windows 11 System Codecs that Vegas needs with generic aftermarket versions, and if a deep scan with Revo won't work, you may need to reinstall Windows 11 OS from a cleanly formatted disc in order to get all that stuff out of your registry.

Personally, I consider K-Lite right up there with bedbugs.

 

I see what you mean, will investigate this further. Thank you

Dexcon wrote on 5/31/2024, 9:10 AM

Mocha is a different animal to what you've worked with before (unless you have Mocha Pro). I mainly use Mocha Pro in which you need to save a tracking project and import it into another Mocha Pro project in order to use the original tracking data. In Mocha Vegas after you've done the track, use File/Save Project to save the tracking project, then in your other video event on Vegas Pro's timeline, add Mocha Vegas as an FX then after opening Mocha, use File/Open Project to import the previously saved project and then run the Mocha Vegas track again. It should then create the new motion data for that specific video event.

K-Lite 😲eek!

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

steve_ua wrote on 5/31/2024, 9:47 AM

Mocha is a different animal to what you've worked with before (unless you have Mocha Pro). I mainly use Mocha Pro in which you need to save a tracking project and import it into another Mocha Pro project in order to use the original tracking data. In Mocha Vegas after you've done the track, use File/Save Project to save the tracking project, then in your other video event on Vegas Pro's timeline, add Mocha Vegas as an FX then after opening Mocha, use File/Open Project to import the previously saved project and then run the Mocha Vegas track again. It should then create the new motion data for that specific video event.

K-Lite 😲eek!

Just did that in a new project with two unedited files, and it works perfectly. I will do more projects with different file formats and effects to figure out what could be causing the glitches, but so far it's 50/50.

If it's K-Lite pack messing with it then I really need to get rid of it.

mark-y wrote on 5/31/2024, 9:52 AM

GPU - RTX 3080 (latest drivers)

Are you sure to have the Studio, and not Gaming drivers?

steve_ua wrote on 5/31/2024, 3:19 PM

K-Lite advanced codec pack installed

Not sure if that relates to your problem; however, doing so may have replaced Windows 11 System Codecs that Vegas needs with generic aftermarket versions, and if a deep scan with Revo won't work, you may need to reinstall Windows 11 OS from a cleanly formatted disc in order to get all that stuff out of your registry.

Personally, I consider K-Lite right up there with bedbugs.

 

Uninstalled K-Lite Codec Pack completely and now Vegas 21 freezes on start up, also mp4 video thumbnails disappeared..

On the other hand Vegas 17 still runs fine. Guess there is something wrong with the Vegas 21 installation.

jetdv wrote on 5/31/2024, 5:36 PM

Did you reinstall VEGAS Pro 21 after uninstalling K-Lite? I would definitely do that.