Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

System requirements

G

Göran Thorén

Active member
Joined
Jan 20, 2009
Messages
37
Reaction score
0
Points
0
Hi all.
I´m a bit confused regarding ram memory requirements when editing RED in FCP.
In the whitepaper minimum is 2Gigs of ram but I´ve seen 8Gigs in other places.
What´s the deal here?
 
I don't edit RED yet but, IMHO as a computer connoisseur and Avid Certified Support Techinican, I'd say that RAM is never too much, get the most you can just limited by your OS and hardware capabilities.
That's quite cheap these days and will give a boost to your computer's overall peformance
 
While FCP will work well with 2-4 GB, the conversion processes based on REDline (REDrushes, Crimson, Clipfinder) will profit considerably from 2 GB per core.
 
Yes, I can understand that but the rason I´m asking is that right now I only have 4Gigs of ram since 2Gigs of ram is not working on my new MacPro. I need to know if that is enough since I won´t be able to get the mother board fixed til tuesday when I´m supposted to deliver the edit.
 
4Gigs will work, but not optimally. When we convert from RED, the memory requirements range from 1G for 1K Express to 2+G for 4K, per conversion stream plus the other overhead. The earlier poster's recommendation of 2G per core is correct.
That said, a lot of our testing is done on a 4 core machine with only 2G, and the VM thrashing is not horrendous unless we try to run the performance monitoring tools as well.:wacko:
 
I was planning on do a native ingest and somehow eport xml to crimson-to REDCine-to dpx.
Will that be possible?
 
Apart from REDCine being pretty buggy – yes.

But why not use Color?
 
The spec is 2.5Gb minimum however it will run with less. You really need to have 4Gb for red based work or preferably more. If i were to build a system Id go for 8Gb these days.
 
So a workflow in my case would be:
Ingest native RED
Edit FCP
Send to Color
Export dpx from Color

Right?
 
Yes. If native RED is too slow in FCP, you can also ingest as ProRes (which will be slow now), edit (fast instead), re-conform with media manager and send native to Color.
 
Thank´s uli!
There is only three clips in the edit so I guess this will work.
I´m a bit confused about reconforming.
Should it matter which format I´m editing in? I mean I would guess that I could use a proxie quicktime since I´m only sending (XML) the sequence to Color. Shouldn´t Color link to the R3D files?
 
Don't use proxies when sending to Color, use a native ingest or ProRes. Color seems to have problems with spanned clips sent as proxies.
 
You must log in or register to reply here.
Back
Top