Forum Replies Created

Page 146 of 152
  • Pierre Jasmin

    December 16, 2005 at 11:58 pm in reply to: creating a matte for Twixtor

    I meant reimport in FCP

    Pierre

  • Pierre Jasmin

    December 16, 2005 at 11:58 pm in reply to: creating a matte for Twixtor

    I meant reimport in FCP

    Pierre

  • Pierre Jasmin

    December 16, 2005 at 11:57 pm in reply to: creating a matte for Twixtor

    I don’t think Twixtor runs yet in Motion (supporting AE plugins does not seem a priority over there). I am saying maybe if you have the Apple Production Studio that comes with a copy of Motion then maybe you could use that to make a better matte and render it and import it in Motion.

    It would be cool if Apple fixed and expanded their AE plugin support 🙂 – Send bugs for plugins like Twixtor not working well in Motion )others have problems with FCP) to:

    https://www.apple.com/feedback/motion.html
    https://www.apple.com/feedback/finalcutpro.html

    Pierre

  • Pierre Jasmin

    December 16, 2005 at 11:57 pm in reply to: creating a matte for Twixtor

    I don’t think Twixtor runs yet in Motion (supporting AE plugins does not seem a priority over there). I am saying maybe if you have the Apple Production Studio that comes with a copy of Motion then maybe you could use that to make a better matte and render it and import it in Motion.

    It would be cool if Apple fixed and expanded their AE plugin support 🙂 – Send bugs for plugins like Twixtor not working well in Motion )others have problems with FCP) to:

    https://www.apple.com/feedback/motion.html
    https://www.apple.com/feedback/finalcutpro.html

    Pierre

  • Pierre Jasmin

    December 16, 2005 at 6:05 pm in reply to: creating a matte for Twixtor

    You don’t use a matte as an ALT source. The Foreground-Background segmentation matte is only an option in Twixtor PRO. The ALT source is your friend to enhance the image (when you have dark or low-contrast imagery (eg more contrast without clipping) or to revert to use the original source if what you are retiming receive a lot of treatment and as a result has not much details left.

    Unfortunately Final Cut Pro does not have roto tools other then the simple garbage matte tool, “masking” tools one uses when process like ‘keying’ are not sufficient. Products like Combustion or Motion or stand-alones like Silhouette Roto have better toolset for the purpose of making such a matte. Of course when the camera moves, building such matte can be a lot of hand work.

    Pierre

  • Pierre Jasmin

    December 16, 2005 at 6:05 pm in reply to: creating a matte for Twixtor

    You don’t use a matte as an ALT source. The Foreground-Background segmentation matte is only an option in Twixtor PRO. The ALT source is your friend to enhance the image (when you have dark or low-contrast imagery (eg more contrast without clipping) or to revert to use the original source if what you are retiming receive a lot of treatment and as a result has not much details left.

    Unfortunately Final Cut Pro does not have roto tools other then the simple garbage matte tool, “masking” tools one uses when process like ‘keying’ are not sufficient. Products like Combustion or Motion or stand-alones like Silhouette Roto have better toolset for the purpose of making such a matte. Of course when the camera moves, building such matte can be a lot of hand work.

    Pierre

  • Pierre Jasmin

    December 15, 2005 at 1:03 am in reply to: Twixtor and slow-motion!

    There is substantially less of that with Twixtor 4.5 then previous versions on cluttered multiple motion scenes, but it can still happen, it is typically caused by large regions that are visible in one frame and not the other, in which case the documentation goes over in detail about how to try to fix that with Twixtor Pro and a bit of manual work. The amount of “PRO” features varies per app we support currently, so I won’t be more specific.

    If you are speeding up, you might consider Nearest Frame mode to reduce that effect

    Pierre
    RE:Vision Effects

  • Pierre Jasmin

    December 15, 2005 at 1:03 am in reply to: Twixtor and slow-motion!

    There is substantially less of that with Twixtor 4.5 then previous versions on cluttered multiple motion scenes, but it can still happen, it is typically caused by large regions that are visible in one frame and not the other, in which case the documentation goes over in detail about how to try to fix that with Twixtor Pro and a bit of manual work. The amount of “PRO” features varies per app we support currently, so I won’t be more specific.

    If you are speeding up, you might consider Nearest Frame mode to reduce that effect

    Pierre
    RE:Vision Effects

  • Pierre Jasmin

    December 13, 2005 at 6:28 pm in reply to: motion morph in Combustion4

    Good to hear. Although not necessarily your problem, note that to have Hold Edges checked and Auto Align as well can cause some swimming as one setup tells RE:Flex to “go there” and the other to “come back”… the new update has a different behavior for Smart Blend (maintains a full alpha at the frame edges through the mix — blend 0 to 100% — if the two sources have full on alpha to start) and so is preferable probably then Hold Edges when doing Motion Morph.

    Also to do both 4×4 and Smoothest Mip Map might be overdone and in the end uses incredible amounts of memory if you are not at least in Less Memory mode (vs Faster AA Method). 4×4 Anti-Aliasing + AA Method to Faster is probably a good way to kill your favorite app memory management (as it will then require 16X more memory about).

    Pierre

  • Pierre Jasmin

    December 13, 2005 at 6:28 pm in reply to: motion morph in Combustion4

    Good to hear. Although not necessarily your problem, note that to have Hold Edges checked and Auto Align as well can cause some swimming as one setup tells RE:Flex to “go there” and the other to “come back”… the new update has a different behavior for Smart Blend (maintains a full alpha at the frame edges through the mix — blend 0 to 100% — if the two sources have full on alpha to start) and so is preferable probably then Hold Edges when doing Motion Morph.

    Also to do both 4×4 and Smoothest Mip Map might be overdone and in the end uses incredible amounts of memory if you are not at least in Less Memory mode (vs Faster AA Method). 4×4 Anti-Aliasing + AA Method to Faster is probably a good way to kill your favorite app memory management (as it will then require 16X more memory about).

    Pierre

Page 146 of 152

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy