So now I have to wait. I was hoping to avoid this but I guess for now, I have no choice. Some interesting things with REDrushes, it has the ability to read each RSX file (the file containing all the color settings which has to be adjusted per clip) of each clip and incorporate those settings in the render output for each respective clip. And the much cooler setting that allows you to refer to one individual RSX file which would in theory save you the time of having to open every single clip and creating a color profile for it. I say in theory because until it works, it will remain a theory. The RSX sourcing only one file for all clips unfortunately has a serious bug that results in each clip being rendered out as an all white frame. Or perhaps, I am being a cynic and in fact it's minutes upon minutes of fabulous RED footage of a polar bear in a snow storm. I can only wonder. So as a result I took the long route and made a profile for each shot. In a way this was good because during location 01, the sun was in and out creating havoc with Roman's life (Roman Baska was the Director of Photography on Lotaluv) not to mention the hell he would have given me for showing ppl the shots without a somewhat decent color correction :P. Below are some observations .

Observation 01:

Pretty decent load on the 8 core I am using, 100% across the board, at least I know I can't run it any faster without a render farm.

Observation 02:

REDrushes for some reason does 6 clips simultaneously. It's an odd number (even though it's even) as at first (because I am so good at numbers) I saw six clips and thought, wow how ingenious... they have one clip assigned to an individual processor. Later after counting the processors on my fingers did I realize I am a retard, and that in fact REDrushes does use the multi-core efficiently by spreading the load. Why 6? Because there are 6 days in a week no doubt... oh wait is there 6?

Observation 03:

Maitreya is a shifty looking pirate. Good thing I kept my distance.