Vegas Pro 15 frame rate anomaly

[Pete Tombs]

Thanks, George. One for Magix, I guess. Rather annoying though when a free software (Resolve) has no problems and one you paid for (Vegas) does!

P

[Steve Rhoden]

Just seems that’s how Vegas 15 handles Pro Res 422HQ files, which may be the indication of a slight bug
in its Pro Res architecture.

Steve Rhoden (Cow Leader)
Film Maker & VFX Artist.
Owner of Filmex Creative Media.
Samples of my Work and Company can be seen here:
https://www.facebook.com/FilmexCreativeMedia

[Pete Tombs]

Probably. More than a slight bug, though! It makes it unusable. Pro res is pretty much a standard delivery format these days

[George Dean]

I’m on the latest Vegas Pro 15 build 384. Here are the specs to a ProRes 422 HQ 1080-24p clip shot with a Panasonic GH4 and recorded on an Atomos Ninja Flame. This ProRes source media works fine in Vegas.

Best Regards……George

[Pete Tombs]

Thanks. I’ll check what build I’ve got. I think it is the latest.

[George Dean]

I doubt it is the build. I purchased ver 15 when it was first introduced and updated the builds as they were released, although I may have missed one. However I have never had any problems with ProRes or DNxHD in Vegas.

I have also never had a problem with Vegas getting confused and having problems that were solved by doing a full reset, but I have read many others that have.

I have also read of many that have had problems from Windows 10 update, but this just doesn’t seem like a problem that could be caused by that.

I have also read of those who have had problems in Vegas with a specific clip that run fine in other viewers, but never when a clip would run fine in Resolve and not Vegas. That is the part that is confusing and puzzling me.

Best Regards……George

[Pete Tombs]

Hi George

I seem to have fixed it by disabling the mxhevcplug.dll plug in. Renamed the folder and that forced it to use the quick time plug in that was already there.

Not exactly ideal, but it appears to have solved this particular issue for now. Hopefully the next version of Vegas will have a proper native solution to this problem as I can’t believe I am the only person experiencing this.

Thanks for your help.

Pete

[George Dean]

I think there may be something else to this other than just the mxhevcplug.dll plug in. At least there appears to something else that is different between your system and mine.

Here is what I did…..

With both Quicktime and mxhevcplug.dll enabled, my Vegas works fine frame by frame using the frame advance icon on the viewer and clicking with the mouse. When I use the ‘Alt’ key + the numpad arrow keys, it also advances one frame at a time. If I use only the numpad arrow key, it will advance 2 frames with each press. I cannot get it to advance a frame (or two) when the actual frame stays the same, it always advances the actual frame with the frame counter.

If I disable the mxhevcplug.dll, as you have by renaming the folder, Vegas reverts to using Quicktime and functions the same way as above. This of course disables the Magix Intermediate render format and templates such as the 422 (HQ).

If I then also disable Quicktime, Vegas of course will not load the ProRes clip.

If I then enable the mxhevcplug.dll plug in (leaving Quicktime disabled), Vegas again functions as above!!

So, again, why does mine work and yours does not. One difference for sure is, although we are both using ProRes 422 HQ source media, they most likely came from different camera codec’s. There doesn’t seem to me to be any suspicious differences according to the Mediainfo, but they are most likely a bit different, although I don’t think this has anything to do with it.

At least you now have a work around so you can proceed with your project.

Best Regards……George

[Pete Tombs]

There are other issues as well that are caused by dsiabling the plug in. The blacks in the test footage I rendered were very badly crushed (most detail lost) and as this is black and white film – not a good thing!

I think the only solution here is to convert all the footage to another codec that Vegas15 can handle.

The company really should fix this as a matter of urgency.

P

[George Dean]

Pete is this clip the only one you have? If you had another than was a few hundred meg that you could upload, I would then download and try on my system. Other than that, which still would not fix your problem, I think you have the solution to run it through Resolve and render to an intermediate for Vegas.

Best Regards……George