Vegas Pro 14 crashing finding files

Kit-As-Was wrote on 10/4/2017, 9:23 PM

So I decided to do a little house-keeping on a project and move some files to newly created folders. I expected Vegas would ask me to find a missing file and then automatically locate the rest. That dialogue did come up but Vegas still had me find every file in the project and then after I located the last file the damn thing crashed.. Of course when I opened the veg file again I was back to square one so this time I told Vegas to leave all the "missing" tracks offline. Has anyone else experienced this kind of bug? What's the quickest way to locate missing tracks once Vegas is opened. If it helps I have both Vegasaur and UltimateS Pro 4. Thanks.

Comments

NickHope wrote on 10/4/2017, 10:30 PM

You can replace them 1 at a time by right clicking in the Project Media window and choosing "Replace".

You can also edit the "File Path" fields in the Events view of the Edit Details window. Might be quicker if you get going with copy and paste.

I don't know of any faster ways.

I just tried to adapt @johnmeyer's method of editing markers in a spreadsheet to editing file paths but unfortunately I couldn't get the cells to paste back into Vegas :(

I am still hoping some smart coder (or Magix themselves) will step into the void left after Peachrock stopped supporting their Veggie Toolkit which included the Offline Media Resolver. That worked pretty well, and I can imagine it could be improved further with some "intelligence", like the smart search for offline media in Media Manager.

Kit-As-Was wrote on 10/4/2017, 11:05 PM

Thanks for the reply. A better way to find "missing" files is sorely needed. I don't think it has changed in years. I wonder why my Vegas 14 is crashing at the end of the process.

karma17 wrote on 10/12/2017, 7:08 PM

I don't know if this helps, but I was having a similar type issue with rendering and I'm not sure there is an official Vegas position on this, but it seems to help when your source files are not on the same drive that is being rendered to. And, I don't even know if that's your situation.

Also, I had an issue where the system kept freezing up on one .veg file and for some reason, the culprit seemed to be an audio track where I had duplicated the same track several times and cross faded it over itself. Again, this might just be a one-off thing that happened to me. But ever since I've kept my source files on a separate drive from my rendered files drive, I haven't had any issues. I also keep an eye on .veg files that get really messy and involved, thinking that some in the code perhaps some thing is getting crossed up and causing a crash.