Undo Buffer Error

DRF wrote on 5/23/2003, 12:27 PM
I'm doing a video of almost all still shots - about 100 of them. I keep getting an error that says, "A problem occurred while processing the undo buffer. Save your work and restart Vegas." And then I have to shut down V4 and restart.

For some reason my computer is really choking on this project. When I start Vegas and load the veg file it may take as long as 10 minutes before all the still shots are fully loaded. I've done larger projects without these problems. I've tried it on my home computer and my work computer with the same results. The still shots are all jpg (about 100mb worth).

Any ideas?

Thanks in advance - DRF

Home computer specs:
1.0 ghz Athlon
768 Ram
270 gb space on 4 HD's (video drive has 110gb free)
WinXP Pro
V4.0c

Work computer specs:
2.4 ghz P4
512 ram
120 gb HD with 87 gb free
WinXP Pro
V4.0c

Comments

SonyDennis wrote on 5/23/2003, 5:10 PM
What format are the images. If TIFF, consider changing them to Targa or PNG. TIFF are read using QuickTime and it has problems with lots of images active at once.
///d@
DRF wrote on 5/24/2003, 4:09 AM
Thanks for the reply. The images are all JPG's. I've heard about using PNG files instead, but the file size is usually considerably larger than JPG - wouldn't this make matters worse?

Thanks!
DRF
mikkie wrote on 5/24/2003, 9:05 AM
"wouldn't this make matters worse?"

Might not as the system has to do slightly more work I think with a jpg - use a batch utility to convert to png and see if it helps? If doing this test, wouldn't worry about transitions or anything right off - just get the clips in there and see if it dies.
BillyBoy wrote on 5/24/2003, 9:27 PM
My guess and that's all it is... a guess is one of your JPEG's is corrupt and Vegas is choking on it trying to open it. A fairly common problem IF the file is corrupt for any graphic application.

Just messing around I just dropped 1,456 JPEG's on the timeline in one gulp to see what if anything bad would happen. Nothing, worked fine. Took about 25 seconds to load, spans just under two hours on the timeline, weighted in at 186MB.
DRF wrote on 5/25/2003, 4:12 AM
If one of these JPG's is corrupt, would I be able to open it in a graphics app? I scanned all of them into PhotoPaint (Corel) and I can still open each of them in PhotoPaint.

What I've done so far is to pull a bunch of the pics off the timeline and edit as I go, adding a few at a time. It's working but obviously it's slowing down as I add more. It's to the point now that I can't even scrub the timeline. The music plays with an occassional hiccup, but I see a new picture every 10 seconds maybe because it's trying to process it and can't keep up. I only have about 3 minutes worth of stuff on the timeline right now.

I'm wondering about memory. Bad stick of RAM? I have three stick of RAM, could one being going bad? What usually happens when RAM gets flaky? All other apps. on the computer work fine. Any other ideas?

Thanks!
DRF
mikkie wrote on 5/25/2003, 11:30 AM
'nother guess, nothing more...

BillyBoy did a great test (didn't know anyone had that many jpgs on disk), so as he wrote, possibly a problem with your jpgs. You saved them in Corel, which depending on version and settings can be somewhat different then more std jpg files. *might* try saveing/converting some in another app, and see if that helps.

FWIW, not all jpg saves are identical format files, and I have noticed a difference when trying to work with a Corel jpg versus something like Adobe or Pegasus when opening the file in a non-Corel app.