Anyone know what this problem is in Vegas Pro 14?

Former user wrote on 7/3/2018, 8:31 PM

Every time I apply Media Fx in an event and change the resolution to 720x480 NTSC Widescreen the video bottom is left with a line where Media FX is never applied. In rendering this line also appears.

Has anyone here ever had this problem or know how to solve it? This problem only occurs when I apply FX media, when I apply FX event it gets normal.

Comments

Grazie wrote on 7/4/2018, 12:41 AM

I Have absolutely noooo idea. Not seen this before. As a superficial first level track-down I’d concentrate on all things GPU, drivers and so on. For some reason the Math is getting screwed. As I don’t recall this with other Users, I’d regard this as something local.

karma17 wrote on 7/4/2018, 6:07 AM

I was just curious. Does the line occur on the actual rendered video or just in preview?

Can the line be cropped out in Pan and Crop or is it always there no matter the crop?

If you go to the Media Fx and use the Color Corrector and desaturate to Black and White instead of using the Black and White filter, does the line still occur?

 

 

 

 

Musicvid wrote on 7/4/2018, 7:11 AM

Start over with a fresh project that matches your Media properties, otherwise effects will not be generated at the same aspect. The math is simple:

720*1.212/480 !~ 1920/1080

The shape of your effect is not the same shape as your video, which is not the same shape as your project. Make it so and all will be peachy.

Rendering at greater than source resolution is not recommended nor necessary. It will not look better than native resolution and hardware upscaling.

Former user wrote on 7/4/2018, 8:19 AM

@karma17 This problem occurs both in preview and in render. The problem occurs in every effect if it is used as FX media, no matter what effect it may be. If I use the crop pan the problem disappears but I lose some of the scene due to the zoom.

@MusicvidI started the project with the correct settings, but the problem remained. However I realized that if I do the project in 1920x1080 by applying the FX media and then nesting it all, the problem no longer occurs when I define the new settings.

@Grazie The strange thing is that this does not occur in Vegas Pro 13. I did this test with the GPU disabled. I then enabled for Intel Graphics HD and the problem disappeared. It must be my PC that is already old and outdated to the latest software standards. Thanks!

Musicvid wrote on 7/4/2018, 9:50 AM

I  started the project with the correct settings, but the problem remained. However I realized that if I do the project in 1920x1080 by applying the FX media and then nesting it all, the problem no longer occurs when I define the new settings.

Yes, may be seen to support my observation, but in a roundabout way.

It would be better if your project properties (before adding generated media) and render properties matched your Media properties door to door, because it will look better, especially on your big screen. I can't twist your arm, so good luck.

Former user wrote on 7/4/2018, 10:22 AM

@Musicvid You did not quite understand what I said. I said that I set the project properties at 720x480 before pulling the media to the timeline. Only then did I apply the FX media. But I believe this is a hardware problem. I will test later on a more current pc.

Thank you for your help. No need to twist my arm. Even because I would not allow it.

Musicvid wrote on 7/4/2018, 10:52 AM

Every time I apply Media Fx in an event and change the resolution to 720x480 NTSC Widescreen

The project, thus display aspect in your image says 1920x1080. The error you reported is perfectly logical and expected in that context, regardless of how you might change your project settings later.

Generated Media in a 1920x1080 project will not have the same aspect as in a 720x480 widescreen project. They disagree by a small amount, because ntsc widescreen display aspect is not 16:9.

I'm thinking now from your last post that you must have posted the wrong screenshot, which is not of an SD project as you indicated.

Glad you are getting it sorted, though, and I've exhausted my usefulness here.

Former user wrote on 7/4/2018, 1:25 PM

My only annoyance in this story is that this does not occur in Vegas Pro 13. In Vegas pro 13 I can change the project properties at any time and in any situation and this type of problem does not occur. And what can we do? We can not do anything. We just have to accept.

@Musicvid Thanks for your help. I can sort it out here by nesting the project.