I'm trying to render a fairly complex 24 minute segment to a new AVI file. It's frozen at 48% after two hours and the clock keeps ticking. Any idea what causes this? I'm using Vegas 8.0a with Neo files and I also have .psds and quicktime on the timeline.
Keep an eye on your page file via the task manager. See if your system is running out of ram. Do you know what it is hanging on? Is it a psd file? Is it a part of the video that you applied a certain fx to?
Well, I was able to retrieve the rendered part of the file and it ended on a clip that I have Magic Bullet applied to. Although I've been rendering it in small chunks now which it working fine. I think the memory was around 2.5 gb on the task manager when it was frozen. I've got 4 gigs installed but only two show up in XP. Anything I can do if this is a memory issue? Should I set my virtual memory in some special way?
Marc, just a suggestion and that's to change your PSDs to PNGs. The file size should drop (in some cases a lot) which will make Vegas happier.
BTW, if you're using multi-layered PSDs and only saving the relevant layer(s) as an image, the image size will still be that of the full PSD .
At least it was on a recent project I did (Photoshop 7) before I realized it. and changed to PNG.
> I've got 4 gigs installed but only two show up in XP.
What do you mean only 2 show up? I have 4GB of memory and when I right-click on My Computer and select Properties the System Properties show 3.25 GB of RAM. You should see the same or else something is wrong with how your computer is set up.
In the Task Manager under Physical Memory (K) the amount labeled Total should be around 3405508 for a system with 4GB of memory. Make sure all of your RAM is recognized.
> Should I set my virtual memory in some special way?
Yes, you should set you virtual memory to the max Windows recommends for both initial and max. In System Properties | Advanced | Performance Settings | Advanced see what pagefile size Windows recommends. For me it was 4987 MB. Then set both Initial size (MB) and Maximum size (MB) to this value. This will make permanent swap file that does not grow or shrink which will give you the best performance.
Can you describe what kind of levels(PF Usage) I should be seeing under task manager/ Performance while working on a vegas project. I have 2 GB of ram. Quad core xp
I am trying to figure out if I am experiencing crashes because of a corrupted file or just a memory problem. I notice that it crashes when the PF usage is 1.52- 1.8 GB most of the time around 1.6 GB. As I add video the PF Usage keeps going up when it hits 1.5-1.8 ( I think it depends on how long the last clip is that I bring in that determines the number) then it crashes. Do you have any idea why this could be happening? I have already adjusted the pagefile size according to your last post JohnnyRoy.
No, he shouldn't necessarily see the same, but 2 GB is very low.
Evidently WIndows on a Mac can only see 2GB out of 4. And we have HP XW9300s at my work that could be configured in a way that only 2GB would show in XP or Vista 32.
In fact, those XW9300s only show about 2.5 GB out of 4 when they're configure properly. This is because of the specific mix of cards we have installed.
Hmmm. My page file gets up that high when I'm running a handful or two of very piggish programs. If yours gets that high just running Vegas I'd maybe be a little suspicious.
As far as I understand it, programs under XP32 and Vista32 are limited to a total of 2GB. That's RAM and Page File combined. I wonder if Vegas can hit that point, and what happens when it does?
I don't know if that really has anything to do with StormMarc's render frezes, though.
I am having the same problem here with a 2 minute clip that uses up to 19 tracks.
The project has no film clips, just fotos in png format plus some animated text and of course audio (wav).
Rendering to m2t (HDV1080-50i) and/or avi (1080i intermediate) wouldn't go through. Vegas always crashed around 60...70% in the project (the clock kept on ticking but nothing more happened).
Rendering to SD (576/25i mpg2) was fine, however.
Even after spliting the project in two one minute chunks the second one would constantly cause Vegas to stall.
Setting the Dynamic RAM preview to 0 seems to solve the problem - at least now my second half runs through.
However I have not yet tried to render the whole project with that setting.
P.s.: My System is a 3,06 GHz Intel-pentium, Windows XPsp2, 2 GB RAM
> I've got 4 gigs installed but only two show up in XP.
What do you mean only 2 show up? I have 4GB of memory and when I right-click on My Computer and select Properties the System Properties show 3.25 GB of RAM. You should see the same or else something is wrong with how your computer is set up.
***JR, you're right, I have 3144164 of physical memory showing up in TM. What I meant was in Vegas (about Vegas>computer = only 2 gigs are recognized.
> Should I set my virtual memory in some special way?
Yes, you should set you virtual memory to the max Windows recommends for both initial and max. In System Properties | Advanced | Performance Settings | Advanced see what pagefile size Windows recommends. For me it was 4987 MB. Then set both Initial size (MB) and Maximum size (MB) to this value. This will make permanent swap file that does not grow or shrink which will give you the best performance.
***Thanks... I made the change (it was set to system managed). QUESTION: The Pagefile should only be on the system drive right?
QUESTION: The Pagefile should only be on the system drive right?
No, if possible your pagefile should be on a separate drive to the system drive. Also separate from your data drive.
I used to have my page file on a nice fast WD 36G 10,000rpm drive that I didn't use for anything else (except quick temporary backup), but with file sizes the way they are now I've had to replace it with a slower 500G.
I hate seeing that super little drive just sitting on the shelf!
I just had another render error. PF use was at 1.44gb. Task manager listed Vegas as running but the remaining time ran out on the render progress bar and Vegas went for 8 hours stuck at 44% until I ended task. Oh well back to rendering in small pieces.
Im having a similar issue with rendering - and I also have quicktime/.mov video on the timeline??
If I try to slectively pre-render the timline, it hangs/freezes after the 2nd chunk is rendered (vegas pre-renders in chunks) it is that "tori Amos" contest files that was mentioned here in an earlier post...
I only have a GIG of ram installed and the pagefile stops growing after 480MB - I'm currently rendering out to an .avi file and it seems to be working.
The timeline is about 5mins and has Croma key and Croma blur added on track level - settings are 8bit render - tried 32bit and it froze.
Diffinetly some render issues with Vegas Pro 8a sony support?
update: Vegas rendered the file and hung at 100% complete but the clock kept on counting, I let it go for about 10 mins before I had to end task to close Vegas.
Tried to open the file in windows media player and it was all studdering and the audio was all out of wack - I then opened vegas again and dropped the rendered file on the timeline and it played fine????
This could be a quicktime issue - StormMarc, could you remove the quicktime files from your timline and see if you can both prerender and render out to a file and report back what happens?
The problem is that sometimes I'm having success rendering the entire project (even with quicktime on the timeline) so the problem not consistent. The quicktime files I'm using are from the Digital Juice videotraxx library.
I'm also using magic bullet looks on the quicktime files. Vegas 8.0a does seem much more stable than the first release but this is definately still a problem. 32 bit is still a nightmare for me.
with my core2duo & 2GB RAM, a 36-min. vegas project stopped rendering .wmv about 40% done - counter still going, but Windows Task Manager showed only 2% or 3% CPU usage.
Next day I tried again without changing anything and it rendered just fine; I did it after finishing my day's work, so no programs were running in the background (but I did leave Windows firewall and AVG antivirus running, etc.).