Obviously, John's account has been hacked... :)

Did the active take info and project media window still show them as the correct clips?

Yes, Nick, the active take info and the project media window did show them as the correct clips.

Ohhh Man !!!!

AARRRGGGH!!

It just happened to me in Version 11 64bit, build 595 . And here's the evidence:


I then tried a "copy as takes" to get 00162 back where it should be and Vegas went into "not responding". It's sitting in this state. I hate to kill the process, because there might be a clue to the cause of the problem. Any suggestions?


...Jerry

Edit: I just went back to Vegas and it was playing the event, but the preview was all white. So, I pressed "pause" and Vegas went back to "not responding"

Edit2: I just sent an email to "ForumAdmin" asking whether there was anything I could do to help. We'll see if Paddy is available.

Any time Vegas enters a "hung" (non responsive) state, you can capture a snapshot of the app to determine what is causing it to hang. You can do this either using Task Manager (dump file will be very large), or using SCS's Diagnostic tool (resulting dump file will be smaller and easier to email).

Once you have created the snapshot, you can attach this to your support ticket. This will allow the developers to see the problem.

Thanks,
Paddy
SCS

When Vegas isn't replacing footage it renders clips to black. V11.595 replaced a few frames here & there with black which is even worse because I worry they will be undetected before shipping out projects to my clients. The replaced footage bug is also particularly bad because it is not always easy to detect when you do a quick change & re-render. Footage that rendered correctly the first time may have errors even though the changes you made were very small.

IMO This is too serious a problem to risk using V10 or V11 for commercial clients!

So for now I am back to editing in 9e. V10e also replaced footage and rendered to black so now we are a couple years past 9e with a NLE that still does not work. These are serious bugs that could jeopardize the trust my clients place in my work. In fact, I blew two Saturdays in a row becuase V11.595 failed to render footage correctly.

Paddy,

I submitted the following support ticket #120321-000103 (assuming you might want to get some higher level support personnel to look at this).

I added the images above and a copy of the mini-dump. I'm also in the process of uploading the Verbose Dump and the Task Manager Dumps to a downloadable location. It will take a while for it to be available as the filesize is about 3GB. Once the upload is complete, I'll post the URL. Edit: On second thought, the URL is in the service ticket. Seems that no one other than Sony needs access to the verbose dump data.

Let me know if there's anything else I might do to help.

...Jerry

1 week ago i was editing a 2 camera event. one camera on top, second on bottom.

was synchronizing both tracks, wen i looked, the second track had the same videos as the top one. WFT?? the videos where very different on image/cut points.

removed second camera videos, cleaned media pool, added again. the videos still where the same.

ok, so i stepped back, i thought: "i must be doing something wrong, lets start from the beginning."

opened videos of camera 1 on virtualdub (they where on separated folders), everything fine. opened second camera videos, everything fine.

added to timeline again. second camera videos are the same as camera 1 again.

i thought vegas was "loosing" itself on video name/files/folder, so i batch renamed the files, renamed folders, tried again, and everything worked fine.

pew, that was close. ;)

amendegw and malowz, in that Vegas session, or in your previous Vegas session, had you been working with more than one instance of Vegas open, in particular copying and pasting between them?

malowz, what version of Vegas are you running?

"in that Vegas session, or in your previous Vegas session, had you been working with more than one instance of Vegas open, in particular copying and pasting between them?"Nick,

I'm pretty sure the answer to both questions is "yes", but can't be certain.

...Jerry

In V10 this happens to me after I've been copying and pasting between projects. I see the problem the next time I open Vegas and (I think) the problem is seen in the project that received the copied media. This is how I deal with it. Clumsy but it works.

1. Have only one instance of Vegas Pro running.
2. Save a backup copy of your corrupted project.
3. In a new project, create and render an item of dummy media for each piece of affected media. They should be longer than the affected media (not entirely sure this is necessary though). You can use Media Generators to do this but remember to render an audio stream as well as video if your affected media contains audio. Name each media the same as the original media but with a suffix. e.g. clip01-DUMMY.avi
4. Open the corrupted project.
5. In the Project Media window, replace the affected media (right click on the media > "Replace...") with the dummies.
6. Remove all unusued media from project (lightning bolt icon).
7. Save
8. Close Vegas
9. Reboot computer (just in case)
10. Start Vegas
11. Open affected project
12. In the Project Media window, replace the dummy media (right click > "Replace...") with the originals.
13. Remove all unusued media from project (lightning bolt icon).
14. Save
15. Restart Vegas

Once I had this problem so I moved all the footage. When I opened the project Vegas had to look for the footage in the new folder. It fixed the problem in terms of the video footage being right on the timeline, but the names of the footage was wrong in the project footage window. Didn't really matter because the footage itself was correct on the timeline. I only experienced this problem once, so I don't have a lot to go on. I hope that helps in some way.

