Error When Rendering EVERY TIME

teacherlady wrote on 1/26/2007, 5:09 PM
TImeline is over and hour in length with a lot of video. Using SONY Multi-Media machine with 1GB RAM. Have followed all the guidelines in VASST training videos for Sony Vegas Movie Studio and I have worked with Final Cut Pro and Premiere quite a bit. Each time I try to render the project, I get an error similar to "The instruction at . . . . referenced memory at . . . . The memory could not be read." I have tried everything I know to do--making sure all files are in the same folder, putting the entire project on an external 300GB drive (didn't help), putting the entire project on my C drive (didn't help), downloading the update from SONY and uninstalling and reinstalling the program including making adjustments to the registry. CAN ANYONE HELP!! I MUST get this project done quickly!

Comments

ScottW wrote on 1/26/2007, 5:20 PM
Does this happen at the same point in the render every time? If so, then you may have some corrupt media at that point.

If the failure point changes, then you most likely have a heat issues with your processor. Rendering takes a lot of CPU, which means that the CPU will run hotter than normal.

I would start by doing a dust bunny patrol. Power down your machine, take the side off and using some canned air, blow the dust off the cpu heatsink, fan etc. In fact, blow the dust off everything, including out of the power supply.

--Scott
teacherlady wrote on 1/26/2007, 5:39 PM
It was happening at 63% each time and then got to 64%. I assumed corrupt media so took a lot out and replaced it. Now it's happening with minimal %. Thanks and I will try it!
SCSIraidGURU wrote on 1/26/2007, 7:01 PM
www.memtest86.com

Run a memtest on each stick and find the bad stick.
Paul Mead wrote on 1/26/2007, 10:16 PM
Can you tell us more about the event that is being rendered at the time of the failure? Is it from the same source as all the other events, or is it something different, say, maybe a video clip from a still camera or something like that? Are there any effects applied to that event? Anything different about it at all?
teacherlady wrote on 1/29/2007, 10:09 AM
Upgraded my 1 GB RAM to 2.5 GB this weekend. No special effects applied except basic transitions. Video was captured from SONY DVD camera -- the DVD itself. The error seemed to be happening in a group of still pics. Have taken them out and re-imported the originals and tried again....same error. Then actually removed that entire group of pics . . . same error. Stops rendering. I thought it was corrupt picture files, but then wondered if it could be a corrupt portion of the actual Vegas file itself??? Soooo, I have saved it under a different name. That didn't work. I have MOVED all the timeline files down on the timeline--meaning to the right of the place where it constantly stopped rendering----and then tried to select the events and render the loop region only---didn't work. I'll do another scan disk and defrag tonight, but I'm running out of ideas to try. I WAS able to get the first half of the project rendered by splitting it in half. But the second half has the place where the error occurs and I can't seem to get around it.
teacherlady wrote on 1/29/2007, 10:15 AM
Thanks Scott! The dust bunny patrol went on duty and it really wasn't bad at all since I had recently put in a new HD. But I think the HEAT issue was definitely a factor. I have opened it up, taken it out of the cabinet, have a small fan blowing on it to keep it cool while rendering, and bumped up my RAM to 2.5 from 1GB. At least I was able to render the first half!! Now to get the second half. I know it would all fit on one DVD if I could just get it past this "freezing up" or stop rendering error within the 2nd half! Seems to be corrupt picture files or a corrupt project file??? Not sure how to get around the corrup project file???
KayAt wrote on 1/29/2007, 10:31 AM
You could try opening your picture files in Image software and then resaving them to another name, format? BMP or JPG work best for me
rustier wrote on 1/29/2007, 8:32 PM
If you keep getting jammed at the same point and pictures are involved - I would guess the problem to be the pictures. Resize your pictures to a resolution that VMS won't have to mess with. (It will resize to match your output but there are limits and some snags. I don't know why Sony doesn't just make the sizing universal - check that - they want to sell more software - it is soo annoying and people keep runniing into this snag - oh well) Kelly Chien (chienworks) has the exact numbers. Search the forum for photo size. Dollars to donuts I bet you got a few whopper pics in there and Vegas is belching. knock the size down
StubbornSwiss wrote on 1/30/2007, 4:36 AM
If I may chip in here.......

