Never install codec packs, especially K-Lite. Mercalli should know better. The K-Lite codec pack replaces many of the excellent codecs installed by Vegas with inferior ones. If Mercalli wants a specific codec installed, then just install that one codec. Tell mercalli that you want a specific target, not a shotgun blast that may take out other programs.

Okay, I installed Mercalli 2.1 and the 2.0.95 Sony Vegas Plugin (x64). Here's my observations.

1) I Installed Mercalli 2.1 and ignored the K-Lite install, although I did install their recommendation of updating the "Intel Media SDK"
2) I had Matroska (Haali) Splitter & ffdshow previously installed.
3) Mercalli 2.1 seemed work better than 2.0 as previously I had problems with the video "export" e.g. exports in 2.0 would freeze during renders and sometimes would take many minutes to resume - this seems to be fixed. Some exports would display hiccups & glitches - this also seems to be fixed.
4) There were some problems however.
...a) Since K-lite was not installed, the initial splash screen/bitch message is presented whenever Mercalli v2.1 SAL is launched. Clicking the "ignore" button allows the user to continue. Very annoying.
...b) For some unknown reason, if I export to one format (say h264), then export to another format (say wmv), Mercalli sets the first export to 0 bytes. One-at-a-time exports seem to work fine.
5) The important thing (to me, anyway) is that the 2.0.95 Vegas Plugin continues to work fine - no nasty messages and excellent stabilization.

If I see anything more, I'll post back here.

...Jerry

One more thing...

I'd like to send ProDAD an email about their splash screen and K-Lite. I've done a search of SCS Support Documents, this forum and Google. All I can find is anecdotal reports of K-lite causing problems.

Can anyone point out a link where Sony has actually recommended not installing K-lite?

...Jerry

btw: I'm not going to install K-Lite & test, 'cuz one of those anecdotal posts indicated that K-Lite could not be uninstalled.

Thank You for all answers...

I'm going to postpone problem, will try to resolve this with first attempt to use SAL version. Now all I need works under Vegas.

Generaly speaking : I believe there is something dangerous in codecs packs.

I still have mess in vReveal (which is very fast and allow real time playback even with 100 fps avi movies (HD), which are a result from Bluff Titler models animation - so I like to use it). vReveal uses installed codecs on system level - but it's not absolutely true : I have old camera Panasonic VDR D160 which saves MPG movies. Under Vegas all works fine, under WMP also... but vReveal can't play audio. Have spent a lot of time in order to repairt it, but can't find source of problem.

I have installed in the past k-lite and I can imagin that this pack writes a lot to the registry of Windows and then can't clean all writings during performing of uninstall. This may lead to situation, that external programs (like vReveal) which would like to use 'virgin' codecs section in registry, may be unable to find proper codecs. Suppose, that it also may be dangerous for Vegas (even never have experienced any problems).

It would be very good idea, that SCS would send to the users info about using K-lite codecs pack.

Best regards,

I cancelled the K-Lite codec-pak install and Mercalli seems to still work fine.

I agree that proDAD should know better than asking video editors to install something as potentially harmful as that. We have documented cases here on the Sony Forum and the Creative COW of K-Lite causing Vegas to stop working properly. No editor should ever install a codec-pak on their Vegas workstation. It's like taking all of the pills, in your medicine cabinet just to see if one might cure you. Bad idea!

~jr

@johnnyRoy

Are you continuing to see the splash screen requesting the K-Lite install every time you launch Mercalli v2.1 SAL? Or have you figured out a way to disable it?

...Jerry

WHAT?!? ProDAD are inviting us to install K-lite?!?

Now I've heard everything.

CODEC WARS ALERT!!!!!

G......

> "Are you continuing to see the splash screen requesting the K-Lite install every time you launch Mercalli v2.1 SAL? Or have you figured out a way to disable it?"

Oh it still pops up and I just press Ignore. There is no way I'm installing K-Lite.

~jr

Maybe some of you should report this to ProDAD?

Jøran

Okay, I sent an email to a contact in proDAD. If, and when, I hear some resolution, I'll post back to this forum.

...Jerry

As I said earlier - ask them which specific codec they are expecting. You don't need a shotgun when one BB will do the job. I like the "all the pills in the medicine cabinet" analogy.

K-Lite is harder to get rid of than a case of bedbugs.

So... does anyone see the bright side here? With all the recent threads where forum participants are getting downright nasty to each other, we've finally found something we can all agree upon! [chuckle]

...Jerry

Nothing like a common enemy to unite people!

"Nothing like a common enemy to unite people!"

Of course, there's always a Tub of Ben and Jerry's? Or maybe a picnic in the Sunshine, or an appreciation of a good film or a walk with chums through a Gallery of modern art. Come the 4th Feb (?) in London I'm watching the Super Bowl with chums, eating my World Famous Chili Con Carne and supping chilled lager.

See where I'm going with this? No?

On this one I don't see enemies - I read a need for a reality check, and wanting/needing better.

Cheers

G

Jerry,
Did you get anywhere with proDad support on this issue??

I have just gone through an exchange of notes after I reminded them that I had not received a reply after a month to my support ticket.

Needless to say, I got nowhere asking how to disable that initial nag screen.

Here's their reply, totally missing the point:
"Mercalli SAL is checking your clip during the import. Mercalli SAL needs the CodecPack, when this message occured. You can´t disable this note of Mercalli SAL."

I have found that 2.1 work for the most part except that exporting to some formats, the exported clip is twice as long as the original. Go figure.

I am less than impressed.

Tom

Tom,

The short answer is "no".

Here's what I did. ProDAD has a Facebook page, so I sent an email to the the guy who hosted that page. Here's what I wrote:

"the recent releases [of Mercalli V2 SAL] that attempt to force users to install the K-Lite codec pack are causing somewhat of a kerfuffle over in the Sony Vegas Pro User Forum:

I received a response rather quickly...

"I will pass onto the development team... Thanks for bringing the matter to my attention, and feel free to reach out any time."

Haven't heard a word since. I've had some other issues with Mercalli recently and think I will make another contact with him.

...Jerry

btw Tom, can I get you to do a test? In Mercalli V2.1 SAL, import a 1920x1080 60i clip, stabilize it, then export it to a Windows AVI format (Cineform, Lagarith or whatever). Tell me what you see.

This is the response from manager of proDAD support when I asked about the problems with K-lite CodecPack and Vegas Pro back in January.:

I have checked the Mercalli SAL V2.1 installation with the k-lite CodecPack in a Vegas system without problems.

Maybe if all of you send them a note they take some action.

Ed

Did that ...

First thing I see is that video is twice as long - IOW it plays in slo-mo.

Used Lagarith loss-less 1.3.26.
Took defaults for both steadying and export...

Should I be seeing anything else, Jerry? :-)

Tom

"Should I be seeing anything else, Jerry? :-)Ha!! I ignored one of the first rules of computing... "If you see an error message, ignore it an plow on." [grin]

Here's what I saw:



As we all know, Lagarith does indeed support "Interlace" - WTF? Well, after I saw your post, I clicked "save video" and it worked fine.

Another annoyance, but not a deal-breaker, and probably not worth reporting back to ProDAD. Thanks for testing.

...Jerry

Interesting - I did not see that message.

I did report the length of the exported clip to proDad.

Tom

Just curious I have Mercalli V2.0. What's been added to 2.1 that required the upgrade.

I was just on their site and couldn't find list of 2.1 features.

Thanks,
-bK