Peter Litwinowicz
Forum Replies Created
-
The FxPlugs live in /Library/Plug-ins/FxPlug . Delete the Twixtor folder you find there.
Note that Spotlight doesn’t search the /Library directory by default, which is why your search did not find it.
CHeers,
pete Litwinowicz -
>But do I have to go through the footage all over again replacing the keyframes?
Short answer: Yes. Sorry.
Pete
-
>But do I have to go through the footage all over again replacing the keyframes?
Short answer: Yes. Sorry.
Pete
-
Simple answer (and you’ve already read it in the manual): you cannot get Twixtored output when the display is set to Source. As the manual says “Source” setting displays “the unprocessed output”.
However, to answer your question: you want to set the speed to go to only 300% starting at a particular frame (for example, when the “sun comes up”). if you only set one keyframe of 300% this will tell AE to set the value at 300% for all times. So the WHOLE clip gets sped up.
So what to do? Go to the first frame of the sequence and set a Speed keyframe of 100%. Then go to the frame before you want to speed up and set another keyframe of 100%, then go the frame where you want it to start going 300% and set a keyframe of 300%. This will keep the speed at 100% for all the frames before the one where you want to speed it up (so it will play a the normal speed until it hits the 300% keyframe).
Hope this helps.
Pete LItwinowicz
RE:Vision Effects. -
Simple answer (and you’ve already read it in the manual): you cannot get Twixtored output when the display is set to Source. As the manual says “Source” setting displays “the unprocessed output”.
However, to answer your question: you want to set the speed to go to only 300% starting at a particular frame (for example, when the “sun comes up”). if you only set one keyframe of 300% this will tell AE to set the value at 300% for all times. So the WHOLE clip gets sped up.
So what to do? Go to the first frame of the sequence and set a Speed keyframe of 100%. Then go to the frame before you want to speed up and set another keyframe of 100%, then go the frame where you want it to start going 300% and set a keyframe of 300%. This will keep the speed at 100% for all the frames before the one where you want to speed it up (so it will play a the normal speed until it hits the 300% keyframe).
Hope this helps.
Pete LItwinowicz
RE:Vision Effects. -
First, make sure you are running FCP 5.1 or later. FCP didn’t add support for AE plugins on INtel Mac until version 5.1 . If you have version 5, you can update to version 5.1 by simply running Apple’s Software Update in the System Preferences.
Second: try accessing the plugin by using the menu item Effects->Video Filters->RE:Vision Plug-ins->Twixtor 4.5.
Hopefully that will get you going.
Pete Litwinowicz
-
First, make sure you are running FCP 5.1 or later. FCP didn’t add support for AE plugins on INtel Mac until version 5.1 . If you have version 5, you can update to version 5.1 by simply running Apple’s Software Update in the System Preferences.
Second: try accessing the plugin by using the menu item Effects->Video Filters->RE:Vision Plug-ins->Twixtor 4.5.
Hopefully that will get you going.
Pete Litwinowicz
-
yeah, are you seeing this on your background layer? I presume this is because you need a matte with antialiased edges, which works great for the foreground. So when the matte is used to cull out the foreground when calculated the background layer you still see an edge. Does this sound right?
Two answers: you can use InvMatteShrink (see manual), which grows the foreground matte by the specifiied amount (in pixels) to allow for edges that need an antialised-edge matte for the foreground. This way you can probably remove much of this extra line you are seeing.
As Pierre said, if that doesn’t work, send us the project (I presume it’s for the footage you sent the other day?).
Also, we had a major website/email server failure yesterday and are still recovering… which is why we have been slow in responding.
Pete
-
yeah, are you seeing this on your background layer? I presume this is because you need a matte with antialiased edges, which works great for the foreground. So when the matte is used to cull out the foreground when calculated the background layer you still see an edge. Does this sound right?
Two answers: you can use InvMatteShrink (see manual), which grows the foreground matte by the specifiied amount (in pixels) to allow for edges that need an antialised-edge matte for the foreground. This way you can probably remove much of this extra line you are seeing.
As Pierre said, if that doesn’t work, send us the project (I presume it’s for the footage you sent the other day?).
Also, we had a major website/email server failure yesterday and are still recovering… which is why we have been slow in responding.
Pete
-
We have no extra tutorials at this time, except to look at the pre-made projects I suggested you look at (take a look at those, they might be very helpful, even if they don’t show you step by step).
And, sorry to say, some shots are just very difficult. With arms an legs crossing the body and each other, this can be very difficult for Twixtor (and any retiming solution), even with mattes and splines. THe sample projects I pointed you to have an example of a person with a couple arms crossing each other and a torso. And even with multiple layers of mattes, it still needs quite a few splines to guide the tracking.
Yes, it can take a lot of time to do this if you don’t roto for your everyday job. But the point is that it is often possible with Twixtor where other retiming products don’t offer these options to guide the tracking.
Cheers,
Pete Litwinowicz