Prores Vegas 13 project has problems in 14

william-kersten wrote on 10/10/2016, 9:11 PM

I have a feature film in Vegas 13 edited from a Prores original HD file.  It is  23.976 fps progressive, 1920x1080x32, ProRes Audio: 48,000 Hz, Stereo, AAC.   It works normally in Sony Vegas 13 last build.    i opened it in Vegas 14 and each shot from the feature length scan of a film negative has one or two extra frames added at the beginning of each cut - which were not there in Vegas 13.  It completely screws up the cut and will go out of sync with the sound.  Vegas 14 is not keeping in sync with the original cut.  It is definitely introduced by Vegas 14 because I checked the original file in Sony Vegas 13 and it is normal with perfect cuts.  So this is some glitch or bug due to VEgas 14 using a Prores file.  I have no problem so far using XAVC files in 14 - only Prores.  This is on a Win 7 64 bit Pro with 32 GB ram and Nvidia quadro 4000 graphics.


NickHope wrote on 10/11/2016, 1:03 AM

In VP13 ProRes files were handled by the Quicktime copec qt7plug2.dll. In VP14 they are handled by Vegas' own codec mxhevcplug.dll.

You should submit a support request at , including as much detailed information about the problem as you can.

As a temporary workaround you can rename the folder C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\mxhevcplug to C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\mxhevcplugRENAMED This will prevent Vegas finding the codec and it will default to Quicktime, if you have it installed, so it should behave like it did in VP13 unless there is another factor at play. Please let us know if it works.

Note that this will also disable reading and rendering with HEVC. I have no idea why ProRes shares the same codec DLL with HEVC. It seems like a strange choice to me.

Edit: In VP15, a ProRes clip will fall back to getting decoded by the so4compoundplug codec rather than Quicktime. So you would also have to disable that by using this method. Discussion here.

william-kersten wrote on 10/11/2016, 11:16 AM

EDIT -  Thanks Nick that worked.  I really appreciate your help. 


Bill Kersten

jason-pegg wrote on 11/27/2016, 9:01 PM

Thanks, Nick.  That worked well.  I'm reading ProRes files created by a BlackMagic HyperDeck Shuttle 2 that creates 16 channels of audio.  Video was working fine but I was only getting one (blank) track of audio.  Your workaround took care of it.  I'll definitely leave a note for the MAGIX folks as suggested.

Thanks again!


NickHope wrote on 11/27/2016, 10:34 PM

Note that qt7plug2.dll will incorrectly decode your video with significantly more contrast than mxhevcplug.dll, as it did in earlier versions of Vegas Pro, which may result in clipping of shadows and highlights. You may wish to transcode your 16 channels of audio to PCM audio files within Vegas, then re-enable mxhevcplug.dll to decode the video stream.