I have an older Vegas 11 installed on my C drive, but have installed Vegas 23 on a different drive. It does load, but won't update, because there is an error, "There were no compatible products found on this computer". How do I get it to see my Vegas 11 on the C drive? I feel that is the problem.
Vegas 23 will not update Vegas 11 if that is what you are trying to do. Each version of Vegas is a unique installation. You can have multiple versions on the same computer. The problem is probably because you did not install in on the C drive, but I am not sure about that. Why do you not want in on the C drive?
That error message would indicate that you are trying to install the deep learning models. You need to install Vegas Pro 23 first.
DMT3, Thank you for your response. I am trying to update 23, not 11. I left 11 on my computer for now, since I bought an upgrade from Vegas online and I wanted it to be able to find a previous version of software so it would know I was eligible. My C drive has about 40% open space, but i don't like installing software on it. I mainly just keep just the operating system on there in case the drive fails, then I only have to replace it and not all of the software.
VegasDerek -Thank you for your response. You are correct, I did notice that it said it was a deep learning model that would not update, but I have already installed Vegas and the program does work, just not the update. Any ideas or questions to help find a solution?
It's unclear what's happening as it's possible your expectations about the installation of a new version of Vegas Pro may be different to the real-world process.
Installing a purchased upgrade of Vegas Pro (i.e. a newer version such as Vegas Pro 23 when you already have an earlier version such as VP11 in your case) creates an unique installation of the upgrade (as pointed out earlier by DMT3). This means that you will have both VP11 and VP23 installed and individually useable. The installation of a purchased new version of Vegas Pro does not install 'over' and replace the older version. However, an update to a version (e.g. VP23 build 302) does install over and replace the earlier build of the same VP version (e.g. VP23 build 278). Note: the process is different for Vegas Pro versions obtained under the subscription arrangement.
Your eligibility to upgrade pricing is based on the purchase record on your MAGIX My Account; the installation of a new version of Vegas Pro does not need to seek out the installation of an earlier Vegas Pro version on your computer.
... but I have already installed Vegas and the program does work, just not the update
This is rather confusing. Do you mean that you have installed Vegas Pro 23 and Vegas Pro 23 does work? If yes, what 'update' doesn't work?
BTW, the Deep Learning Models installation does not provide another program over and above Vegas Pro 23 - the DLMs provide additional AI FX available from within the FX window in Vegas Pro 23.
@Dexcon Thank you. Yes it sounds like you may be on to something. Since I am upgrading to a Magix product, I may not have the "VP build 278" as you say. The update is for Vegas Pro 23 DLM smart mask 2 update, version 23.1.0.2, where it senses I have 23.1.0.1. When it tries to install the error is, "There were no compatible products found on this computer". I can probably live without it, but it would be nice to have all functions and not be on my mind that I am missing an update. You would think I could maybe pay for the update or something, but then that might mean I should have bought the full version.
@Wesley-Carter If you installed vp23 to a drive other than the c: drive, maybe the DLM update cannot find it. If that's the case, you might try temporarily moving it to "C:\Program Files\VEGAS\VEGAS Pro 23.0" where it expects it to be in order to do the update. Then move it back.
23.1.0.2 was supposed to go with build 356, not 302.
@Howard-Vigorita Thanks for the idea. Have you try moving a folder over and back again? Wondering if that might create a mess with registry or other links, even though I would be moving it back.
@RogerS Interesting that 23.1.0.2 was supposed to go with build 356. I only have a build 302, so that might explain it.
Thanks for the idea. Have you try moving a folder over and back again? Wondering if that might create a mess with registry or other links, even though I would be moving it back.
@Wesley-Carter I do it when I need to run multiple builds of Vegas on the same machine. I haven't needed to do it yet with vp23 b302 and b356. But did it with vp21 b108 and 208 without a problem. But it caused problems when I tried it with later releases of vp21 which changed some file formats... window layouts I think. I needed to access that build with a different Windows login so it got a unique set of user-specific folders to save things in.
I don't have any problems installing Vegas on my D drive instead of my C drive. I have several versions of Vegas on my D drive. Same with other software. Everything works as expected. As long as the installation allows you to pick a different drive, it should be okay. There are some files that get installed on the C drive such as in Program Data and in AppData, even if you install the main software on a different drive. That works okay.