I have an average of about two crashes a workday with V10. Way better than V11 but in no way as stable as V9. I keep using V10 though because it is liveable, and because V10 works with Boris BCC-7. My fear of Vegas future stability is the only thing that has kept me from upgrading to BCC-8.

Paddy, it is hard to express how reassuring your presence is here. For many of us this is a livelyhood and these problems are a big deal.

I work in Vegas 9e. You all have scared me off of upgrading.

Recently I started using deshaker. It worked for me until it didn't. I would get error messages that I could not decipher.

After much wasted time and head scratching I figured out how to work around the problem.

Like many other users I usually drag clips from Vegas explorer straight to the timeline without going through the trimmer and creating subclips. I trim directly on the timeline.

I discovered that right clicking on all my clips on the timeline and selecting create subclips made all my problems go away. I'm sure many wiser heads could explain to me why.

Anyway I mention this just as a theory that I think Vegas can get itself confused as to which media it is pointing toward and this create subclips resolved this particular problem for me.

One of the reasons I have stuck with Vegas since 3.0 is that I can just dump the video on the timeline and start editing. I can also copy the VEG to an identical workstation with a copy of the source files and let it render-out various file formats while I start another project. Very efficient compared to my workflow with FCP or PPro.

However, Vegas 9e is the last version I feel comfortable using that type of workflow as the V10 & V11 present too many risks when more than one instance of Vegas is open at once.

If I need to stablize something in V10e, I rename the file, destabilize the clip to an int. file like DNxHD, and then add the new stablized footage to my 9e timeline.

I did have 9e crash just occassionally after installing 10e and 11.595 on the same drive. I have since switched back to an OS image that has 8c and 9e only. If I want 10e or 11.595 I reboot to a different OS drive that is identical to the first except that it has 10e and 11.595 added. It actually sounds more complex that it is... Having my workstations multiboot allows me to have a really clean install on the days I have to get a ton of work done. The clean install has no other 3rd party FX installed and only has the DNxHD & Blackmagic codecs installed.

Curious to know any other tid-bits of info regarding when it happened. Did it happen while you were editing? Or had you opened the project up? Did Vegas crash at all pre-swapping of footage? I ask because for me in V10 it never just happened while I was editing but rather after a crash or when simply opening a project.

Even though I have yet to see it myself with V11 I've been pretty hardcore about using the same methods I used in V10 when I was having the issue happen to me more than I would have wished (which would of course have wished that it never happened). Back in the days before this bug ever reared it's ugly head I would only save after major revisions just in case I ended up not liking what I had done. I'd say I'd maybe get to version 3 or at tops 5. With the new music vid I just posted in another thread I had gotten to version 25 of Daniel's vid.

As soon as I open a project that I had closed I now save as a new version. I hit ctrl-s OFTEN. If I make major changes I save as a new version. If I'm going to render I save it as the last version and just before rendering save as yet another new version, basically saving the same version twice. I do this because as I mentioned crashes during rendering for me seem to increase the odds of the swap footage bug happening. It's less hectic in practice than it sounds but even with V10 when I did have this bug I was almost always able to open my second to last save and not loose ground.

On a side note regarding crashes I had just had a few the last week that bothered me. After some digging I realized that under virtual memory in Windows 7 set to the first tick box "Automatically manage paging files size for all drives" on. This only had about 8000 mb's assigned to my C: drive, which is rather small as its solid state. After unticking I told it to do system managed on my internal C: and internal D: so it now has 16382 mb's. So far *knock on wood* have not had a crash.

- Ray
Underground Planet

"Curious to know any other tid-bits of info regarding when it happened. Did it happen while you were editing? Or had you opened the project up? Did Vegas crash at all pre-swapping of footage? I ask because for me in V10 it never just happened while I was editing but rather after a crash or when simply opening a project."Well, I'd been editing for several hours (saved often). I'd also closed the project and opened it again several times. I'm pretty sure the Video Event that was replaced was one that I copied from another project. I don't recall that Vegas had crashed at all during this process (will wonders never cease? [grin]).

I only noticed the problem when I made a test render and noticed that one of the video events was duplicated in the render. Went back to the project and noticed the error. When did this duplication occur? Can't really say as this was the first time that I'd tried a test render.

...Jerry

Yea, I know man, some have said they have had it happen in V10 with hitting the undo but mine was almost always after closing and re-opening a project. Like I said, or maybe in my description I wasn't clear but before closing I'm actually saving the same thing twice. I ctrl+s to save on that version and then save and re-name a second. On the occasion this did happen in V10, for me at least, only the most current one would get it. P.I.T.A. I know but can be a lifesaver.

- Ray
Underground Planet

oops - wrong thread ;-(

@Nick Hope
nope. only one vegas open all the time, and no copy, just drag and drop from explorer.

was a new project, vegas v11 521 (happened before the last update) x64 on win7