Low Memory Error

PerroneFord wrote on 12/29/2009, 9:17 AM
I thought I'd post an error indicative of the problem some are having with AVCHD files.

In this example, we have a single piece of media, with a duplicate track. The top track has a B&W effect, the bottom track has 3-wheel color correction applied.

Clip is 2:20:05
Source is Canon 5D (1080/30p)
There are no other user apps running.
Preview is at (good/half) to save memory
Encode did not complete a single frame before error

http://i666.photobucket.com/albums/vv28/perroneford/LB/lowmemory-1.jpg

Comments

TLF wrote on 12/29/2009, 12:26 PM
Perrone,

It's just a thought, but are you certain that the .mov files are 30p? It may seem a silly question, but there is a reason behind it...

My old Kodak stills camera produces .mov files, but Vegas used to stutter like crazy with them, and would freeze like crazy whenever I tried to work with them. When I examined the timeline, it appeared that they has a framerate of 24fps, not the 25 or 30 I had expected. Yet altering the timeline settings did not resolve the problem.

So, just a few minutes ago, I loaded some clips again, but this time told Vegas 9.0c (32 bit) to match the project settings to the clip. And much to my surprise I discover that the framerate is in fact 24.055fps. Allowing Vegas to match the project to the clip has improved the playback to the full rate.

So could you check what the clip's framerate really is? It's a long-shot, but might reveal something useful.
PerroneFord wrote on 12/29/2009, 12:35 PM
The Canon 5D only shoots 30.00p. Vegas reports it as 30.00p when I match the clip. GSpot reports it as 30.00p, and I've built a template specific to the Canon 5D for 30.00p.
Rob Franks wrote on 12/29/2009, 4:25 PM
PF,
Is it possible for you to upload the clip some place for testing?
I'd really like to see what this low memory error is all about first hand.
PerroneFord wrote on 12/29/2009, 5:06 PM
I can manage to send you about 15 seconds worth. But your contact information is unavailable.
JohnnyRoy wrote on 12/29/2009, 5:17 PM
Perrone, I couldn't help but notice on your screen shot that your Up Time is 4 days. You might try rebooting the computer and then render again. I don't know if Windows 7 still has this problem but XP would run out of resources when there was plenty of memory available because of the way it managed handles. Just something to try (couldn't hurt).

~jr
PerroneFord wrote on 12/29/2009, 5:28 PM
Maybe I'll give that a whirl, but the system has been sitting idle with nothing running over the holiday weekend. I just fired Vegas up this morning to do some re-renders, and that was the first thing I got.
BudWzr wrote on 12/29/2009, 5:29 PM
This is not possible to be a Vegas error. Vegas doesn't manage memory, it simply requests ram from Windows.
Rob Franks wrote on 12/29/2009, 5:51 PM
"I can manage to send you about 15 seconds worth. But your contact information is unavailable."

I have absolutely no idea what my max is for incoming email but you can try me at neonbob1@mts.net
PerroneFord wrote on 12/29/2009, 6:42 PM
Done.
Rob Franks wrote on 12/29/2009, 7:06 PM
Thanks PF

I'll play around with it a little tomorrow.

Just for the record though I should point out that this is not "AVCHD" but rather h.264 in a mov container. There seems to be quite a bit of confusion over this term "AVCHD".

It's a format that simply happens to use the H.264 codec. It also has a specific set of rules, a certain audio type and a very particular and specific file structure. There are 2 types;

Main profile which is used by Sony and has a max bit rate of about 17M and playback/edits easiest. (although I believe the new Sony pro avchd cam uses the other profile)

High profile which is used in Canon and Panasonic cams. This has a higher bitrate... to a max of 24M... but it's more difficult to edit/playback
PerroneFord wrote on 12/29/2009, 7:16 PM
I get caught in the AVCHD trap. Yes, it's h264. Sorry.
Rob Franks wrote on 12/29/2009, 7:31 PM
Heck...
I decided to play with it tonight... I SHOULD be in bed.

I must say PF... I'm not seeing any memory issues. I've rendered this as m2ts, avc.. I've tripled up on layers and brought the upper layer to 50% level. As seen by the screen shot it's working fine. ( I will say though that this stuff does play back like CRAP on the time line!)



Maybe if you can tell me EXACTLY what your workflow was and what you rendered to I can try that.