v6.x RE:Vision Effects ReelSmart Motion Blur Pro

Pro license works with After Effects, Baselight, Final Cut Pro, Flame, Smoke, Fusion Studio, HitFilm, Media Composer, Motion, Natron, Nucoda, Nuke, Premiere Pro, Scratch, and Silhouette. Pro license also works with the regular product of any supported host.

Adobe Hosts

• After Effects CS6, CC, CC 2014, CC 2015, CC 2017, CC 2018, CC 2019, 2020, 2021, 2022-24
• Premiere Pro CS6, CC, CC 2014, CC 2015, CC 2017, CC 2018, CC 2019, 2020, 2021, 2022-24
• ​Note: If you’re using AE CC 2015, you will need to use 2015.0.1 (13.5.1) or later.

Apple Hosts

• Final Cut Pro 10.1.4 (and up)
• Motion 5.1.2 (and up)

Avid Hosts

• Media Composer 6.0, Symphony 6.0, Newscutter 10.0 (and up)

OFX Hosts

• Autodesk (All versions)
• Baselight 5.2.11675 (and up)
• Catalyst Edit 2015.1.0.104 (and up)
• Diamant and Dustbuster+12.0 (and up)
• Flame 2019.2 (and up)
• Fusion Studio 5.2 (and up)
• Resolve Studio 11 (and up).
• HitFilm 3.0.0.0576 (and up)
• Natron 1 (and up)
• Nucoda 2014 (and up)
• Nuke 5.1 or Indie 12.2 (and up),
• Scratch 4 (and up)
• Silhouette 6.1.3 (and up)
• Vegas Pro 64-bit only, v10.0e (and up)

System Requirements

The same OS and hardware requirements for the version of the Host that you are using.

GPU Requirements

Below is information you will need to know for our products that support GPU acceleration.

• All plug-ins that support GPU acceleration also work in CPU-only mode if your GPU does not work with our plug-ins.
• GPU with 1Gb memory officially supported. GPUs with 500Mb can work for our plug-ins but are not officially supported.
• Driver for GPU must support OpenCL 1.1.
• Intel on-chip GPUs ( HD Graphics 4000 or later) are supported when OpenCL 1.1 drivers for them are available.
• Windows 7, 8 or 10 or later, 64-bit for GPU support. Vista is still supported for CPU mode.
• Mac OS.  Mac OS 10.7 is required for GPU support, but we recommend Mac OS 10.8 or later. Intel HD Graphics requires Mac OS 10.9 or later
• Important note for Macintosh users and nVidia cards: Make sure to update to the latest nVidia drivers and not rely solely on the drivers that come with the Mac OS.  http://www.nvidia.com/object/mac-driver-archive.html

Adobe After Effects GPU Requirements

First, we support GPU rendering in all modes of After Effects, including RAM preview, with AE’s multiprocessing (multiple frames at once), turned on, Render Queue rendering, aerender, and dynamic links within Premiere Pro and AME.

It is important to note that our GPU accelerated modes of our plug-ins can provide you with different results than on the CPU.  As such, it is not wise to mix CPU-generated images with GPU-generated images.

If a GPU is not supported, or we run out of GPU memory to run on, our plug-ins will return a green frame to let you know.  So if you switch the Use GPU menu to ON and you see a green frame immediately, you know that you do not have a supported GPU. We do not fallback to CPU rendering in the case where there is an error on the GPU during a rendering of a sequence, because then you might get CPU and GPU calculated images intermingled and may not understand why your sequences are not looking proper from frame to frame.

When working completely on a single machine, you can simply pick GPU mode or CPU mode as you see fit… and render to RAM, to disk, etc. and all the frames will be rendered using the same mode. There are cases where you might send jobs out to machines on a render farm  and the set of machine(s) may be a mixture of GPU-supported and non-supported GPU (or no GPU); or conversely, you may know that all the machines that will be rendered on are all GPU-supported, or all are non GPU-supported.  As such, our plug-ins in After Effects that support GPU acceleration will present you with a “Use GPU” menu with 3 options:

