or check your temporary files folder for "filename.veg.bak" file. You may be lucky to find a backup file there.

It's happening to enough people that I would call it a bug and report it.

(Yes, I used the "B" word).

Hi All

I've fixed it, but it wasn't as easy as I thought

I added another take with the right clip an though that would do it.
But every time I came back to the project (after saving and quitting vegas)
The same thing happened !
I had to copy the source material, calling it *2.* (like transition2.mov)
And then adding that material as a take in the time line.
Anoying ...

thanks for your replies.

I also think its a bug, I've seen other posts describing similar issues.

Kind Regards
Christoffer

btw.
I'm on a win7 machine with 12 GB ram and i7 quad core 2.67 Ghz

yeah, it's a bug. I had to happen to me on a big project. Had to keep making copies of the veg file and fix it.

Dave T2

Hi all, please provide as much detail on this issue as you can, so that we can reproduce it. It would be helpful to get an idea of your workflow, especially with regards to Project Media. We believe this issue can occur on large projects, when copying/pasting media from one .veg file to another, but that's about all the information we have at this point. If you can provide any additional specifics, it would help us in resolving the issue. Thanks in advance.

On the project it happened with.

1) 90 minute video final length.
2) Consisted of 2 camera shoot with DV AVIs. The timeline was edited using the Multicam feature in Vegas. The audio track was replaced with a separate WAV file recorded on a digital audio recorder.

3) Built as two 45 minute projects and then nested for the final edit into one project
4) Sometimes when I would open the final project with the nested files, one of the nested files would be corrupted. It was always the same file that got corrupted. The AVI in that file was slid on the timeline throwing it out of sync. And some scenes were white.

5) I would go back in and try to fix the corrupted project, but I could not. I would generally have to rename the project and then fix it. Once I got it fixed, it would work okay until the next day or so when I would open the project again. I found that sometimes if I opened the fixed project before I opened the final nested project, that it seemed to keep it from getting corrupted, but this is only anecdotal.

6) All AVI files were captured to the same folder, but different names. Some stills were used, but I can't remember if these got corrupted or not.

7) Computer is Core 2 duo 3ghz, 2 gig memory, 1 IDE system drive, 2 Sata capture drives. Using Vegas 10B on Windows 7 with latest SP.

This was a few weeks ago so I can't remember all of the details, it you have specific questions, please ask.

Dave t2

Dave T2, thanks for your reply. That's very helpful. Do you recall if you ever copied and pasted events from one timeline to another while creating these two child projects?

Sometimes when I would open the final project with the nested files, one of the nested files would be corrupted. It was always the same file that got corrupted. The AVI in that file was slid on the timeline throwing it out of sync. And some scenes were white.
It sounds to me like there are two issues occurring within the corrupted child project: 1) a video file is being erroneously slipped within the event, and 2) one or more media files are being replaced by a white media generator. Is this interpretation correct?

Regarding the "white scenes" :
--Did your project contain white media generators prior to the problem?
--After the video has been replaced by white media generators, do the correct video files still appear in your Project Media list? Or are they completely gone from the project? In other words, are the video files being replaced only on the Timeline, or also within Project Media?
--If you enable View > Active Take Information, what is the label displayed on the Timeline event? Does it correspond to the correct media, or has the label been changed as well?

Thanks again for your cooperation, and if anyone else has additional input, it would be appreciated.

Let me go home tonight and see if I can replicate the problem. I think I still have the project available. If it becomes trashed, is there any advantage to sending you the Veg file.. Actually, now that I think, I may still have some of the trashed veg files on the computer.

If so, should I send them and where?

Dave T2

Yes, we'll contact you through your profile email address. Thanks.

I still need to be able to repro the issue in house, with media and all, so if any others can contribute their findings, please do so.

These are good questions.

I'm just fishing here but I'd be curious about the names of the files as well as the total length of the path to the file. Windows has path length limits. I don't know if Vegas also has limits, but I think this sort of problem has come up for FCP users in the past. Parts of FCP had their own varying limits that weren't the same as OSX's limits, so you could get filename truncation.

I think it's more likely that this is timeline corruption though. One thing I used to see (haven't checked in a while) was that if I created subclips, renamed them in the project, and then copied them to a new project, those subclip names would revert to the defaults they started with. It suggests to me that Vegas was able to retain two names for a media object.

Rob

