vegas 8, vista 64 and bullet looks
 

I am trying to render out a 4 minute project and it keeps stalling out at 73 percent. I have rendered it out once before, since then added a couple different shots. its got grading throughout the entire piece. the shots I added are no where near where its stopping. what should I be looking for?? I am gonna try rendering without mbl, I am sure thats whats slogging it down. anyone else having issues rendering with MBL? I am using a new asus laptop, 4gb ram, vista 64 vegas 8.0c

Can you try rendering to a different hard drive and see what happens? That's what I would try first.

I have been fighting vista since I got it, I am trying to render to my external, but it wont let me, says I need admin permission,but I am the admin. any idea how I go about giving permission??

whoa, correction, I never caught on to the fact that it was 32bit, not 64 bit. dont know why my brain thought it was 64.

Do you have User Account Control turned off? If so, that could be your problem.

Turning off UAC can create a host of issues...including permissions issues.

BTW, I had enough issues that I actually ended up reinstalling Vista...as turning UAC back on didn't undo all of the problems.

Are you in 8-bit or 32-bit color depth? I ran into a similar problem when trying to render a short project in 32-bit color depth in 8.0c with tons of MB applied, i.e., it didn't finish. Also, what are your RAM preview settings? Too high (if I recall) could result in incomplete rendering, too.

Steve

i'm in 8 bit, my preview settings are at 300. I shut off the computer, restarted and was able to render the file to my external, and it seems to be cruising a long now. crossin my fingers. must have been some weird vista glich that needed a kick in the head.

annnnnnnd vegas just crashed, completely.

man, how are you vista guys able to get any work done?? I cant get a single render to work. I am pulling all the effects off, see if that makes a difference, then going shopping for XP tomorrow. this is killing me.

My Vista 64 machine running Vegas Pro 8.1 seems to be doing fine. It's just working just like XP has. Mainly during installation I get some popups asking if I really want this program to run or copy to happen but rendering has been fine.

I have never had too many issues with Vista...there was a bit of a learning curve to getting it to run just the way I like.

My biggest issues with it were when I turned UAC off, but otherwise it's been fine.

Sorry for your frustration, Ian. What are your system specs? What's on your timeline? I'd be inclined to look for culprits other than Vista (even though it's a fat target!), especially since many of us run it just fine with Vegas.

Steve

its vista 32 bit (the title of this thread is wrong), its been giving me issues from the get go, it restarts randomly, as I mentioned vegas wont render with any sort of heavy MBL grading (which I have opened a support case with red giant about). I dont WANT to hate vista, there are some things that seem really cool about it. but I am leaving to get on the the trail here in a few days and this thing needs to be running all my programs, or I am hosed.

for some reason I left the recovery CD in portland, so unless I can find another copy here in AK, I cant reload vista and see if that fixes anything. I dont have UAC turned off, as far as I can tell. It has all its recent drivers (again, as far as I can tell). starting to pull my hair out.

If the computer is randomly restarting, and rendering using MB (which hits the CPU hard) dies, could it be HARDWARE problems instead? Maybe heat issues? Or RAM problems?

well, I was wondering that, and I dont have an independant memory tester, so I ran the one vista gives you, and it said the ram was fine. but I dont know how trustworthy that is. if it IS a hardware issue I am completely hosed (unless newegg can get me a new one in 24 hours). is there another way to check for bad hardware?

Sounds corny, but have you opened your case to remove dust? Buildup can cause lots of heat --> odd problems. Sorry if this seems obvious; to some it isn't. :)

Also, you can download utilities (or maybe you already have one from your MOBO manufacturer) to monitor CPU temps within Windows (i.e., not in BIOS). Do a render and see what happens to your CPU temp. If the temps spike, particularly under the load that MB Looks imposes, then you have a cooling issue. A quick fix (i.e., new cooling fan/heatsink), but not if your source for parts is too slow or too far away.

How about memory? Did a stick go bad? Have any extra laying around so you can swap them out? Or how about just alternating pulling out sticks to see if you have a bad one? That is, pull out a stick (or replace it), try the render, and so on. If that's the problem, then you could pick some up at a local computer store for a real quick and easy fix (if they're around you way up there, that is).

If Vista is the problem, and you don't have the OS laying around, then I guess you can't do a HD reformat and fresh install. Hrm.

Steve

just spent 2 hours in a chat session with tech support. they found some gliches, and a driver I was missing that I didnt find for the video card, I am going to try another render and see what happens, crossing fingers!

well that didnt help.

is there a way to test the hardware without taking it to a computer store?

Ian download and run prime95 that will stress test you pc.
If that runs ok for one hour then your pc memory etc 'should' be okay
You can also try sisoft sandra and test individual parts ie memory, cpu

Do you have large jpegs in your project as that can crash vegas faster than anything else.

Im running vista 64 with vegas 8 and MB looks with zero probs(waits for lightning bolt to strike hehe)
good luck if its hardware as it can be very difficult to diagnose even a dodgy psu could be the culprit.

thanks, I will try those. no jpegs in the project, its all video. I realized the one thing I havent tested yet was a completely DIFFERENT timeline, I just kep trying to render the same piece. maybe there is something in the piece making it angry....still doesnt explain the random shutoff issues though.