• OFF – This option causes the plug-in to run on the CPU.  This mode should be used if you do not have a GPU that our plug-ins support.  In addition, the OFF setting might be advantageous if you will be sending a job to a render farm, and some machines have GPU support for our plug-ins, and others don’t.  By selection OFF (CPU mode) you can be assured that all frames across the render farm will run in the same mode (all CPU) and all frames will be consistently rendered.
• ON – This option forces the plug-in to run on the GPU.  If no GPU is present, or is not supported, a green frame is rendered.  If working solely on one machine, you can try the ON setting.  If you get a green frame, then your GPU is either not supported, or there is not enough GPU memory.  Another use for this setting can be to determine which machines on a render farm do not have GPU support by looking to see which machines return green frames.
• ON if GPU supported, CPU otherwise – This mode is useful if your interactive session has a GPU, and you know that all your render farm machines are either all a) GPU supported or b) none are  GPU supported.  In this case, you know that all machines on the render farm will render all frames consistently on CPU, or GPU.  In this situation, with this setting, you don’t have to remember to switch the Use GPU setting from ON to OFF before sending to the render farm.  Note: we can still produce a green frame if we discover a supported GPU but run out of GPU memory, or other such error as the rendering progresses.

Adobe Premiere Pro GPU Requirements

First, Premiere Pro does not need to support the GPU, even though our plug-ins use OpenCL for acceleration.  Nor do you need to have the Mercury engine running in OpenCL or CUDA mode to use our plug-ins in GPU mode. It is important to note that our GPU accelerated modes of our plug-ins can provide you with different results than on the CPU.  As such, it is not wise to mix CPU-generated images with GPU-generated images.

Users of our plug-ins with GPU acceleration will see utilization of two or more GPUs at the same time, provided they are the fastest GPU on the machine, and are of the exact same type. If a GPU is not supported, or we run out of GPU memory to run on, our plug-ins will return a green frame to let you know.  So if you switch the Use GPU menu to ON and you see a green frame immediately, you know that you do not have a supported GPU. We do not fallback to CPU rendering in the case where there is an error on the GPU during a rendering of a sequence, because then you might get CPU and GPU calculated images intermingled and may not understand why your sequences are not looking proper from frame to frame.  So if you see a green frame, that probably means that we’ve run out of GPU resource with which to render the sequence.

Newer versions of our products: Our newer plug-ins for Premiere Pro that support GPU acceleration will have group of GPU options labeled Activate GPU. You’ll see that GPU acceleration is OFF by default. Also note by default that some of our plug-ins will try to conserve GPU memory.  Our plug-ins conserve GPU memory by only allowing Premiere Pro to render a limited amount of images at the same time (this is limited to the number of GPUs present). If you find this actually slows down rendering, or causes a hang, you should try unchecking the “Less GPU Mem” setting before turning the GPU rendering ON.

Older versions of our products: Our plug-ins for Premiere Pro that support GPU acceleration will present you with a “Use GPU” menu with 2 options:

OFF This option causes the plug-in to run on the CPU.  This mode should be used if you do not have a GPU that our plug-ins support, or see a green frame in the middle of a rendered sequence, because this means that our GPU rendering fails somewhere in the middle of a sequence.
ON This option forces the plug-in to run on the GPU.

Other Host GPU Requirements

Version 6.5.2 | November 2, 2021 (Flame)

• Installer needed for Mac OS 12 (Monterey)
• Updates REVisionActivate 21.12.6 (Windows)
• Updated support in Nucoda 2021 and Quantel RIO 4.5.8

Version 6.2b | November 9, 2021 (Avid)

• Installer needed for Mac OS 12 (Monterey)
• Updates REVisionActivate 21.12.6

Version 6.5.2 | November 2, 2021 (OFX)

• Installer needed for Mac OS 12 (Monterey)
• Updates REVisionActivate 21.12.6 (Windows)
• Updated support in Nucoda 2021 and Quantel RIO 4.5.8

