[Larry Brewer]

Strange you should mention that. I have been fighting the “not responding” for the last 24 hrs. When I commented on your post I hadn’t actually connected the thumbnail prob to Vegas locking up. The issue for me apparently was the upgrade I made last week to Vegas 12 Build 486. I have re-installed an earlier Vegas 12 Build 367, and the problem went away. ( the slow thumbnail creation and the re-building of thumbnails continues, but at least it doesn’t go into “not responding” and freeze up.)

Here’s the link to early Vegas versions and builds..

https://download.sonymediasoftware.com/current/

[Larry Brewer]

Steve
Thank you for the quick reply. I uninstalled the current build 486 of Vegas 12, and re-installed build 367. This ended the crashing. Build 486 had mentioned in the release notes… “Display of thumbnail images in the Project Media window has been refreshed.” whatever that means.

Understand that in the project I’m working on I have 7 clip bins, each with 400 to 600 clips. That is a lot of thumbnails. I have always felt that thumbnail creation in Vegas was slow, and was constantly re-creating thumbnails that it had already created.

While build 367 fixed the crashing problem related to thumbnail creation, the slow thumbnail creation, the rebuilding of thumbnails continues.

So it will be interesting to see if anyone else with a very large project has similar issues with thumbnail creation when using build 486.

Larry Brewer

i7, 24 GB RAM

[Larry Brewer]

Ron

I’ve had the same problem from the get go with Vegas. I’ve asked about it on this forum, but never found a solution.

[Larry Brewer]

Nigel
Thank you for the suggestions, and sorry I hadn’t gotten back to you sooner. I recall thinking that I had.

Still working the issue, I recovered 90% of the edit with a restore file. A less stubborn person would have moved on.

I will seriously consider using your suggestion of editing in segments and nesting the veg files. As long as I have used vegas, a person would think I would be more familiar with nesting and the obvious benefits. This might be a real nice way to cut down on the load times, and the danger of having all the eggs in one basket.. so to speak. And this project would really be perfect for that approach due to the layout.

Thanks again!

Larry Brewer

[Larry Brewer]

Thank you for that effort. I will make sequential saves going forward. Can you elaborate on why the veg.bak also crashes at 68%? They are both exactly 3,940,352 bytes, and were saved 23 mins apart, 23 mins in which I did no editing on the project. What could cause both files to be corrupt in exactly the same way?

As I mentioned earlier in the thread, a crash had occurred a couple days earlier and that “restore” file brought back 90% of the project. Thank god for crashes!

And in the sessions before the final disaster, attempts to open the veg at several stages in the project had failed, but the veg.bak had always worked. At least until the day it didn’t.

I have a strange habit of clicking the SAVE icon twice when saving on the fly. Not sure why I do it other than “just to make sure” the project gets saved. Can that be a problem?

Thanks for your help and advice.

[Larry Brewer]

I tried deleting the skf & skl files, no luck.

Haven’t got the right plugins on the 2nd PC I was attempting to use to test the file. Here’s a link to the veg. Could you see if you can open it?

5119_showedit102212.veg.zip

[Larry Brewer]

I am busy right now installing matching plugins on a sec PC to test that.

I will also try deleting the sfk and sfl files.

thanks!

[Larry Brewer]

The entire sad story is way back in the thread, but here is the error message.

“An error occurred while reading the file. Make sure you have read access to the file/folder and that it is not corrupted.”

I just tried uninstalling a re-installing Boris 7. No change.

I tried “hiding” the media by renaming the media folder and just letting it open with the media missing. No luck there either, it still fails at 68%.

[Larry Brewer]

Steve

Thanks for your suggestion regarding the RAM in my PC and the possibility of it being the cause of the .veg file failure to open. It turns out the 12 GB ram (8 GB usable) issue was due to Windows 7 upgrades that for some reason had refused to configure causing my PC to revert. Seriously. The downloading of 14 updates, and the following configuration had repeatedly failed and reverted. Once I got the updates to “stick” and configure, the RAM returned to 12 GB and passed the mem86 test.

The veg file will still not open. fails at 68% every time. I would like to discuss other possible causes and solutions. I’m thinking that the issue is related to work I did before the last save. I used some NewBlueFX glow effects and Boris transitions. I suspect there in lie the problem.

Question: The error window that pops up after it fails does not include the DETAILS button I’m used to seeing, so that I might learn a little more about the failure. Is that normal?

Question: Is there a way to have the veg file open and ignore the plugins?

Thanks!

[Larry Brewer]

You may have led me to a potential problem. Sometime in the last 3 or 4 days my RAM went from 12GB to 8 GB usable. I had not considered a link between the two problems. I’ve yet to determine the cause but it will be interesting to see if the issue remains after I find the memory glitch. I’ll try re-setting the memory sticks. Do you have any other suggestions?