ahahahahahahahaha😂

Disk Manager/ change drive letter and paths

Normally you can move projects across drives (copy back to c: etc.) but it must be looking for some resource that is now hidden from VEGAS.

It really shouldn't matter where the files are if you locate the Vegas file and then point to whatever drive the project files reside. If something this minor can break Vegas, then it must be one brittle piece of software.

If something this minor can break Vegas, then it must be one brittle piece of software.

On that basis, daVinci Resolve must also be one brittle piece of software - because the same thing happens in Resolve: and unlike Vegas Pro, Resolve doesn't offer a search window to locate or replace the missing media.

Just changing the folder name by one character where the media is located results in this in Resolve:

Well, I regularly move files from external drives to SSDs for editing and have never encountered this so something else is at play I think. What other resources is this project looking other than media for that's on the external drive?

What if you move just the project file to the desktop and open it and try to reassociate the media?

I get a message when I launch Vegas that it cannot retrieve the projects---the error message is " *.veg could not be opened" and then the project files disappear from 'recent projects'.

Yes, I've also had that happen over the years, but all that needs to be done in that case is to click on the .veg file in its current location and the project should then open in Vegas Pro albeit with the need to re-associate all the media with their current location/s.

As far as I am aware, 'recent projects' provides a very simple link to the location from where the project was last opened - that it disappears does not mean in any way that the project has been deleted/removed/etc - it only means that the link cannot find the .veg file's location from where it was last accessed.

RogerS's suggestion to simply rename the drive's name (D, E, F, etc) via Disk Management (as is named in Windows 11 and accessible by R clicking the Start button) then R clicking the drive's current lisitng and then click on "Change Drive Letter and Paths ...". This is by far and away the easiest and quickest solution and avoids the need for relinking/re-associating/etc.

@Former user

Disk Management is your friend, but, it goes deeper than that. If you "Change Drive Letter and Paths..." for all drives in Disk Management, then disks can go into and out of the configuration and Windows will remember the drive letter that you set.

All my internal spinning disks and USB RAID disks are "removable" or "hot-pluggable". They can come and go at my whim but always have the same drive letter assigned.

I can work on new projects without any of them in the configuration, only the NVMe disks.

If something this minor can break Vegas, then it must be one brittle piece of software.

On that basis, daVinci Resolve must also be one brittle piece of software - because the same thing happens in Resolve: and unlike Vegas Pro, Resolve doesn't offer a search window to locate or replace the missing media.

Just changing the folder name by one character where the media is located results in this in Resolve:

@Dexcon You are on the wrong forum, BlackMagic Design is here: https://forum.blackmagicdesign.com/ thanks.

(FYI, Rsolve will still launch and you can right click the media folder and re-associate the files with whatever drive it is stored on, but again, this is Magix Vegas, not Blackmagic--so I can understand your confusion.)

@RogerS @john_dennis Each project is in its own SSD. If I move projects to the home drive, there would not be any space left. I swap SSD's, depending on the project, all the time for years. Heck, if you have Vegas, the .Veg file and work files, you should also be able to open the projects on any computer Vegas is installed. For instance, if you have a team using Vegas and members are passing the project around to work on. When I open the Vegas file, the program crashes. Swapping SSD's really ought to be a non-issue. Maybe because I saved the *.veg file on the home drive is a no-no (no, I just checked, the .Veg is also saved to the SSD where the project files reside) and it should have been saved to the SSD as well, but that is silly. If that is the case, Vegas should *still* launch and get a message that the files cannot be found. Now that I think of it, this may be more of a 'crash' issue. There are a couple of larger, more complex projects I am working on and they have been sitting on the same drive dock for a while.

@john_dennis I see what you are saying about Disk Management (you are referring to the Windows OS feature?) where the drive letters assigned tend to be automatic, so it is best to pick (if you are going to assign) the last letters of the alphabet and use that for specific projects. I have a lot of projects going on and frequently swap between disks. For instance, a multi-year project on one SSD and then multi-week on another, multi-day and so on. So start with the letter 'Z' and work my way down, write on the drive, 'the X project'. Like that?

@Dexcon You are on the wrong forum, BlackMagic Design is here: https://forum.blackmagicdesign.com/ thanks.

Very amusing 😄.

@john_dennis I see what you are saying about Disk Management (you are referring to the Windows OS feature?) where the drive letters assigned tend to be automatic, so it is best to pick (if you are going to assign) the last letters of the alphabet and use that for specific projects. I have a lot of projects going on and frequently swap between disks. For instance, a multi-year project on one SSD and then multi-week on another, multi-day and so on. So start with the letter 'Z' and work my way down, write on the drive, 'the X project'. Like that?

I haven't gotten to the point of running projects on particular drive letters. My intent is to have the configuration stay the same over time. My optical drive has been R: (Read-only) since the days when I had to edit a batch file. My first archive has been D: for longer than I am currently able to remember. There are lots of other things that I'm currently unable to remember.

@Former user

I manually name all of my external drives using Disk Management (yes, it's a Windows OS feature) in part because they each have a pair for backup purposes. It doesn't really matter what letter you start from as Windows won't reassign manually assigned letters. It will assign new drives the next unused letter (though you can change that).

I can understand why you would assign drive letter paths, but if you work on a lot of projects that conga line across your computer, you eventually run out of letters of the alphabet. If you have an HDD or SSD, with the *.veg file AND the project files, that truly ought to be all you need to restore the project and continue working on it. If I swap the drive between a lap and desktop, with the same version of Vegas running on both, I ought to continue without issue, as I have before, regardless of drive letters being assigned to where. Maybe for some workflows you would want specific driver letters assigned, but not when you are turning Vegas into a daily driver. Again, this is really a crash issue and probably has nothing to do with letter paths. If I have hundreds of SSD's, each with its own .veg and attendant project files, it really shouldn't matter.

@Former user said: "the error message is ' *.veg could not be opened'."

Do you have a nested project within your master project?

@john_dennis Thanks, but I don't know how to do 'nested' yet, whatever that is. But it seems like something I ought to learn. I read about it, still did not get it. I will try again.

Did you import a veg file as media to your project?

In general you can move projects around without issue so the question is what's going on with your setup.

@RogerS Nah, I right click on the file, "open with Vegas" and away I go, then the white/ghost screen and the blue circle, cr-ash!

Importing a veg as media is "nesting"- I was answering your question. Sometimes it happens by accident if you import a folder full of media at once and don't notice there are veg in there.

Anyway, none of this makes much sense. Doesn't Vegas use relative paths from the project file. Are you moving the project and the media separately? Maybe make the veg available and see if it works for others.

If you keep opening the files, click 'ignore', the crashes eventually stop. Then I get the files back.

It really shouldn't matter where the files are if you locate the Vegas file and then point to whatever drive the project files reside. If something this minor can break Vegas, then it must be one brittle piece of software.

It does not matter where you parked your car. Just get in and drive away....

If key and car are in the same vicinity, and you know where the key and car is, why not?