-
Corrupt veg file – nesting is involved
I have a series of veg files that just wont open. Whenever I try they ask where the first file is – supposedly an avi file. There are no avi’s. I’ve not made any so there are none associated with these projects. Consequently the project will not open up at all since it cant find that first file. The avi file name is not correct either. It has an “s” on the end of a work which is the only thing that distinguishes it from the veg I am trying to open.
On other vegies it tells me it cant open the project because a nested project associated cant be found.
Some months a go I had a go at importing a nested project as a test – but not on this series (I think). As far as I know it was not a problem. I didnt pursue it anyway and just forgot about nesting…until all this happened.Last night I did import a nested veg into a project that is part of the above problem. But this is one veg of this series I dont have the above “phantom avi file” problem with – the nested was a title for the series. It rendered out OK. Hours later I opening that project again and most of the shots and text/titles were not there on the timeline – black space except for two titles. My remedy was to go back to the original title veg and render it out then import to the other project – no more problems.
Dazed and confused as usual….I’d appreciate your advice. Thx
-
3 Replies
-
Whenever working with nested veg files it’s important to open each nested veg file in Vegas and clean the media pool by pressing the icon with the lightning bolt to make Vegas forget about files that you may have used in the past but are no longer needed. These files are still remembered by the media pool unless you sweep the project media pool to get rid of the reference to them. Then save the veg file and you should be able to nest it without any errors.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Thx John for your reply.
I cleaned the veg by hitting the lightning bolt to no avail so my workaround has been to refer to the dvd the client had with timecode window and trace back. In doing it that way I have ultimately saved myself a lot of time. grueling yes but satisfying nevertheless as the project is getting done.
Cheers -
Sorry that didn’t work for you but glad you found a workaround.
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up