Version 6.4a | October 27, 2021 (Adobe)

• Installer needed for Mac OS 12 (Monterey)

Version 6.2.1e | October 26, 2021 (FCP)

• Installer fix needed for Apple MacOs 12 (Monterey)

Version 6.2.1e | October 26, 2021 (FCP)

• Installer fix needed for Apple MacOs 12 (Monterey)

Version 6.4.0 | September 16, 2021 (OFX)

• Adds native Apple M1 Mac support.
• Fixes issue loading in latest Fusion Studio and Resolve 17.3.
• Fixes DMG installer issue in Mac M1 and Big Sur 11.5.2.
• Fixes Installer UI issue in Linux HDPI screens.
• Fixes Tab Group labels (they are back yeah! but shorter)

Version 6.2.1b (M1 beta) | May 29, 2021 (FCP)

• Fixes potential permission issues with the installer

Version 6.2.1 (M1 beta) | May 21, 2021 (FCP)

• There could be license activation issue on M1 machines

Version 6.2 (M1 beta) | May 7, 2021 (FCP)

• Beta for M1 support.
• Known issue: plugins using image parameters like RSMB Pro and RSMB +Vectors are broken in FXPlug4 which is required for M1 support for FCP and Motion. Bug has been filed at Apple.
• All versions: Fixes issue with 16-bit float when running on GPU

Version 6.2.1 for After Effects | December 27, 2019

• Removes license info from aerender terminal window

Version 6.3.1 for Fusion Studio | November 4, 2019

• RSMB + Vectors could freeze when changing values

Version 6.2 | October 9, 2019

• Mac OSX – Catalina Ready
• Intel Embedded Graphics support fix
• On some computers, initialization could return an embedded graphics card instead of a discrete card
• Import Premiere project in AE with our plugins, there could be a parameter offset

Version 6.2b for OFX | August 21, 2019

• Version needed for Mac Mojave OSX and over

Version 6.2a for OFX | July 18, 2019

• Fixes a small glitch in Linux installer

Version 6.2 for OFX | June 26, 2019

• Adds native Fusion plug-in support for Fusion Studio 16 and Resolve Studio 16

Version 6.2 for OFX| May 4, 2019

• Adds support for Baselight

Version 6.1.1 | January 14, 2019

• Fixes a bug of crashing when activating or deactivating the license from within a plug-in.

Version 6.1 | December 3, 2018

• Implements new RE:Vision Effects licensing scheme.

Version 6.0.2 | October 19, 2018

• Fixes a crashing bug when using GPU-acceleration on machines with more than one Nvidia GPU.

Version 6.0.1 | April 30, 2018

• Fixes a bug where blank, incomplete or “random” images were produced.

Version 6.0 | April 19, 2018

• Initial v6 release
• Adds 360 video support
• New option in Pro version that uses the alpha channel to help to track of dark images with mattes. This is especially useful for CG, masked and/or keyed material.
• New option for linear footage that provides better tracking
• Premiere Pro: adds support for floating point color

What’s new in Version 5.1?

• Version needed to run in AE CC 2015 if you use splines to help guide RSMB Pro.
• Fixes some bugs in RSMB Pro within After Effects CC 2014 where the render cache was not properly re-rendered when masks were modified that the plug-in was using.
• Adds support for RVL_NOGUI_LIC and RVL_QUIT_LIC_FAIL environment variables during render-only use in After Effects.

What’s new in version 5.0.3? Posted June 5, 2014:

• Fixes a bug where RMSB Pro when using tracking points and no image tracking did not work in GPU acceleration mode
• Fixes a bug where negative alpha could be erroneously created when removing motion blur (bug was in GPU mode only)
• Fixes a bug where GPU mode did not work properly in demo mode on some GPUs.

What’s new in version 5.0.2? Posted May 29, 2014:

• Fixes a bug where RMSB Pro when using tracking points and no image tracking did not work in GPU acceleration mode
• Fixes a bug where negative alpha could be erroneously created when removing motion blur (bug was in GPU mode only)