Forum Replies Created
-
Posts
-
Someone else can probably give a way more technical explanation than this but without knowing your footage I’m assuming it’s because there are similiar color values on your FG and when you are sampling the areas you want to keep- Primatte thinks that you are going to also want to keep those same values that are part of the green screen. You might have some green spill on the FG or shes wearing something with the same color.
Judging by the hardness of the key in her hair I’d say your hitting your key quite hard which can be good for a core matte but sometimes this can mean your hard key with Primatte will struggle on those pixels, so you’ll need a second softer key to fill in that area, or a second core matte with a keyer that works differently to Primatte. Keying’s never a one hit solution so don’t worry too much. 😀
Looks like you’ve answered your own question for at least part of it.
Using a retime is the easiest node in my view. I think it gives a clearer view of what your doing as opposed to a time offset or ofsetting it in your read node- especially if you’re handing off your script.
You should just be able to throw a retime in at the start of your tree if you want your 2352 start frame to work at 001. If you are working with a global time frame starting at 1, it will render out at 0001 anyway using your padding %04d. There are two threads dealing with that here:
http://www.fxguide.com/forums/showthread.php?t=7887&highlight=frame+range
http://www.fxguide.com/forums/showthread.php?t=6709&highlight=frame+rangeI’m not sure why you would need to work on something before and after a retime? It would be easier to work in one frame range to my thinking. Is it an element or something?
Hope this helped a little bit.
Cheers
Depending on what you’re doing using the curve editor is pretty slow.
You can simply just right click on any point in your roto on a keyframed frame and hit delete key- all.
If you just hit delete it will delete that bezier point instead.
😀