[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

[George Dean]

Will, have you performed a full reset? While holding down both the ‘Shft+Ctrl’ double left click on the Vegas Pro desktop icon. Before clicking on ‘Yes’, check the box ‘Delete all cached application data’. This will reset your Vegs Pro 14 to the original installed setting and delete the cached data which will sometimes confuse Vegas and and it does some strange things.

I don’t have ver 14, I have Sony Vegas Pro 13 and Magix Vegas Pro 15. These both work the same and advance using the numpad arrow right/left keys frame at a time when ‘Time at Cursor’ is selected and ‘Time Format’ is set to match the media or ‘Absolute Frames’. If I lock the numpad, then the right/left moves the event 1 frame to the left/right. Drilling down into the timeline does not change this, just allows detail of the time line down to the frame level.

Other than possibly the reset solving your issue, not sure what the rest of it will do for you other than, it is working for me!

Best Regards……George

[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

[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

[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

[George Dean]

Hi Pete,

I agree, nothing jumps out of the Mediainfo to imply there is something unusual about the source. And, the fact that it is fine in Resolve, I would tend to think it is Vegas having a problem.

Have you tried to start a fresh project in Vegas and add only this clip to see how it reacts? There may also be something in the cached application data that is confusing Vegas. Maybe a Full Reset would help. Keeping in mind a reset and deleting the cached application data will return Vegas to it’s original installation configuration.

It’s seem pretty weird, wish there was something I could put my finger on.

Best Regards……George

[George Dean]

Pete, is there anything weird in the source media specs? Does Mediainfo (text mode) reveal anything out of the ordinary? What kind of camera codec was used to record the ProRes?

Best Regards……George

[George Dean]

Pete, you have probably checked this, but are your project properties set to match your source media?

Best Regards……George

[George Dean]

Hi Patrog,

Could you post screenshots of your ‘Project’ settings, and the render ‘Template’ you are using? Also, have you applied any ‘Pan & Crop’ or ‘Track Motion’ effects?

Best Regards……George

[George Dean]

Kasia,

I just tried deleting everything from the ‘Temporary files’ folder and restarted Vegas Pro 15. It appears all my settings remained, such as my toolbar scripting shortcuts. Of course I don’t know that will fix any problems, because I do not have any problems currently.

I hope you will post back what id any of these options you have tried and if they solved anything.

Best Regards……George