Andrew Blake
Forum Replies Created
-
It is certainly possible that ancient versions of Vegas were prone to breaking if they used third party codecs. But that is more the fault of Vegas than of those codecs. It is pretty easy for an application to override system codec merits to prefer (its own) specific codecs above others.
Codec Tweak Tool is a great utility for dealing with codecs. It can generate a detailed list of all installed codecs. It also allows to enable/disable codecs very easily, which makes it ideal for troubleshooting.
-
The K-Lite uninstaller works properly. It doesn’t leave anything behind.
You should never let third party uninstallers remove things unless you can manually verify and approve all of its actions. Otherwise you are pretty much guaranteed that they will eventually mess up your system.
-
[John Rofrano]“The K-Lite Codec Pack is a collection of DirectShow filters, VFW/ACM codecs, and tools.”
Only the largest version contains VFW/ACM codecs, and those are all harmless. Furthermore, that type of codec is only used for AVI files.[John Rofrano] “I’ve seen K-Lite mess up many installations of Vegas Pro and Movie Studio over the years and those that it has happened to will agree. It definitely has an effect.”
I only see topics like this one where it gets the blame without any factual evidence. I know its developers are eager to fix problems, or prove that a fault lies elsewhere. But that is impossible to do based on just anecdotes.[John Rofrano] “This is not globally true and changed with different versions of Vegas Pro over the years so while some newer versions may use their own private plug-ins, the majority of older versions did not. I’ve been using Vegas since Vegas Video 3.0 and I’ve seen it all. Not just video codecs but audio codecs get messed up too.”
I am assuming that the topic starter is using a somewhat recent version. You will have to agree that those use internal plugins for MP4.[John Rofrano] “So the video worked one minute, they install K-Lite and now it doesn’t work. How do you explain that?”
I think that this simply is a wrong observation from the user. Or at least the wrong conclusion. Other things might have been installed as well. It might be a different file. Or the cause might be totally unrelated. The same problem also occurred with a restore point from a time before K-Lite was even installed.I know for a fact that K-Lite does not change/remove/touch anything related to Vegas. You can easily verify with SystemExplorer, which allows you to create (and compare) snapshots of the Registry and filesystem. This will also show you that it properly uninstalls and makes no permanent system changes. We have also concluded already that recent Vegas does not use external components for importing MP4. So how can K-Lite break anything? You blame it because that is the easiest way to say that you don’t actually know what is wrong?
-
It is disturbing how little people here know about codecs and how Vegas works. This leads to a lot of bad advice.
Sony Vegas does NOT use DirectShow filters. This is the type of ‘codec’ that K-Lite and other codec packs use for playback. This means that K-Lite simply does not have any effect at all on Vegas. So it does NOT cause problems, but it also does not expand the import capabilities of Vegas.
Sony Vegas uses its own private plugins for importing MP4 files. These plugins are not registered globally (like normal codecs) and you do not need to worry about other programs replacing or removing them.
If you look at the file properties in Vegas, it should show which plugin it uses. This website describes how you can change which plugin it uses for MP4:
https://www.vegascreativesoftware.info/us/forum/faq-why-won-t-vegas-open-my-file-correctly-codecs-converters-etc–104572/Sony Vegas uses/needs QuickTime for importing file formats such as MOV and 3GP. It might also help for certain MP4 files. So make sure QuickTime is properly installed.
The only external codecs that Vegas uses are ACM/VFW codecs, and that is only for AVI files.