Philippe Lessard
Forum Replies Created
-
Philippe Lessard
February 23, 2011 at 10:43 pm in reply to: after effects cs5 render freeze 12 core 64G RAMTry to render on your internal hardrive, we have this error at work when we try to render on our raid network.
Hope this work.
-
If you plan to animate body with joins, I recommend you this script
Its a combination of IK(inverse kinematic) and puppet tool, it may seem difficult at the first look but if you check at the tutorial you’ll be amaze by the time you”ll be saving and the quality of the animation you will able to achieve! -
Philippe Lessard
February 7, 2011 at 10:07 pm in reply to: After effects CS5 XDCAM EX import problemAE prefer a lossless codec in ingest because it have all the informations for each frame, in each frame.And for vfx/composite/keying job youll prefer a 4:2:2 or a higher codec for the chroma information that it contain.There some software able to reprocess h264 from a canon 5/7D to prores 422 with a true chroma information, but just converting to another lossless codec dont make your footage regain color/chroma information, but AE will not struggled/crash to process/render it.
-
Philippe Lessard
January 27, 2011 at 8:56 pm in reply to: Anyone know what this is? Chromatic aberration maybe?Sorry i forgot to paste this link, it’s what you looking for.
https://www.redgiantsoftware.com/products/all/key-correct/
-
Philippe Lessard
January 27, 2011 at 8:51 pm in reply to: Anyone know what this is? Chromatic aberration maybe?You could just use a matte choker, and/or chroma blur and/or a deartifactor.
Look at this:
https://pilalitos.blogspot.com/2006/10/magic-bullet-deartifacting-vs-chroma.html
-
Thanks for the quick reply,
I forgot to mention that i have already make a boris xlm transfer with sucess, mean the xdcam is reconize. but if we export/render the Final Cut xdcam ex sequence as is, im(2 out of 6 computers) no longer able to reconize the codec? I just verified, and the two components you mentioned are updated! I have see other people having this problem and no one seem to have a solution.Is not a big deal for us to export the sequence in another codec(since is not a good codec to work with in AE), but we wished to use the boris xlm transfer.And still, on 6 computers here, 4 are ok and 2 have this problem.
I’ll continu to troubleshot and if i find a solution i will make a post,
but at this time, CS5(at least my CS5) seem to be the problem.Thanks again
-
Yes we have a multi-port Ethernet card on the server and suppose to have a managed switch with link aggregation but this doesnt seem to work well!?
Thank anyway, I will check the SAN forum.
-
You just have to press cmd(command on mac) while scrubbing the timeline!
-
Philippe Lessard
November 23, 2010 at 3:31 pm in reply to: big problems with black flashes and breakupLike said above, check if the footage is not corrupted, and again make a uncompress(lossless) file out of your h264 before import in AE, then turn off multiprocessing, go to your AE preferences while pressing shift+alt on mac( for pc not sure) and go to the secret menu and set the ram to be purge every frame! And purge everything from the edit menu before starting your render.Render to a uncompress codec like animation.Dont forget to reboot your computer before.
If nothing work, troubleshot for a problematic plugins, i remember having this issue with bcc plugins applied on a masked layer, i haved to precomp the effect, then apply a mask.
Hope this help
-
Yes everything is the same, par, framerate, size square pix progressive..etc
The weird thing is that the weird keyframe just dont exist!!! Is also on a key frame, sometime when you strecht keyframe they end on “between frame” but is not the case here.