[Ian Collister]

Thanks both for the help. Filip’s suggestion in Media Encoder has worked a treat. I think it has saved me about a weeks worth of work!

[Ian Collister]

if your project is relatively simple like you say, you probably won’t see much of a difference in CBR and VBR.

Yeah, thinking about it, that makes sense. Again, thanks for the info, greatly appreciated.

[Ian Collister]

‘usually take over a minute to render a minute of content (h.264)’

Thanks Andy, this is the info I was looking for! I had no idea how far off I was.

I have no effects in the comp and the one image is cut to the exact size / depth required. I guess I’m just hitting up against the limits of my RAM / processor etc.

Interestingly, I don’t seem to gain anything from CBR over VBR, the render times are essentially the same.

Thanks for the info!

[Ian Collister]

Oh and I have Media Encoder set up to use 9gb of memory, leaving 3 for the rest of the machine.

[Ian Collister]

Thanks Walter. I found the completely uncompressed setting in the Quicktime options. That looks like it’s giving me a pretty decent render time.

cheers
ian

[Ian Collister]

Ahhh, but only for PC.

Well folks, it’s been a rollercoaster.

cheers
x

[Ian Collister]

Ignore. I thought it was no longer available. My bad.

[Ian Collister]

Hi Walter, sorry for the late reply.

‘or you could convert the expression to keyframes for a direct, dense, point-by-point motion path’

How would I go about doing that? That feels like it would be the answer to my problems…

Thanks for the help!

[Ian Collister]

Anyone?

To simplify, can I create a motion path from a layer that is already being moved / controlled by another layer?

[Ian Collister]

Thanks John, much appreciated!