Mercalli V4 Plug-ins for Vegas Pro

[Jonathan Deitch]

So, I gotta ask … has ANYONE been able to successfully install the Mercalli v4 vegas plugin?

ProDAD is telling me they can’t reproduce the issue, and I can’t get it to work on any PC I own, on any OS (win7 through 10).

No matter what, the Mercalli plugin just doesn’t appear in vegas.

[Mark Barton]

I just downloaded the demo version of the Mercalli 4 Suite and I see both plugins in SVP 13 under proDAD Mercalli v4 and proDAD CMOS fixr.

Running Windows 7 Pro

[Jonathan Deitch]

Ok, so what’s different then?

I do the same thing, I only see CMOS fixer in Vegas Pro … I’ve tried both 12 and 13.

Win7 pro, x64, with an AMD R9/270 video card. It’s fully up to date on all drivers and windows updates.

I tried the same thing on a windows 10 system … same exact result … and that’s an nvidia box.

Both systems are intel chipset motherboards.

Got any ideas?

[Mark Barton]

Check the Mercalli log file for clues. I found mine in the appdata roaming. See image for the path, replace my username with your login.

My log chose detecting Vegas Pro 12 and 13 and copying files to each version.

[Jonathan Deitch]

Nothing useful there …

Per that log, both plugins are installed and registered.

Yet, only the CMOS one appears in Vegas.

[Mark Barton]

Very strange. So did you confirm the file is where the log said it put it? The screenshot shows the location and file size of the ofx file within the bundle on my system. This is the demo version of the Mercalli v4 Sony Suite.

[Jonathan Deitch]

Yeah,

Same file, same location, same size. Matches exactly.

There’s no difference, btw, between the demo and the purchased product … you just enter your registration code and it changes from demo to normal.

[Mark Barton]

So, you mentioned it happens on every machine you own. Is there anything similar to each of those machines? Same antivirus software perhaps? I know that is a slime chance that it is detecting a false positive on only the stabilizer plugin and not the CMOS Fixr. How about the way you invoke the installer? Are you using an account that is normally an administrator or is it a restricted user and you put in the admin password when prompted? You could try running the installer with the right-click option to “Run As Administrator”. In my case my account was already administrator.

[Jonathan Deitch]

Yeah, I’m running as administrator. do have the same antivirus; but the antivirus logs don’t show any record of picking up the file … it’s ESET NOD32.

[Jonathan Deitch]

And tried disabling antivirus … no effect.

What’s bizarre is the same exact behavior on win7 and win10.

The two systems couldn’t be more different than each other … different video cards, motherboards, etc.