working in half HD resolution

[wolf]

we are trying to figure out an interactive workflow on a flame 7.6 to deal with HD files in batch.
i am creating 2 framestores, on 1920×1080 and a halfsize proxy.
i open my proxy framestore and import all my HD media with the fill option.
this creates a halfsize acurate HD frame.
Next i go into batch and build my process tree (for the purpose of the test i just used an action node and did an animated transform)

once happy with my work i open my HD fullsize project and import my frames, goto batch and open my previous action setup and apply it to my
clip and render the HD frames.

my problem now is that flame locks and freezes when i try to apply the action setup that i created with the halfsize proxys to my Full HD 1920×1080 frames.

am i missing something here or is there a setting i overlooked ?

any help on this matter is welcome and appreciated

what workflows did you guys come up with dealing with HD and 2k on your flames ?

w

[Tom]

actually i don´t understand why this happens. i did something similar for a 4k imax project but in a little different order with inferno 4.1 or so (several years ago)

first i created a 4k partition. (didn´t even think about proxies)
imported all my clips

the i created a 2k and a 1k partition (all with the same aspect ratios as the 4k partition. this is important) i created 2 partitions because i wanted to work in 2k but i was too impatient to wait for renderings so i went down to 1k.

i saved my clips with fill from the 4k to the 2 and 1k partitions (to keep their original names)

built the batch setups in 1k or 2k. tested them, showed them to the client and finalized them in 4k. i opened the same setup in 4k. Loading of clips – no problem because of the same names and the scaling of thr setups went very well (because they automatically adjust their settings like in 1K a keyoffset of 1 becomes 4 (or so) in 4k) only sparks had to be readjusted by hand.

it was a big batch. and it crashed after 15min(instead of rendering for 126 hours). but after breaking the batch up into smaller parts everything went fine.

so, actually you shouldn´t have any problems because i think most people did it like that. perhaps you should check your memory settings like the memory keyword.

hope it helps a little
tom

[wolf]

hey tom

it was great to confirm some thoughts of ours.
the above workflow was inspired by kuban.
i did another test this morning with importing the HD footage into my batch action and for a minute or two it seems my machine is crashed but then it returns to normal.

how is the memory keyword to be understood ?

this is straight from the default cfg file:

# Syntax: Memory
#
Memory 50

how much memory do you allocate ?
does 50 mean MB or ?

thanks

w

[wolf]

oh i forgot to mention:

this specific flame i has 2gb of ram installed.

w

[Tom]

hi wolf,

2GB is ok. 2,5 or 3 is the maximum needed as ffi only uses up to 2GB of RAM.

I never really understood the memory keyword. what i did is experimenting with the values. like 150 or more. i think somewhere here are several threads regarding the memory keyword but they are all not too clear for me 😉

tom

[wolf]

tom

i am glad i am not the only one not clear about the memory keyword either.
thanks for your advice.

wolf

[Author]

Posts