"One thing I used to see (haven't checked in a while) was that if I created subclips, renamed them in the project, and then copied them to a new project, those subclip names would revert to the defaults they started with."

Rob, I'm pretty sure that this is actually how Vegas handles subclips that are copied from one veg to another. It's a real shame too since all of our work in naming the clips goes right out the window.

Erik

Strange, happened to me this morning, a image on the network drive had been replaced with part of a clip further down the timeline, lucky could just drop the image file as a take and carry on.

The image was dragged from a windows folder and dropped onto the TL and the other clips cam in via the normal ingest.

It's a real shame too since all of our work in naming the clips goes right out the window.

+1. It's especially a drag since you'd not likely find out that you shouldn't rename subclips until you're pretty far down that path.

The overall observation here is that Vegas is capable of retaining two different names for a clip within the veg file, and that Copy/Paste doesn't necessarily move *all* the info about an element. This might have nothing to do with the current issue. Like I said, I'm fishing.

Rob

Dear ForumAdmin,

I've noticed your involvement in two different threads here over the last couple of weeks. Just between you and me...is this a sign of more such involvement in the future? I like it very much when I feel like our voices are being heard back at the Mothership. Thanks for keeping us in the loop.

Erik

Strange, happened to me this morning, a image on the network drive had been replaced with part of a clip further down the timeline, lucky could just drop the image file as a take and carry on.

The image was dragged from a windows folder and dropped onto the TL and the other clips cam in via the normal ingest.

"The overall observation here is that Vegas is capable of retaining two different names for a clip within the veg file"

When the problem being discussed has gone wrong for me and others clip "abc" refererences the wrong file. Invariably it does seem to have been a file that was once in the project.
The very strange thing though is that Project Media shows the correct file.
Even more curious is that trying to replace the wrong file with the right file fails, you just keep getting the wrong file.
Physically renaming the wrong file or moving it so that on reopening the project Vegas raises a missing file message and then specifying a replacement file works for at least some people. I'm reasonably confident that I tried that and it didn't work but it was over a year ago so I could be wrong.

I had previously thought Vegas should be able to trap this problem fairly easily. If Project Media lists the clip as "D:\123\abc.avi" and some internal value has it as "D:\456\xyz.avi" a simple comparison should be able to raise an exception and fix the problem or alert the user.

What I've ignored is subclips and they are interesting. The concept of subclips is something new in Vegas, they didn't exist when I started using V4 and I'm pretty confident in saying the problem under discussion didn't either. There does seem to be a correlation between this problem arising and the introduction of the "subclip" concept into Vegas.

Bob.

It happened to me once a few weeks ago using a relatively simple project in Vegas 10.0c-64bit under Win7-64. The event that got replaced was a JPG image that I was using as a background in a 16x9 project. I was overlaying a series of 4x3 images which were PNG files. It was replaced by another JPG file which was in the project media list but was not in use. I could not replace the file as Vegas thought it was using the correct file. I had to blow up the background track and start over.

John, this sounds like the sort of project that you could share with SCS with media included. Assuming the pictures were something you could share with them.

Rob

Good idea but the project was more than still imges, it also involved about 90 minutes worth of video and generated media. The video and the project was 16x9, it was a talk and the 4x3 PNG images were from her Powerpoint presentation. The 16x9 background image was to pillarbox the Powerpoint slides.

They wouldn't need more than the project file to determine that something was wrong. Someone with a good knowledge of the structure of a project file could write a utility to detemine there is an error in it, possibly it would throw some false positives but a human should be able to sort the true positives from the false. I'm not so certain though even if they had the project file and the media its going to be of much help to them.


The problem that SCS seem to be grappling with is being able to predictably reproduce the problem. They need to see how it happened, not just the result of it happening. Given the very low incidence of this problem I suspect that will be no easy task for them at all.

Bob.

I have had it happen on at least two projects. The first was easily fixed, but the one I discussed in this thread kept re-ocurring (sp?) after fixing.

Hopefully I can make it do it again.

Dave T2

I cannot get the problem to happen again. BUT I did noticed something about part 1of the project. Apparently when editing some of this, but not all, I had QUANTIZE to frames turned OFF. some of the cuts are straddling frames. May not be relevent and I did not catch it before. This file is the one that kept giving me errors, such as the sync sliding. Part 2 is quantized correctly.

Otherwise, I don't think I can offer anymore.

Dave T2