I have Vegas Pro 9, 10 and 11 on one PC. No problems at all.

Ditto. I have Pro Versions for 8, 9, 10 and 11 on the same PC. No problems. Believe it or not, they all come in handy.

Anyone else having (new) issues with VP10 after installing VP11?

I see some strange behaviour in VP10 after I had the VP11 installed, especially with some 3rd party plug-ins (Neat Video)... Hard to say if the problems were there before VP11, but I have doubts that probably not...

I also found out mpg2 (PAL DVD) rendered video (rendered from VP10-32bit) plays erroneously (lots of shaking) on a PS3, especially the clips that have been stabilized in VP10 using its own stabilizer... This is so frustrating - you have to be alert all the time and continuously check every single frame in final rendered video - time consuming and irritating - you just cannot trust your professional tool! How bad is that?

Christian

"Anyone else having (new) issues with VP10 after installing VP11?"

like i said, might have been coincidence- but really, how could it have been?

i installed 11...my system freaked out. i rolled it back using system restore and all has been well since.

we are talking about essentially a dedicated vegas system on a fresh install of windows 7.

i will be testing again next week when my new computer comes...too bad i cant say i will be excited to have a new computer that is trouble free in confidence.

This is interesting to me and was going to post a separate thread but it may be better here. I have always since VV3, installed the newer version as a separate program and used each as I progressed to the newer versions and then deleted the old. Only thing I usually have issues with is some of the common files but each is setup on the newer version. Now I am at VV9, I bought VV10 but never installed and have all the updates. Now I have VV11 setting here plus updates. So is there any reason or benefit to install VV10 before I do VV11 to get certain library or other functions that are expected by VV11? I would think not but wanted to ask.

Also, I was going to skip using my disks I got when I upgraded and use the latest updated versions. I used to install that way and assume I can still do that and use my serial number from my disks. Is that correct? thanks

Gary

Anyone else having (new) issues with VP10 after installing VP11?

I have two systems (home and work) with VP10 and 11 installed. The work system is fine but on the home system all OFX plugins eventually crash during adjustment (after 2-6 adjustments). This happens in both VP10 and VP11. Uninstalling both and reinstalling VP10 makes the problem go away, so the problem seems to be introduced by VP11.

But this doesn't seem to happen on the PC at work, so there's something different on the home system and I suspect that it's a registry entry, shared library, or hidden data or prefs file rather than hardware. Although hardware is still a possibility.

<edit> This is not to say that you will have a problem, just that VP11 can affect VP10. In my case it's only OFX filters so it wouldn't affect VP9 or earlier since they don't use OFX.

Rob

the sn will work even on the updates

Something happened when I installed to Raylight and Cineform AVis in Vegas 8 after I installed Vegas 10. When I render to either one from 8 its just messed up bunch of images.
(Vegas 10 on one computer won't even render to AVI)

I'm thinking that uninstalling Cineform and Raylight and re-installing them will fix it, just haven't gotten to it yet.

kairosmatt

i always have to reinstall raylight after installing other versions.

"<edit> This is not to say that you will have a problem, just that VP11 can affect VP10. In my case it's only OFX filters so it wouldn't affect VP9 or earlier since they don't use OFX.

Rob"

So from some of the comments above I am probably pretty safe installing the latest version of VV11, skipping VV10 and not affecting my VV9 much. I don't use any of the other add on programs. Just not looking forward to a lot of rework on installations and chasing problems if VV11 does not work well for me. thanks about the comment on the SN.

Gary

If you're worried about mixing and matching Vegas versions you could add one more variable to the mix and run each OS/Vegas version in a separate virtual machine under VMWare Workstation 8.

I'm going to pass, but it could happen.

I have run virtual machines for other reasons and I've done physical to virtual conversions for some of my old images. Who knows? Maybe, some day I'll want to run Sound Forge 4.5 on Windows '98 using the VMWare Player under Windows 7.

Thanks JHendrix,
Good to know about Raylight, it didn't happen to me going from 7 to 8.

kairosmatt

Raylight requires the "DVFilm.fio2007-config" file in the root folder of the Vegas installation. If you install a new version of Vegas simply copy this file from the older installation to the new one. No need to reinstall Raylight.

Willem.

Any penalty installing VP11 on a VP10 system?

A look into my Vegas 10.0e folders in Windows "Program Files" shows that not one single file there was changed during the installations of the later Vegas 11 version + updates.

If there is any influence from V11 on V10 it must take place outside the program folder, then.

All of our Vegas workstations multi-boot. I used to have XP, Vista 32 & Windows 7 64 multi-boot due to a need to ensure stability. My XP & 32 installs were rock-steady & useful before Win 7 SP1 was released.

However, I have not had to boot into XP or Vista for almost a year, so before work resumed in 2012 I used a backup image from a fresh Windows 7 64 install to make all (4) boot drives, boot to Windows 7.

I know have a VERY stable version of Vegas 8, 8.1 & 9e on one SSD. I have 8, 8.1, 9e & 10e on another, and 10e and 11 on a 3rd. The last boot drive is Vegas 11 only.

Right now the Vegas 8, 8.1 & 9e install and the Vegas 11-only install are the most stable. Wherever 10e exists, I have trouble...

I think after the next major 11 update I may start new projects in 11. For right now I am editing in 9e and rendering in 11 with no unexpected problems so far. The reason for staying in 9e is that I can always render-out in 9 or 10 if 11 fails. By keeping all of my work files at 9e, I have more options. When I render in another version, I just resave to a different file name noting that it requires 10e or 11, etc. and cannot be re-edited in 9e.

It sounds more confusing than it is... The majority of my work does not contain fancy effects, titles, etc. It is editing a multi-camera event to get the best camera angle. I have developed a fast & easy way to do this in 9e, so I do not need 10 or 11 to make what I do go any more smoothly. However, 10 was replacing footage or rendering to black which was BAD, BAD, BAD. Sometimes I wouldn't notice it until very near a deadline. VERY frustrating that 10 has been!

@ritsmer
Just a theory that I posted in another thread about changes in older versions: There are a lot of new keys written to the registry in WOW64 that handle calls to 32 bit code inside a 64 bit environment. Some categories of keys redirect globally to newest dlls. SInce I have both 32 and 64 bit versions of 9 and 10 installed, that may be where some of my issues lie. From what I can see, users that have only 64 bit versions installed aren't having the range of problems with previous versions.
And as I posted in the other thread, given my limited understanding of Win7 internal operations, I could be dead wrong.