[Paul Golden]

It’s true that FCP will do that, but I believe that it will transcode everything in your Event to HQ media, not just the footage in your project, so you will still end up with lots of “extra” HQ footage. Am I wrong?

[Paul Golden]

I’m with you Loren. Apple seems to be taking the tack that “disk space is cheap”, so they’ve sort of assumed that the only reason to use Proxy footage is for performance purposes instead of disk space storage. If you shoot hours and hours of footage, it seems silly to transcode all of it unless space is of no consequence to you.

[Paul Golden]

Hi James
I’ve never had a halfway decent result using the H264 media to cut with, and despite Apple’s contention that you can edit with it, there’s a reason why they don’t consider it “optimized”. I find H264 sluggish and problematic on even the fastest machines.

My preference is to cut with Proxy out in the field with my laptop and then re-conform with 422 when I get back and have more space. But I still don’t see the need to fill my portable drives with 422 material I won’t need, when I can live with Proxy and then re-ingest the edit’s footage in 422 to render final and not hours and hours of out-take “chaff”.

So I’m still looking for a way to auto-conform from the original source media like old skool….

[Paul Golden]

Hi Rohit

Updated to the latest drivers, restarted, and Resolve still quits on making a new project. All other menu functions work, but can’t seem to proceed beyond opening the main screen. I uploaded the crash log and my system log to Davinci.

Thanks Paul

[Paul Golden]

Thanks Rohit,

I am on 10.6.8, so I’ll download the new NVIDIA drivers and let you know…

Paul

[Paul Golden]

I’ve had the same experience. I’ve tried installing it on my underpowered Mac Pro 2,1 with a 4870 card, 24 gbs of RAM. It definitely wouldn’t work (i wasn’t surprised.) I figured it was the graphics card.

But then I installed it on my MBP 17″ with dual Nvidia cards and 8 gbs of RAM and the same crash when trying to create a project happens. I even set the energy management to Faster (instead of More Battery Life) as instructed by Davinci. The MBP meets Davinci’s specs, so I’m not sure what’s happening..

[Paul Golden]

Having the same problem here as well. Dropped a 1gb file into a droplet assigned to my computer’s 8 core cluster and nada! Just waiting…Have stopped and started Qmaster services. No luck

Apple…. help?

[Paul Golden]

Thanks Todd…

I’ve managed to track down the layer that’s causing the issue and turned it off (it was another artist’s comp so I wasn’t sure what its function was, but it doesn’t affect it too much visually).

This comp size is 1500 x 1500 (to be used as a sub element later) so I’m trying now to figure out why that layer is giving me a 30K wide element. I agree that’s ridiculously large.

One question: does AE do math on stuff outside the rendered area (1500 x 1500)? The comp would render at everything other render size than Full image res (that’s the way I figured out the rogue layer). If the comp renders at Half res, does AE not bother calculating outside of the visible area or is it essentially 15K across within the memory of what I’m doing?

And how does 64bit change this equation from CS4 in this circumstance?

Paul

[Paul Golden]

Hi Todd…

I hate to break it to you, but I’m on CS5 and getting the dreaded “After Effects error: invalid image buffer size (1605×30067)”

I’m on a Mac 8 core with 24gb of ram. I’ve enable multiprocessor rendering. In an image sequence, my timeline craps out at frame 471 every time. I’ve tried this file on another Mac running CS5 as well as a PC running it.

I can’t seem to locate anything thats causing it….

Help!