Vegas Pro 20 (Build 411) - Issue With Track Motion

MH7 wrote on 4/11/2024, 8:14 AM

Hi guys,

So, as per the title, I’m having a problem with Vegas Pro 20 (Build 411 - I don’t believe my issue is related to the build number of VP). The situation is that I used to be able, with previous versions of Vegas Pro, use Track Motion to create the motion graphics for my YouTube channel and use shadows behind generated media to give a sort of depth, like the material design look that was introduced many years ago.

The problem is now, when I try to do what I used to do (in regard to the shadows), it creates this weird problem when I click the checkbox in Track Motion and enable shadows. It’s hard for me to clearly explain it here in words (as of writing I’m currently on an iPad right now so I cannot access my PC to visually show you this), but if someone has Vegas Pro 20, although it may do the same thing on Vegas Pro 21 (of which I don’t have), would you mind doing the following, please:

Open up a new project in Vegas Pro 20 (possibly even Vegas Pro 21).
Go to the ‘Generated Media’ tab and select a solid colour (any colour is fine) and place it on the timeline.
Add a second solid colour (needs to be a different colour from the colour you previously selected) from the ‘Generated Media’ tab and add it to the timeline underneath the previous ‘Generated Media’ colour.
Now go to left of the video track of your top colour, on the timeline, and select ‘Track Motion’.
Once opened, resize the colour down to less than half of it’s original size so that you can see the other colour that is below on the timeline.
Now, where you see the keyframe area, which looks like a timeline in and of itself (where you see the little diamond shaped dots), you’ll see two (2) extra options to the left of this area, underneath ‘Position’; these options will be ‘Shadow’ and ‘Glow’, select the checkbox for shadows.

Now, if I’ve explained this well enough, and you understand what I’m asking you to do, the result should be that of which is my current problem with Track Motion. Anyone who is kind enough to do this (thank you), would you mind taking a screen capture of your results and posting them in this thread of mine below, please. Once done, hopefully my problem can be shown.

Back to post

Comments

MH7 wrote on 4/12/2024, 11:28 PM

Okay @Reyfox, I coped your settings exactly, Although, I thought I'd try just turning off GPU acceleration in Preferences to see if that would fix the problem. Unfortunately, it did not. I then, after I had restarted Vegas Pro for turning off GPU acceleration, decided to change the File I/O settings that you did.

I then restarted Vegas Pro and checked to see if the problem was fixed. Well, at this point, even though I had disabled GPU acceleration and change the my File I/O settings to your settings, the problem still persisted.

I then thought I'd look to see if GPU acceleration was turned off and, to my surprise, it seems as though when you change that File I/O setting that it, at least in my case, turns GPU acceleration back on.

Therefore, seeing that, I turned GPU acceleration off again and...bam, problem fixed!

So, if anyone else is having similar problems to @Reyfox and myself, you need change the following settings in this exact order, otherwise it will not work:

From the 'Options' menu above select 'Preferences...'.
Go to the File I/O tab.
Change File I/O settings to @Reyfox's here:

Restart Vegas Pro.
Reopen 'Preferences...' and select the 'Video" tab.
Where it says 'GPU Acceleration of video processing:' select 'Off' from the dropdown menu.
Restart Vegas Pro (the problem should now be fixed).

A huge thanks to @Reyfox for sorting this problem out. Thanks mate!!!

By the way, this fix to the shadow issue I was having also fixed the issue I was having with the ‘Border’ Video FX.

Reason for 14 Edits: Fixing formatting, paragraphing my post and adding @Reyfox's screen shot to my post at the appropriate place of step number 3. Also, some other fixin' and trimmings I felt I needed to do, along with adding a link to another problem that I posted about and was having that has now been fixed with Reyfox's fix.

Update: Removed link to the other problem that I was having with ‘Border’ FX. I decided to delete that thread since it wasn’t needed anymore because that problem, also, has now been resolved, thanks to Reyfox.

MH7 wrote on 4/13/2024, 1:01 AM

The only downside with this fix, at least for me, is the disabling of GPU acceleration on the timeline because Vegas Pro 20 utilises my RX 7800 XT quite well with up to 65% utilisation. So, I may have to figure out another way around this problem. Perhaps a future AMD graphics driver update will fix this issue in Vegas Pro. We'll have to wait and see. Nevertheless, I am still quite appreciative of the fix. I'm not sure I would've figured it out.

Reyfox wrote on 4/13/2024, 6:45 AM

Glad that things are working for you, albeit, in a roundabout way. As to why this is an AMD issue and not a Nvidia issue is way above my pay grade. There are issues that Nvidia users suffered that AMD users didn't. I would think with the constant updating of video card drivers that things like this would happen.

It is hard for software developers to test for every contingency with new drivers. There is a new Pro Edition driver out that I haven't tried yet, but will and see if that changes anything.

Dexcon wrote on 4/13/2024, 6:51 AM

@MH7 ... it would be a good idea to change the 'Solution' credit to @Reyfox because, as you've noted, it was Reyfox's suggestion who sorted the problem out for you. It's usually considered etiquette on the forum to acknowledge the forum member who provided the solution.

Reyfox wrote on 4/13/2024, 7:23 AM

I tried the Pro Edition drivers and the results were the same if the GPU is enabled in the Video tab.

MH7 wrote on 4/13/2024, 8:17 AM

@MH7 ... it would be a good idea to change the 'Solution' credit to @Reyfox because, as you've noted, it was Reyfox's suggestion who sorted the problem out for you. It's usually considered etiquette on the forum to acknowledge the forum member who provided the solution.

No worries mate! Good point. It is considered etiquette to do such a thing. Therefore, I have changed the solution to @Reyfox’s post that hit the nail on the head (AKA solved the problem). My apologies @Reyfox.

Thanks @Dexcon! 🙂

Tagged solution post changed!

Dexcon wrote on 4/13/2024, 8:59 AM

@MH7 ... Thank you. Cheers.