I had them installed at the same time and it still didn't work before.

I think that VV4 must be alone without VV3.

I've had it both ways; VV3 with VV4, then just VV4, and the customise box still won't come up in VV4.

you have to have DVD architect installed aswell for the custom boxes to come up
regards
Simon

Thanks

KB

[HKEY_LOCAL_MACHINE\SOFTWARE\Sonic Foundry\MC MPEG Plug-In\1.0\License]
"key1"="" <--------- !!!!!REMOVE THIS KEY!!!!!!!
"CurrentKey"="E8-5J9HDE-JXDF77-CX4N3E"
"InstFlags"=dword:00000010
"AppGrade"="0x0010"

Enjoy!

folks, it seems double posting to me.

can we have SoFo in this one, pleeeze ?

no hints here, just facts. it is a lot of work installing/uninstalling VV3 / V4 / VV3+V4 / with or without DVDA, just because "it seems that...".

I rather say: "it shouldn't". I never read here from SoFo origin that we would have to wave goodbye to VV3 to say hello to V4.

1st a big disclaimer - haven't and won't have vv4 till closer to the dealine so-to-speak. So this is just a guess sort of thing...

What kovax suggests makes sense if the mainconcept plugin for VV4 looks to see if it's gotten registered yet, and is confused or won't accept the entries under the mainconcept key for VV3. If it doesn't work...

I'd suggest uninstalling VV4 (yes again), rebooting, and trying a fresh install. Had a prob. with the beta where the install did not put in all the registry settings it should have the first time I removed it & then reinstalled [did this for another prob.]. I considered this just one of those things, but maybe it's happened here as well? Otherwise (if that doesn't work & the reg settings suggested earlier have no effect)...

With any of the direct x or active x controls, the files that make the codecs as well as the filters in Vegas, windows registry keeps track of which ones to use and where they are located.

There always has been a prob. with video related ax controls because you can have many versions from the same company, as well as different brands that do the same thing. To explain, you should have an mpeg2 splitter to demux the streams prior to playback etc. It's very possible to have one or more ligos brand files on your system, perhaps one from Cyberlink or winDVD or whatever, one from MS, and of coarse the stuff from Mainconcept, where again you can have different branded versions. With the latter, a concrete example is the mainconcept files that prem installs in the windows folder (in system32 in xp).

This sort of thing can cause the mainconcept plugins not to work in Vegas - there would be no custom settings in this case because Vegas wasn't using the files that came with it.

I've read too many posts here where folks have had both versions of Vegas installed to believe it's an either/or thing. Instead I'd suspect that VV4 is more sensitive so-to-speak, &/or might stick closer to the .NET design of keeping everything more self-contained not dealing as well with conflicts elsewhere.

At any rate, to follow through with this line of diagnosis I'd use DXMAN to look for mainconcept control files, making sure that they were all located in the SonicFoundry folders, & secondly I'd check for files of the same name in the windows install folder, removing any found there at least temporarily.

mike

> and of coarse the stuff from Mainconcept, where again you can have different branded versions. With the latter, a concrete example is the mainconcept files that prem installs in the windows folder (in system32 in xp).
>
> This sort of thing can cause the mainconcept plugins not to work in Vegas - there would be no custom settings in this case because Vegas wasn't using the files that came with it.

We were aware of the issue that Premiere installs the MainConcept DLLs in the Windows system folder. Vegas 4 will preload MC files from the MPEG folder so that it should not be using those from the Windows system folder. The MPEG plugin should give you a warning that it did not initialize properly when it is attempting to use the MC files that are not from its own folder. However, our older applications (Vegas 3.0, ACID 4.0, Sound Forge 6.0, etc.) do not preload the MC files so you may run into problems using MPEG with them.

We are aware of this only being an issue with XP SP1. If you are running into problems using MPEG then please contact SF Customer Support.

One more thing, that might help us track this down is to know the version of the file "mcplug.dll" that exists on the problem systems.
You can search for this file then please note all the occurences in your system right click on the properties of the file/s and list the vesion numbers in this forum.


Thanks

Ivan

Also, can you correctly save MPEG using the built in templates? or is it the custom button the only thing that does not work?

Ivan

We are now fully aware of this problem. Please contact us directly by phone or email for further assistance.

This worked for me.

On my system under registry item: [HKEY_LOCAL_MACHINE\SOFTWARE\Sonic Foundry\MC MPEG Plug-In\1.0\License]

was:
key1 REG_SZ E8-3LQD09-JTRTZP-3CQ5JV

I deleted this key1 item, rebooted and VV4 now has Main Concept Custom / Advanced features. Yay!

I needed Constant Bit Rate which works fine at 6K. Now if they make it not so damn slow, 14 minutes to MPEG2 encode a 50 second clip on a fast computer! VV4 is such a lovely product to use in an artistic manner.

-Big Al