-
Norman Black
April 18, 2013 at 5:11 pmSystem codecs for general use.
In Windows there are three codec systems where you can install something for “general use”
Video for Windows
Direct Show
Media FoundationVegas only uses Video for Windows
Video for Windows was depreciated in 1997 when DirectShow was created. Interesting Vegas used something depreciated before its first release by I digress. Media Foundation depreciated DirectShow as of Windows 7.
Video for Windows only allows one codec per FourCC id installed. So a new install of something is destructive to an existing install.
DirectShow allows multiple implementations per specific codec class. They are chosen on a merit system, you can have control over this, but you would need to get a utility or edit the registry. Of course this means nothing since Vegas does not use DirectShow.
K-Lite Basic, Standard and Full versions only install DirectShow codecs. K-lite Mega does install some Video for Windows codecs.
K-lite comes with 32-bit and 64-bit versions of the codecs. If you run Vegas 64-bit then any 32-bit codec pack, even Video for Windows cannot effect you.
Vegas uses its own codecs directly. They are in the folder named Fileio or something like as I remember.
When I get home I will look at the Video for Windows registry, DirectShow also for giggles, and see if Vegas installs anything into those systems. I have my doubts except maybe the SonyYUV codec which exists in the Vfw chain.
-
David Alfredo
April 18, 2013 at 8:47 pmexcellent post Norman, and yes, Vegas Pro 12 invokes its own codecs as I was able to identify running a process monitor showing files opened by software, I encoded some mp4 on Adobe Media encoder while rendering a mainconcept template on Vegas (thanks 3770K multithreading) and different x264 codecs in different folders were being using by each, so pretty much as long as you install Vegas after you installed your codec pack you’re mostly fine.
-
John Rofrano
April 18, 2013 at 10:52 pmThat’s good to know. I still wouldn’t install a codec-pak on my video editing workstation but I’m glad that Vegas isn’t as susseptable as it once was.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Norman Black
April 18, 2013 at 11:16 pmI looked at my system. I looked at Video for Windows and DirectShow and DirectX installs. I have installed things like Photoshop, K-lite “standard” 32-bit, Sony Movie Studio and Vegas pro.
I have K-lite installed only for movie playback of any file type out there using Media Player Classic Home Cinema which is included with K-lite.
My Sony stuff is only installed 64-bit.
Sony installs nothing into Video for Windows.
Sony installs nothing into DirectShow.
Sony installs various audio plugins into DirectX.To look for installs I first used tools that show you and let you poke around Vfw and DiectShow. I also searched the registry in the appropriate locations and generically for anything pointing to the Sony installation. Also, items copied to Windows folders (SYSTEM32, drivers, etc) were known Windows items and one VMware item.
One note. Even if an application uses VfW or DreictShow there is nothing forcing them to use some other installed codec. If the app wants to use its own is certain can ignore the system codec search. It appears Sony is doing just this for the Sony YUV type codecs listed in the Video for Windows render as dialog. They are not installed generically and other apps do not see them.
David Alfredo did some good work looking up the Sony codec DLL file loads. Thanks! Saved me the effort of starting up Vegas in my debugger.
Sony codecs are all in File IO plug-ins folder and they all appear to be using proprietary API interfaces (aka, no Vfw or DirectShow) and this jibes with the rest of what I see.
It would be nice if Sony supported DirectShow for input on unknown file types, or codecs. Then you could put an MKV on your timeline for example. As it is, unless it is AVI (VfW) or Quicktime (MOV) if Sony does not support it, it wont work…period.
Why the heck can’t VfW just die and go away. It was replaced 15 years ago with better systems.
-
Graham Bernard
April 19, 2013 at 7:00 amNorman, that’s a great bit of detective work! Puts my mind at rest.
Thank you.
Grazie
Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge -
Thayalan Paramasawam
April 20, 2013 at 9:24 amHi Sir
Me to will not install a codeck-pack in my working station
-
David Alfredo
April 20, 2013 at 9:30 amconsidering Vegas Pro 12 is able to work with these out-of-the-box…
AA3, AAF, AIF, ASF, AU, AVC, AVCHD, AVI, BMP, BWF, CDA, DIG, DLX, DPX, DV, EXR, FLAC, GIF, H.264, HDP, IVC, JPEG, M2T, M2TS, MVC, MOV, Sony MXF (XDCAM – HDCAM SR), MP3, MP4, M4A, video MPEG-1 / MPEG-2, MPO, OGG, OMA, Panasonic MXF (DVCPRO, AVC-Intra) PCA, PNG, PSD, QT, R3D, SFA, SND, TIFF, TGA, VOX, W64, WAV, WDP, WMA and WMV
there’s no point in installing a codec pack just to support some obscure format/codec not listed there, so yeah, my multimedia PC at home is suited for a codec pack, but the IT guy at my workplace makes sure there’s no workstation “infected” with them.
-
John Rofrano
April 20, 2013 at 12:10 pm[David Alfredo] “there’s no point in installing a codec pack just to support some obscure format/codec not listed there”
I understand and agree with your point but Vegas is used by a lot of gamers to record their game play and post YouTube videos so none of those “professional” formats matter to them. They only use obscure formats like H.264 in an AVI container or MKV which wreaks havoc in Vegas. They want to edit video just like they edit words in a word processor and can’t understand why they can’t. In fact, that’s a pretty good analogy. Installing a codec pak is like installing every language and font in the world on your PC just because you need Russian. It is much better to just install the Russian font (i.e., a single codec that you need) instead of all of the ones that you don’t making your PC run slower because it has to deal with all those other languages and fonts that you will never use.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
David Alfredo
April 22, 2013 at 8:43 amexactly John, codec packs are very useful if you intend to use your computer as a media center, I’d suggest a dual-boot build if you really need to have a codec pack installed, keeping a “clean” Windows for Vegas operation, it doesn’t take long and you will probably avoid a plethora of potential issues. Not everybody can afford two different computers, but a dual-boot is easy to set up, will provide more details if needed.
Reply to this Discussion! Login or Sign Up