OK. I've added the information. This problem seems to be worse than it was originally --now I can't seem to render in any format, whereas earlier I was able to render at least one .M2TS file but I don't remember which exact settings I used. Now I can't seem to render anything without getting the error message.

I'm using Vegas Pro 9.0c (demo version)

I just looked at my posting and for some reason its not including my system information. I'll add it manually below:

Operating System
Platform: Windows XP
Version: 5.01.2600 (Service Pack 3)
Processor
Class: AMD Phenom(tm) 9950 Quad-Core Processor
Identifier: AuthenticAMD
Number of processors: 4
MMX available: Yes
SSE available: Yes
SSE2 available: Yes
SSE3 available: Yes
SSSE3 available: No
SSE4.1 available: No
SSE4.2 available: No

Display
Primary: 1680x1050x32

Memory
Physical memory: 3,327.2 MB
Paging memory available: 5,210.8 MB
Virtual memory possible: 2,047.8 MB

Video Card: NVIDIA GeForce GTX260

as a test, drop some generated media on tl and see if that renders ok.

don't know about the format from canon camera, but i usually encode ALL varieties of mp4, avchd to .mxf BEFORE editing. never had a problem thereafter....

This thread might help.Low memory error
Search the forum for "low memory error" -- there are numerous discussions that will have ideas of what might help.

Will any type of media render in any format?

I found Lars message about setting memory to 4000, but when I tried to change it I was only allowed up to 1024, and that didn't fix the problem. I just saw a new post where someone had been rendering for months without a problem, but after updating he gets the same message. I think this is called a "bug". It should probably be fixed rather than making people work around it.

By the way, I downloaded a demo of Neoscene form CineForm and after converting my files to Cineform AVI I am able to render without a problem. I previously I was trying to render AVCHD directly. It seems this program isn't quite ready for AVCHD. I can play with them on the timeline, but can't render them unless I change them to a different format.

I own a copy of CS3 which is also compatible with the Cineform AVI. I was demoing Vegas Pro 9 (I own Vegas 6) because I thought it could deal directly with my AVCHD files.

If I'm going to have to buy NeoHD anyway I probably won't buy upgrade Vegas as well since I can use the files in my Premiere. But I do find Vegas more intuitive to work in.
Ron

"It seems this program isn't quite ready for AVCHD. I can play with them on the timeline, but can't render them unless I change them to a different format."

I render some extremely large avchd time lines without issue at all so the problem isn't Vegas. I suspect an issue with your machine.

Same as Rob I have no problem rendering AVCHD without using any proxies.

Switch over to a 64bit OS, use Vegas 9 64bit and toss in 24 megs of RAM.

Your AVCHD will render fine. ( I "virtually" guarantee it )

I assemble in 32bit Vegas cause it seems to edit smoother, but I render in 64bit cause Vegas 32bit crashes 50% of the time. (only on render)

CT

So could you describe your system? (It wasn't stated on you profile.)

I have a laptop which is not nearly as powerful as my desktop, and it will render the AVCHD with Vegas Pro9 (albeit not very quickly), so I think my machine "should" be powerful enough to do it. And it works with the HD files in the cineform-AVI format.

To me a "bug" is when program doesn't work sometimes as it should for reasons which aren't obvious. Can anyone see an obvious reason for my not being able to render the AVCHD?

If the render only works consistently if using the 64bit OS, then is should be advertised that way. If it's only compatible with certain MB's or certain CPU's then it should be advertised that way as well. My machine (Quad-Core CPU, SATA II hard-drives, 4 Gig Ram, Windows XP Pro) exceeds the minimum requirements stated for the program. So indeed it may be my machine that's the problem, but it's not obvious to me what exactly about my machine is the problem.

In any case I'm not the only one finding this issue, and others only started finding this issue with the latest upgrade, so I'm still thinking there's something in the program that needs fixing.

I'd love to see it working cause Vegas is way easier to work in (for me) than Premiere CS3.

Ron

I'm running win7 64 on a quad core with 8 gig ram...

What do you have your Preview Ram set at?

Ron -- you seem to like Vegas. I do too. So I'll show you how much I like Vegas.

I've had my share of Vegas problems too over the years. When I installed Win7 on my newest built computer (an i5-750) I was sure that all went well but to my dismay my install of Vegas would not perform. You'd think it was Vegas that was at fault. It kept crashing on certain media. My laptop had no trouble with the same media. My old Vista system had no problems eiither. I started thinking it WASN'T Vegas but my new system. Somehow Vegas 9 on my newest machine would not run right. So I took my blank spare boot drive ( I always keep an identical boot drive spare around in case my boot drive fails) and I loaded a fresh copy of Win7 -- loaded the system drivers - video card drivers etc. Basically a clean fresh install. I installed Vegas and wham! .. No problems.

This was the second time I've had to do this. On Vegas 8, I had a similar situation under XP. All was well and then one day --- I could never figure out what went wrong, but a clean install of XP worked in that case.. It's lots of work I know --- but to me it was worth it to be able to run Vegas reliably. In both cases I kept my original boot drive intact and never lost any data. It's one way to find out what goes on because it seems to me your system is plenty fast enough to render AVCHD - Paul

OK, so it's looking like 64bit is the way to go for the AVCHD stuff. I have my Preview set at maximum 1024. I suppose with Win7 I could give it quite a bit more.

I'll have to decide if Vegas is worth the OS upgrade. Once this demo runs out and I'm stuck using Premiere for I bit I may be convinced. Or maybe I'll upgrade to 9, but use Neoscene until I can manage the OS upgrade. (Or maybe they'll fix the bug on the next release:)

Ron

"OK, so it's looking like 64bit is the way to go for the AVCHD stuff. I have my Preview set at maximum 1024. I suppose with Win7 I could give it quite a bit more."

No, you will not get more... you're using vegas 32 and you can't get more without a bit of a hack. You don't need more anyway (unless you're doing lots of preview through dynamic playback). If anything you have it set too high. Drop your preview ram to about 128 and see what happens.

I agree with Rob. Set your Dynamic Ram preview much lower for rendering. I use 64 or even 32. Just don't use Zero.

rsi,

I've seen this problem side stepped in quadcore systems by reducing the threads from 4 to 2 or possibly 1. It is something simple to try if a deadline is in your face.

David

Sounds crazy -- but Lars got his project to render by using "4000" as the Dynamic Ram Preview setting. Dynamic Ram preview is not suppose to help or hurt the rendering but store the PREVIEW in RAM so as to get smooth playback of effects or transitions. BUT -- apparently -- 4000 worked for Lars.

Dyanmic Ram Preview to 4000

You can't set Vegas 32 that high, even if you reset through internal settings it will only go to 3072. He is using a 32 bit OS along with 32 bit Vegas.