Forum Replies Created

Page 47 of 54
  • Peter Litwinowicz

    May 3, 2006 at 8:22 pm in reply to: Silly wabbit…TWIXTOR’S for kids!

    You can read about the Mac OS 10.4.6 fix here: https://www.revisionfx.com/generalfaqsOSX104.htm

    [LAVA] “For rendering, should AE’s frame blending be on or off to allow twixtor to work best? The render times shot through the roof – as it was rendering with fields on gave an estimated time of about 230 hours.”

    Twixtor is replacing AE’s frame blending, so you should have frame blending off. Hope this helps.
    Pete
    https://www.revisionfx.com

  • For our plugins, you can read our FAQ about this: https://www.revisionfx.com/generalfaqsOSX104.htm

    Pete Litwinowicz
    https://www.revisionfx.com

  • Peter Litwinowicz

    April 9, 2006 at 10:28 pm in reply to: Question on MacBook Pro & FCP Universal

    Keep in mind that FCP runnning natively on the Intel boxes does not support an After Effects-compatible plugins. If you rely on any plugins that are of the After Effects-compatible type (like all our RE:Vision Effects plugins), then you can’t use them on Intel machines.

    This is not because we can’t update our plugins to run on Intel Macs… it’s because FCP doesn’t support them.

    If you are worried about the fact that FCP doesn not support AE plugins on Intel platforms (at least not yet), please report your concern here: https://www.apple.com/feedback/finalcutpro.html

    Pete

  • Peter Litwinowicz

    April 7, 2006 at 5:20 pm in reply to: Mac OS 10.4.6 update problem

    For even more complete info on this bug, including the extra fixes that may be needed for FCP, go here :

    https://www.revisionfx.com/generalfaqsOSX104.htm

    Pete Litwinowicz
    https://www.revisionfx.com

  • Peter Litwinowicz

    April 7, 2006 at 5:20 pm in reply to: Mac OS 10.4.6 update problem

    For even more complete info on this bug, including the extra fixes that may be needed for FCP, go here :

    https://www.revisionfx.com/generalfaqsOSX104.htm

    Pete Litwinowicz
    https://www.revisionfx.com

  • Peter Litwinowicz

    March 31, 2006 at 10:14 pm in reply to: Re: Flex from Combustion running in AE?

    You need to buy another set of RE:FLex for AE.

    Pete

  • Peter Litwinowicz

    March 31, 2006 at 10:14 pm in reply to: Re: Flex from Combustion running in AE?

    You need to buy another set of RE:FLex for AE.

    Pete

  • Argh. I said:
    2) Twixtor’s motion blur is meant to *replace* the motion blur found in AE. So you’ll want to turn off AE’s frame blending for the clip/footae that has Twixtor applied to it.
    and I meant
    2) Twixtor’s motion blur is meant to *replace* the motion blur found in AE. So you’ll want to turn off AE’s motion blur for the clip/footae that has Twixtor applied to it.

    Pete

  • First, let me clear up a misconception: The difference between the demo and the full version is the watermark. That’s it.

    Now, as to Twixtor and the calculation time you are seeing
    1) You can set Twixtor’s motion blur compensation to 0.0 if you don’t need it. All that setting does is a) add motion blur if you are speeding footage up and b) remove motion blur if you are slowing footage down. If you are not changing speeds by a large amount, then setting this to 0.0 will be fine (do a comparison test on a couple of frames… if you don’t see enough of a difference, then you don’t need it and it is unnecessarily slowing you down).

    2) Twixtor’s motion blur is meant to *replace* the motion blur found in AE. So you’ll want to turn off AE’s frame blending for the clip/footae that has Twixtor applied to it.

    3) TURN OFF AE’s Frame Blend for the comp/clip with Twixtor applied. Twixtor works independently of AE’s frame blend and having the two on at the same time is unnecessary (and will produce incorrect results).

    4) 55 seconds a frame is not the standard amount of time for Twixtor to process two PAL HDV-sized frames. It should be more on the order of 3 to 10 seconds (depending on whether you use Twixtor’s motion blur compensation, and the amount of movement in the scene). Of course I don’t know if your 55 second timing takes into account all of your other filtering/editing that you are doing on the 2 clips. I just did a test on my 1.5 Ghz G4 single processor laptop and it was taking 6 seconds for 1 1440×1080 frame, with motion vectors set to “Best” and motion compensation set to 0.5 and the interpolation set to “Motion Weighted Blend)”. So for one clip on a 2.5Ghz dual proc G5 I suspect that it should take about 2 or so seconds a frame. This timing isjust for the Twixtor processing… this does not include reading the frames from disk or any other processing you are doing on the clips. ALSO, if you do not have enough memory to hold 2 HDV frames (Twixtor needs to get 2 frames for each frame it makes), plus extra memory for Twixtor, perhaps you are thrashing to disk?

    5) Workflow tip for using Twixtor when interacting: set Twixtor’s Motion Vector setting to None (you’ll get something equivalent to AE’s frame blending) when keyframin the frame number of speed setting. Most definitely set motion blur compensation of Twixtor to 0.0. THen, when going to render, turn the Motion Vector Setting to “Best” and the motion blur compenation back to what you wanted (0 or 0.5 or whatever). ALSO, when interacting, I would turn the interpolation type from “Motion Weighted” to “Blend”. Again, when going to render, set it back to Motion Weighted. Doing these 3 things will improve interactivity immensely (and then setting them to their required setting for rendering will get you the high quality results you want when going to disk).

    [Mylenium] “In addition to this, you should slice your long shot in separate sections and only apply Twixtor to the parts that need retiming – frames that Twixtor doesn’t see won’t be analyzed and render at normal speeds. “

    You don’t really need to slice up your footage. Twixtor only does motion analysis if the speed is not 100% at a particular frame (100% speed is figured out internally, and the skipping of motion estimation step at 100% speed applies whether you are using either the Speed or Frame method of retiming inside of Twixtor).

    Hopefully this answers your questions,
    Pete Litwinowicz
    https://www.revisionfx.com

  • Peter Litwinowicz

    March 10, 2006 at 9:20 pm in reply to: Timewarp does not affect Audio Track?

    By the way, Twixtor allows you to use AE’s time-remapping feature, but use Twixtor’s motion estimation “under the hood”.

    That way you can do both audio and time changes (with motion estimation) at the same time and get more control than you get with the “Pixel Motion” setting… (which is what you would use TimeWarp for right?), but you still get to remap the audio by using the time-remap feature of AE. Of course, you are limited to what AE can do when time-remapping audio.

    You can get a demo version of Twixtor in the “Downloads” section for Twixtor on our website: http:/www.revisionfx.com

    Pete LItwinowicz

Page 47 of 54

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