Doom9's Forum - View Single Post - Better decoders in Premiere Pro / Sony Vegas? ( Colorspace issues )

Warperus · 13th November 2012, 09:21

So, you have H264 High 4:2:2 (made using x264) as input for Sony Vegas? It uses internal codecs for some known types, QuickTime for mov and some mp4 files and VfW codecs for avi files. As far as I know, Vegas reads H264 with QuickTime (in mp4) or internal mainconcept codec, but 4:2:2 profile is not supported, and you can't use arbitrary decoder unless you hide the fact it's h264. So you need to use some sort of proxy/frameserver.

For example, you can set up ffdshow tryouts, set up .avs files support in vfw decoder configuration, make avisynth script and put avs file into Vegas. Or you can set up ffdshow support for High422 profile, use make avi tool in ffdshow and then open this proxy avi in vegas.

The other way around this problem is to reencode file into more vegas-friendly codec that supports 422 or 444 after you get files back from archive.

13th November 2012, 09:21	#2 \| Link
Warperus Registered User Join Date: Apr 2010 Location: Sain-Petersburg, Russia Posts: 139	So, you have H264 High 4:2:2 (made using x264) as input for Sony Vegas? It uses internal codecs for some known types, QuickTime for mov and some mp4 files and VfW codecs for avi files. As far as I know, Vegas reads H264 with QuickTime (in mp4) or internal mainconcept codec, but 4:2:2 profile is not supported, and you can't use arbitrary decoder unless you hide the fact it's h264. So you need to use some sort of proxy/frameserver. For example, you can set up ffdshow tryouts, set up .avs files support in vfw decoder configuration, make avisynth script and put avs file into Vegas. Or you can set up ffdshow support for High422 profile, use make avi tool in ffdshow and then open this proxy avi in vegas. The other way around this problem is to reencode file into more vegas-friendly codec that supports 422 or 444 after you get files back from archive.