I don't think your problem is your system. I am running VMS 7 Platinum on a Pentium 4,1.7GHz, with 1G of ram. I know this is an older system (what system isn't "old" in these days of Vista), and I know it takes a bit longer to render a larger project, but I have no problems with it whatsoever.

As has been suggested, try reducing the size of your pictures if the original resolution is really high. Working with pictures, I always reduce my picture size to 1024 x 768, and I still get absolutely great looking images on my 50" TV. (I'm sure if I had to, I could even reduce the size some more). I use a free program called:

PIXResizer

Have you tried putting together a "mini" project, with totally different material, just to see if in fact it will render through to the end?

I'm not really a guru on these forums, but I hope I have been a help in some little way :)

Albert
teacherlady wrote on 1/30/2007, 9:20 AM
Everyone stand and do the "happy" dance!! I was able to get Part 2 rendered last night! I still haven't got the entire project to render as one, but I'm still trying. The picture size could def be an issue and causing the "burp!" Loved that term! My pastor actually put the project itself together and I'm finishing it for him, so I didn't pay much attention to the file sizes! Should have :-) I will check it out this evening using Photoshop and get them down . . . the entire project made it to 69% last night and then froze. However, the 2nd part rendered completely . . . how?? I ended up copying all of the timeline pics/video/music, opening ANOTHER Sony Vegas Movie Studio application, and then copying to a new timelime and saving with a new name. Rendered without a hitch! By going to File/New, and copying, it wouldn't work. Certainly something to keep in mind for future problems with others! As always, still learning :-)
Paul Mead wrote on 1/30/2007, 9:37 AM
Edit: Looks like you posted a solution before I posted this response. Oh well, I will leave this just in case it may be useful to someone.

Assuming that you can reliably catch the failure at the time it happens, can you note the frame number that was being rendered at the time of the crash? After the crash go back in to VMS, find that frame, move the corresponding event and all events after it to the right (leaving that place in the timeline empty) and try rendering again. If the failure now happens at the new location for that event then I would suspect something about that event. If not, well, I dunno...

I also second resizing the still pictures, just for grins. VMS simply does not properly manage its buffers when rendering hi res pictures. I got burned by that a year ago and spent a huge amount of time tracking it down. In addition to PixResizer, you can also download a Microsoft powertool from the Microsoft website that enables a resize option in Windows Explorer. Very handy to use since you can resize using the regular file tool that you use all the time, Windows Explorer. It allows you to select multiple pictures and resize them all at once -- quick and easy.

That said, I can't believe that we still have to do this kind of stuff just to get VMS to work properly. I sent a data DVD to Sony a year ago with all the files necessary to demonstrate the problem and I begged them repeatedly to fix it. I never heard anything back. Hey, Sony, this is really causing a lot of headaches for people. I mean, how many people use still cameras with less than 2 megapixel resolution these days? It would really be appreciated if this problem was resolved.
teacherlady wrote on 1/30/2007, 7:12 PM
Praise God~~Hallelujah~~Amen!! It is finished :-) I took each still picture into Photoshop and brought the size waaaay down and rendering completed flawlessly!!

Thank you to EACH one of you for your input--every single suggestion was put to use! The completion of this project involved many . . .thanks for using your gifts of "help"!

The DVD was created based on an adoption journey~~check it out!
www.blessingsfromvietnam.com
Paul Mead wrote on 1/31/2007, 6:52 AM
After you have caught your breath and had a chance to enjoy your success I suggest you file a formal problem report with Sony telling them how this problem caused you a tremendous amount of stress. Maybe if enough people complain the problem will finally get fixed.
StubbornSwiss wrote on 1/31/2007, 7:18 AM
First of all, congratulations on your "new" family. I visited your web page, and all I can say is..... Blessings!

Secondly, by using PIXResizer (and I'm sure other software available), you can reduce the size of a bunch of pictures at the same time.

Finaly, I agree with Paul..... if enough people complain maybe Sony will do something sooner. This is the same situation with the Audio Restoration plug-in in VMS 7 Platinum. Guys & Gals..... please send "polite" complaints to Sony :)

Albert