VV 2g download upgrade/VF 2.0 upgrade

dsanders wrote on 9/3/2001, 9:24 AM
I have been using VV 2b for about two months without any problems. I then noticed that VV 2g was available so I downloaded it along with VF 2.0. I installed the VV 2g then VF 2.0. I then tried to run VV and had a couple of problems. First off, I tried to use the text generator and got an error stating that VV could not start the proper COM object (or something like that). I noticed that I now had two different text generators listed from within VV - I guess VV installed one, while VF installed the other. Also, when I then tried to drop a quicktime movie onto a time line, VV said it was an unsupported format. The quicktime movie is generated directly my Olympus 3040 Digital Camera and worked just fine under 2b.

So I uninstalled everything (except the new DirectX stuff that 2g had me install before) , and started all over. I installed VV 2b (from the CD in my retail box), registered it and everything was back to normal. I then installed VV 2g and no longer was able to use my quicktime movies. I then installed VF 2.0 and lost the ability to use the text generator. So the problems are pretty reproducable.

Again I uninstalled everything but just reinstalled VV 2b. So..., has anyone else had similar problems? VV has crashed on me a couple of times, so I thought it might be a good idea to install VV 2g. I was also told by a SonicFoundry Tech Rep to install VF 2.0 for some of the new plugins. Do I really need to install VV 2g to fix stability problems? How do I just install the VF 2.0 plugins? Any suggestions?

Comments

SonyEPM wrote on 9/4/2001, 9:22 AM
If you are seeing problems, I would advise uninstalling both Vegas and Video Factory, then reinstalling Vegas 2.0g only. We run both side-by-side all the time but perhaps you have exposed some conflict we have not run across.

It should work fine to have both, but as always, revert to last known good config if you have problems.
FadeToBlack wrote on 9/4/2001, 2:57 PM
dsanders wrote on 9/4/2001, 9:19 PM
I uninstalled everything (again), installed VF 2.0 then VV 2g. If I do an Insert Text Media, I get the generic text plugin. If I do a View | Plugins, I see two different Sonic Foundry Text plugins under the Video | Media Generator tree. The second one seems to be the generic text plugin, but the first has a whole bunch on new features. How do I go about making this the default "Text Media" plugin. In addition, if I try to drop a QuickTime movie onto a track, VV gives me the message "None of the files dropped on Vegas could be opened." What am I doing wrong. Before I uninstalled everything, I was running VV2b and the QuickTime stuff worked fine? Any suggestions?

Thanks
dsanders wrote on 9/6/2001, 9:00 AM
Ok, I uninstalled everything (except the new DirectX stuff for VV2g)- VV2g and VF2a. Then I installed VV2g only and I can't get it to recognize QuickTime Movies. If I try to drag and drop a .mov file onto a track, the cursor stays as a typical "drag and drop" style cursor and I get the message "None of the files dropped on Vegas could be opened." If I unistall VV2g and install VV2b then drag a .mov file onto a track, the cursor changes to show the outline of a Video and Audio track and the operation succeeds! So, for me VV2b works, VV2g doesn't! I also tried the whole thing over again after downloading QuickTime 5.0.2. but that did not seem to make a difference. I guess I'll wait for VV3.0 to come out - but somehow I don't think that it will be a free upgrade.

As a result of all of my playing around, I have had register VV about 15 times now. Is there a point at which the registration process will now longer work? I don't want to get into a situation where I have to call for an activation code.
SonyEPM wrote on 9/6/2001, 9:11 AM
Please email our tech support department and tell them your situation- they'll make sure you can continue to register.

As for Quicktime, that's pretty odd. Nobody else has reported this bug, but we'll keep our eyes on it.
dsanders wrote on 9/6/2001, 10:46 AM
I installed VV2g (demo) on the machine that I use at work and it seems to work just fine. I don't know what is happening! If I can trace it down, I'll let you guys know!