At Boris FX, we’re here to help. Our customer service team has compiled a list of quick links and FAQs to allow for hassle-free activation and product guidance.


  • Soundbite FAQs
  • What are the advantages of Soundbite over products that create a transcript?

    Boris Soundbite does not create a transcript. The process of making audio searchable in Soundbite is referred to as Indexing. The indexing process generates a record of the sounds in the audio – known as phonemes – and stores this information on your computer. Rather than making decisions about the words that are spoken at the time the audio is indexed – resulting in a transcript – Soundbite locates areas in the audio that sound exactly like or similar to the words or phrase being searched. There are a number of advantages to Soundbite when compared to products that create a transcript:

    Indexing Speed. Soundbite indexes media files much faster than real time, rendering a one hour file searchable in about a minute. This enables Final Cut Pro users to begin searching their daily news, interview and/or scene footage very quickly.

    Dictionary Independence. Typical speech to text systems can only recognize words found in their specific dictionaries. Phonetic indexing is not dependent on a fixed dictionary, so Soundbite users aren’t dependent on updates to be able to find slang, proper names and other topical keywords when they need to.

    Spelling Errors. Proper names are particularly useful query terms but also particularly difficult for speech to text solutions, not only because they may not occur in the dictionary, but also because they often have multiple spellings. With phonetic searching, exact spelling is not required. If it’s spelled like it sounds, Soundbite will find it.

    User-determined Threshold. If a particular word or phrase is not spoken clearly, or the audio quality is poor, speech to text solutions will likely not recognize the words correctly. Soundbite’s lets the user set a tolerance threshold: A high threshold only returns results which precisely match the search terms, while a lower threshold allows results which have lesser audio quality or broader variations in pronunciation. This capability is unique to Soundbite and simply not available in other solutions.

    What content can Soundbite search?

    Soundbite searches most common file formats that can be played on your system using QuickTime. 

    Soundbite searches all clips, sub-clips and sequences that are part of specified FCP projects or “watched” folders. Soundbite will periodically check for new media files and automatically make them searchable as well.

    How is Soundbite integrated with Final Cut Pro v7.x or v6.0.2?

    Soundbite understands how to read the information contained in your FCP project. It not only can discover and locate the media files associated with a project, Soundbite also reads all metadata associated with those assets. This metadata can be searched in conjunction with the dialogue.

    Once you find clips that you’d like to add to your project, Soundbite will export the media file reference into your FCP project, along with markers named for the word or phrase that was searched.

    How is Soundbite integrated with Final Cut Pro X and Adobe Premiere Pro?

    Soundbite v1.1 includes XML export options for Adobe Premiere Pro CS5.5 Mac and Apple Final Cut Pro X.

  • Soundbite Loads but is Not Functional
  • Subject:  Soundbite loads but the functionality has stopped.

    Issue:  User is unable to Open files, Index folders, or Delete already Indexed folders.

    Cause:  This would be due to a corruption of the Soundbite protocols, which will need to be reset.

    Steps to work around this issue:

    1. Close Soundbite, and go into this directory –Macintosh HD :: Users :: [ Current User/Home Folder ] :: Library* :: Preferences

    2. Locate a file called “com.borisfx.Boris-Soundbite.plist” and delete it.g3. Afterwards, go into this directory –Macintosh HD :: Library :: Application Support :: Soundbite

    4. Inside the Boris Soundbite folder, send the ‘Default’ files and the ‘Machine’ file to the Trash – Keep this folder open.b

    5. Re-launch Boris Soundbite from the Applications directory.

    *If the problem persists, Quit Soundbite and, in the ‘Soundbite’ folder, remove the ‘index’ folder.


  • Title 3D Crashing
  • Subject:  Title 3D Crashing

    Issue:  Title 3D crashing Final Cut Pro when applying, launching or rendering.

    Steps to work around the issue:

    1. Quit Final Cut Pro and go to this location in the Finder –Macintosh HD :: Users :: [ Current User/Home ] :: Library** :: Preferences

    2. Inside this location, delete the file that reads: “com.borisfx.Title 3D”

    3. Inside the same Preferences folder, enter the Final Cut Pro User Data directory and delete these two files: ʻFinal Cut Pro Obj Cacheʼ & ʻFinal Cut Pro Prof Cacheʼ After this, re-launch Final Cut Pro and Title 3D should be operational again.

    *Note: this folder is hidden by default in later versions of OSX.  In order to access this folder, you will need to enable view of hidden objects in OSX, or load it from the ‘Go’ menu.

  • BCC Suddenly Experiences Problems on Windows
  • Subject: BCC Suddenly Having Problems On Windows

    Issue: My BCC Is Suddenly Experiencing Problems On My Windows System; Reinstalling Does Not Help

    Cause: Recent Changes, Manual Or Automated, Have Caused A Corruption in BCCʼs Behavioral Protocols

    How to Get Around the Issue:

    1. Close your Host NLE/Compositor program and go into this directory –
    C:\Users\[Current User]\AppData*\Local\BorisFX

    2. Inside here, you will see a folder for Boris Continuum Complete — send this folder to the Recycle Bin and re-launch your NLE/Compositor program. The problem should not come up with any new effects.

    *Note:  The AppData folder mentioned above is hidden by Default in most installations of Windows 7 and Window 8 (even the Win 7/8 Professional version).  If you do not see this folder, you can go into the address field above and add “\AppData” and hit Enter – this will give you access to this hidden folder.

  • One Frame Watermarks on BCC AVX 9 on Mac
  • Subject: One Frame Watermarks on BCC AVX 9 on Mac

    Issue: When I render my BCC AVX 9 effects, each effect has a watermark on the first frame.  This isnʼt visible before render, and the BCC AVX 9 software is fully licensed.

    Cause: Problematic Build

    How to Get Around the Issue:

    This is a known problem with one particular Installer build that was sent to multiple channels.  If you are experiencing this problem, Quit Avid, Uninstall BCC AVX 9 and download this file: https://xfer.borisfx.com/BCCAVX902Mac64Bit.dmg

    Once you have downloaded this alternate installer, Reinstall BCC AVX 9 using this installer and re-render your effects; the BCC AVX Watermark will no longer appear on your existing clips, nor will it appear on any further ones.

    Note: this will even work with timelines carried over from network systems.

  • Issue Launching Boris RED in Media 100
  • Subject: Unable to Launch Boris RED in Media 100

    Issue:  When I apply Boris RED as a filter, Comp or Title, I receive an error that the Boris Graffiti or Boris FX file is missing.


    Cause:  The files for Boris RED need to be in a specific location in relation to Media 100.

    Steps to work around the issue:

    1. Quit Media 100 and go into the Media 100 Folder folder in the Applications directory.

    2. Check to confirm that Boris RED is located in all three of these folders –
    Macintosh HD :: Applications :: Media 100 Folder :: Filters
    Macintosh HD :: Applications :: Media 100 Folder :: Graphics
    Macintosh HD :: Applications :: Media 100 Folder :: Transitions :: DVEʼs

    3. If Boris RED is missing from any of these directories, manually Delete the Media 100 Folder by sending it to the Trash.

    4. As an Admin-level User account, run the Disk Utility and reinstall Media 100.

    If Boris RED is located inside these three folders, then conduct a search on your system to locate the Media 100 Suite application itself.If it is located anywhere else, such as the Desktop, you will need to place the Media 100 Suite application itself back into the Media 100 Folder in the Applications.Once the Media 100 Suite application is back in the Media 100 Folder, with Boris RED in the folders above, Boris RED will operate inside Media 100 once again.

  • Media 100 Error Codes -39 and -2048
  • Subject: M100 Errors -39 and -2048

    Issue: When Working In Media 100, Suddenly I Am Seeing Errors That Read Error Code -39 and/or -2048

    How to Get Around the Issue:

    These two errors will come up, usually together, when there is a problem with Quicktime playback.  To clarify the nature of these messages:
    Error -2048 is actually a Quicktime error, not a Media 100 error, stating that a clip cannot be loaded; Error -39 is the same error, just using a Media 100 numerical code, relaying the same problem.

    If this comes up repeatedly, this will likely be connected to a specific clip in your project. What you will want to do is:

    1. Isolate the clip that is causing this problem
    2. Quickly, see if you are able to play this file from inside a Bin rather than inside the Timeline.

    If you are able to play this from inside a Bin, then most likely the file that is failing to play back is a rendered file, rather than the source clip.  In that case:

    1. Quit Media 100
    2. Delete your Render files associated with the project
    3. Re-launch Media 100, and you should be able to re-render these files and play them back successfully.

    If you are unable to play this file from inside the Bin:

    1. Quit Media 100
    2. Locate the file in the Finder
    3. See if it will play in Quicktime player

    Most likely this file will not successfully load into Quicktime player, in which case this video file is corrupt, and needs to be reinstated.  At this point:

    1. Delete this file
    2. Re-launch Media 100 – now this file should simply fail to load as an offline file. 
    3. Save your Media 100 project files. 
    4. Now, you will need to re-construct the media file.Note: if the corrupt file was a render file, you should be able to successfully and safely reconstruct this clip by rerendering.
  • BCC Installed but Not Applying in Final Cut Pro X
  • Subject: BCC Installed but Not Applying in Final Cut Pro X

    Issue:  When I apply a BCC effect in Final Cut Pro X, I see a red screen with a yellow triangle showing an “!” symbol.  The effect parameters load but the video is gone, and the effect does not appear either.

    Cause:  When BCC loads within Final Cut Pro X, itʼs actually loading Motion Templates rather than the BCC effects themselves.  If this error comes up, either the Filters themselves, or the Motion Templates, are missing.

    Steps to work around the issue:

    1. Quit Final Cut Pro X and Motion 5, and Uninstall BCC FxPlug.
    2. As an Admin-level User, run the Disk Utility on the boot drive, and reinstall BCC FxPlug, making sure that the Plugins and Templates are set to install.
    3. In the Finder, check for the BCC plugs in the first directory below, and for BCC templates in the second directory below Macintosh HD :: Library :: Plug-Ins :: FxPlugMacintosh HD :: Users :: [ Current User/Home ] :: Movies :: Motion Templates

    If the files are located in the directories above, launch Final Cut Pro X again and the plugs should load successfully now.

    If the files are not in the directories above, Uninstall BCC again, go into the Terminal application, type in the following and hit Enter sudo chmod 777 “/Library/Application Support/”

    After this, Restart the Mac, reinstall BCC FxPlug, and the plugs should operate now.

  • BCC AVX Crashes Avid on launch with Segmentation Fault Error
  • Subject:  BCC AVX crashes Avid on launch with Segmentation Fault error

    Issue:  When launching Avid Media Composer after installing BCC AVX, Avid crashes with the following error:
    error while trying to \Initialize AVX2 Host\ pop up appears and reads: \Segmentation faut\ in thread \MainThread\, at address 0x0

    Cause:  This would be due to BCC attempting to load a hardware asset that is no longer present — the most common reason would be if CUDA-based hardware was removed from the system, but the drivers for this hardware were not uninstalled.

    Steps to work around the issue:

    1. With all possible programs closed, delete the file called “libcudart.dylib” from this location -Macintosh HD :: Library :: Application Support :: BorisFX :: Lib :: BCC9BitDepthSupport*
    2. – If Avid crashes, search for these following files, and if you find them, delete them as well -Macintosh HD :: System :: Library :: Extensions — Filename: ʻCUDAʼ (if folder, delete)
      Macintosh HD :: System :: Library :: StartupItems — Filename: ʻCUDAʼ (if folder, delete)
      Macintosh HD :: Library :: Frameworks — Filename:  “CUDA.framework”
      Macintosh HD :: Library :: PreferencePanes — Filename:  “CUDA Preferences.prefPane
      Macintosh HD :: Library :: LaunchAgents — Filename: “com.nvidia.CUDASoftwareUpdate.plist”

    3. Once these files have been removed, Restart the Macintosh and try re-launching Avid Media Composer.
  • Poor Performance with Static BCC Wild Cards Effect
  • Subject: Poor Performance with Static BCC Wild Cards Effect

    Issue:  When Previewing or Rendering Static Instances of BCC Wild Cards, The Performance Is Notably Slow

    Cause:  The BCC Wild Cards Is Processing Unnecessary Information

    How to Get Around the Issue:

    1. During Preview at least (and possibly during Render), dis-engage the Anti-Aliasing function completely.  
    2. Turn off the Motion Blur if enabled.
    3. Set the Back Face to None, as these two functions are being processed despite not carrying out any visual alteration to the effect.

    Note: if you wish to use this effect in conjunction with another clip or visual effect (such as Glow or Glare), it would be recommended to either Pre-Comp or PreRender the BCC Wild Cards effect before applying additional elements.

  • Boris Effects are Misaligned after Rendering from Sony Vegas

    Subject:  Boris Effects Misaligned After Rendering From Sony Vegas

    Issue:  When I render my timeline from Sony Vegas, my effects have changed position.  My Vegas timeline is a custom size.

    Cause:  When the render carries out, the raw media automatically adjusts to compensate, but the effects do not.  Note: Even if your Vegas timeline is an SD/HD standard, this can happen if you render/export to an alternate resolution.


    Steps to work around the issue:

    1. Go into the ʻRender Asʼ window in Sony Vegas and press ʻShow filter optionsʼ.

    2. Check the box that reads ʻMatch project video frame sizeʼ but nothing else.

    3. Likely you will have 1 option – select this option and press ʻCustomize Template…ʼ





    4. In this window, change the Width and Height to
    match your custom timelineʼs settings.

    5. Press OK and Render.


  • Launching Boris RED as Transition in FCP
  • Subject:  Boris RED/FX does not launch as Transition in FCP.

    Issue:  When user applies Boris RED/FX as a Transition in Final Cut Pro 7, the plugin is recognized but when called upon from the Viewer window, the interface does not load.

    Cause:  Intermittent limitation of old-style plug-in architecture.

    Steps to work around this issue

    NOTE:  Any one of these might be enough to get the interface to load, so it might work before you reach the end of list below.

    1. Move the Playhead to the point of the specific Transition you are attempting to create/edit.


    2. Highlight the Transition.

    3. Go into your RT settings (located in your FCP System Settings) and make sure that your RT is set to ʻSafeʼ rather than ʻUnlimitedʼ.

    4. If steps 1~3 do not work, delete the Transition and reapply it.

    5. If steps 1~4 do not work, delete the ʻFinal Cut Pro Obj Cacheʼ & ʻFinal Cut Pro Prof Cacheʼ files from this directory –

    #  Macintosh HD :: Users :: [ Current User ] :: Library :: Preferences :: Final Cut Pro User Data

  • Jacked and/or Flickering Titles Made by Boris RED/Graffiti
  • Subject:  Jagged and/or Flickering Titles Made by Boris RED/Graffiti

    Issue:  My Titles Made in Boris RED/Graffiti are Jagged and/or Flickering When Rendered in My Host Application.

    Cause:  There are two settings in Boris RED and Boris Graffiti that re-adjust fields to optimize both vector and extruded text – Usually These Are Disabled, Causing These Problematic Renders; In Rare Cases, however, Having These Enabled Will Cause a Render Problem.


    Steps to work around the issue:

    1. Inside the Boris RED/Graffiti Interface, go into the Project Settings, accessible under the Edit menu.





    2. Inside the Project Settings, you will see two check-boxes: “1:2:1 Deflickering” & “Better Quality Field Rendering”.

    For Titles, it is generally best to enable both of these settings.  However, as mentioned previously, there are rare instances where enabling one of these will cause a similar problem.  As such, it is recommended you toggle these settings, individually, to obtain optimal render.

    3. If this does not fix the titles after a re-render, try rendering again, this time setting your Hostʼs Render Settings to a different Codec.

  • Avid Crash Outputting on Mac
  • Subject: Avid Crashing When Outputting

    Issue:  Avid Crashing When Outputting Timeline with Boris RED/FX/Graffiti.

    Cause:  A conflict is occurring between the output protocol or the hardware driver and the Boris Frameworks.

    How to Get Around the Issue:

    1. Quit Avid and locate your Boris plugs in this directory – 
    Macintosh HD :: Library :: Application Support :: Avid :: AVX2_Plug-Ins

    2. Inside here, ‘right-click/Control-click’ on each of your Boris RED/FX/Graffiti plugs, and select “Show Package Contents”. 

    3. Inside this new window, go into the Contents folder, and then into Frameworks – inside here, you will see a central Framework file for this plug.  Delete this Framework file for each of the plugs and re-launch Avid, and the crashes should no longer continue.

  • No Visible Video on Media 100
  • Subject:  Media 100 Gets an SD Video Signal but No Video Is Visible

    Issue:  When user goes to digitize SD material into Media 100, the source is recognized and the V is green, but the video preview is black, and the resulting video file has no video.  Audio works fine.

    Cause:  Default setting set to a modern digital standard.

    Steps to work around the issue:

    1. Close the Edit Suite window, but keep Media 100 open.
    2. Go into the Preferences and into the Video Input preferences.
    3. Set the Video Pedistal from 0 IRE to 7.5 IRE.
    4. Close Preferences, Re-Launch Edit Suite and try Digitizing Again.
  • RED/Graffiti Crashing on Launch
  • Subject:  RED/Graffiti Crashing on Launch

    Issue:  RED/Graffiti is crashing host upon launch, as well as when attempting to launch as a stand-alone program.

    Cause:  Problematic Fonts unable to successfully initialize, causing an interruption of launch operations.

    Steps to work around the issue:

    1. Primarily, you want to force most of the Filters on the system Offline.

    2. If you are using Mac OSX, close as many programs as possible and launch the FontBook application.  Inside here, you will see your Fonts listed —


    3. Highlight the Fonts in large groups and press the square button below (representing an unchecked checkbox).  Note that some Fonts are tied to the system itself and will not disable, so you will need to disable the Fonts in groups.

    If you are running Windows, you can Offline the Fonts on your system by closing all possible programs and physically removing the bulk of the Fonts from the Font directory* to a new folder of your own elsewhere.

    * – C:/Windows/Fonts

    Once the bulk of your systemʼs Fonts are disabled, try launching Boris RED/Graffiti again.  If it launches, you can close the program and bring groups of Fonts back online – eventually, you will re-enable one more more Fonts that are causing the crash, in which case you can keep the Font(s) disabled.

  • Getting your Boris product to display in the Operating Language
  • Subject: Boris Product Displaying in English on Non-English OS

    Issue:  I have installed my Boris Product(s) on my Non-English Operating System, but the Boris displays in English, not the language of the Operating System.

    Cause:  All Boris programs will run in the native language for most Operating Systems, but this requires a file to be installed called the ʻBoris Language Pack.ecsʼ

    Steps to work around the issue:

    1. Close all Boris programs and host programs.

    2. Re-run your Boris Installer – If you are on Windows, you will want to go with the ʻModifyʼ option (on the Mac this will come up automatically).

    3. Inside here, enable the ʻBoris Language Packʼ install option and Continue.

    a4. When installation is complete, close the installer and re-launch your Boris program and/or host.

  • Getting your Boris product to display in English
  • Subject: Boris Displaying in My Operating Systemʼs Language Instead of English

    Issue:  My OS (Mac/Windows) is a non-English OS, and after installation, my Boris product is displaying in the same language as my OS.  Instead, I want my Boris product to display in English.

    Cause:  The Boris installer, detecting the non-English nature of the Operating System,

    Steps to work around the issue:

    1. Close Boris Programs and any Host NLE that might be running.

    2. Go to the Boris FX, Inc. Folder — On Mac OSX, this will be located inside the Application Support directory.  On Windows, this will be located in the Program Files (or current equivalent).



    3. Delete the ʻBoris Language Pack.ecsʼ file & Re-launch your NLE and/or Boris Program.

  • Sony Vegas Pro will not update filter list
  • Subject: Sony Vegas Pro will not update filter list.

    Issue:      Sony Vegas Pro won’t update filter list to reflect newly installed BCC effects, requiring you to manually clear the effects cache.

     Cause:    This is a known problem with the BCC/RED installers for Sony Vegas and will be resolved at some point in the future.

    Steps to work around the issue:

    1.  Uninstall BCC for Sony Vegas.
    2. Show hidden files if they aren’t already on your system. For instructions on how to do this click over to https://windows.microsoft.com/en-us/windows7/show-hidden-files
    3. Open “My Computer”
    4. Open “Users”
    5. Open the folder labeled with your username.
    6. Open “AppData”
    7. Open “Local”
    8. Open “Sony”
    9. Open “Vegas Pro”
    10. Open the folder labeled with your version of Sony Vegas
    11. bLocate and delete the file called “svfx_plugin_cache.bin”
    12. aReinstall BCC for Sony Vegas


    For further questions/information please contact Technical Support at: https://www.borisfx.com/support/form.php


  • BFX Error -28
  • Subject: BFX Error -28

    Issue: When Working with BCC, Sometimes I See An Error That Reads ʻBFX Error -28ʼ

    Cause: This Is A Broad Error, But This Generally Indicates A Strain Of Available Resources For Preview Or Render

    How to Get Around the Issue:

    Your primary objective will be to remove any strain on the CPU, GPU or RAM usage when it comes to the BCC operations.

    The most common reason for this would be if the BCC effects are stacked among other effects; these could be other BCC effects or non-BCC effects, either built into the NLE or from another third party.  If you are stacking multiple filters onto your clip and receiving this error, it would be recommended that you break down the effect types used, and see if you are able to Pre-Comp or Pre-Render your footage having applied some effects, and applying the remaining effects to this Pre-Comp/Pre-Render.  A good example might be to Pre-Comp/Pre-Render footage that you are cleaning up using some of the BCC Image Restoration filters, and then conducting work involving Lights, Colors or Keying to this Pre-Comp/Pre-Render as a second pass.  The reason for this is the Pre-Comp/Pre-Render will purely be visual information, so the Host NLE will only need to process the newly introduced effects.

    If you are exclusively having this problem with GPU/OpenGL based effects, it would be recommended, if possible, to dis-engage any secondary Monitors you have – any additional Monitors beyond the main display would be utilizing the same resources as the OpenGL-based BCC effects.  If you are able to disengage any secondary Monitors, you will need to do so while the Host NLE/Compositor is Closed.

    Lastly, if you are on Windows, while the Host NLE/Compositor program is running, launch the Task Manager and go into the Services tab – inside here, you will see a running entry for your Host.  Right-click on this and go into the ʻSet Priorityʼ – likely your Host will be set to ʻAverageʼ; if this is the case, set it to ʻHighʼ, and after a minute or two, your Host should be operating with a bit more power.

  • Render Queue CC AME Workaround
    1. Add the project to the Render Queue:
    2. aIn the Render Queue twirl down the Output Module parameter and click on Lossless:
    3. bIn the Output Module window select Format Options:
    4. cIn Format Options select the codec that best suits your needs:
    5. dBack in the Output Module check the box next to Resize, open the Resize to dropdown menu and select the size and frame rate that works for you:
    6. eHit okay, select your render destination, and start your render.
  • Downloading Issue with Norton 360
  • Issue: Norton Utility sees downloaded Boris products files (BCC, RED et al) as security threat and deletes them. However, Boris files do not have a virus and are not a threat.

    Cause: This is a known problem with Norton 360 and downloaded Boris product files. We are working with Norton to resolve this.

    Steps to work around the issue:

    1) Open Norton 360

    2) Choose Tasks

    3) Choose Check Security History

    4) Choose Quarantine view from drop down menu

    5) Select the Boris file that was quarantined

    6) Click Details

    7) Click Options

    8) Click Restore

    9) Confirm by clicking “Yes”

    10) Click Close

    11) Run the Boris Installer to install the Boris product you are looking to use

  • Graffiti 5 installer doesn’t display Pinnacle Studio 16 as install option
  • Subject: Graffiti 5 installer doesn’t display Pinnacle Studio 16 as install option.

    Issue: Graffiti 5.2 installer doesn’t display Pinnacle Studio 16 in the list of host applications during install process. However, Pinnacle 16 is a supported host application.

    Cause:    This is a known problem with the Graffiti installer for Pinnacle and will be resolved at some point in the future.

    Steps to work around the issue:

    1.  Open the Graffiti Installer
    2. Select Pinnacle 14 as the host:
    3. eProceed to the next step in the install process
    4. Click the “Browse” button when given the option to select the plugin directory.
    5. fSelect “C:\Program Files (x86)\Pinnacle\Studio 16\plugins\RTFx” as your directory.
    6. gComplete the installation process
    7. Check to ensure that Graffiti is listed in Pinnacle 16, it will be listed in the FX browser.


    For further questions/information please contact Technical Support at: https://www.borisfx.com/support/form.php


  • FCP7 Crash in OSX 10.8
  • Subject: BCC Shaders crash FCP7 upon launch in OSX 10.8.3.

    Issue:      After installing BCC version 7 or 8, FCP will crash on launch citing Boris Shaders as the cause.

    Cause:    Shaders calls upon a portion of Mac OSX that no longer is supported in 10.8. This is due to the fact that FCP 7 is being considered a legacy product.

    Steps to work around the issue:

    1. Open Macintosh HD :: Library :: Plug-Ins :: FxPlug


    b2. Select “Boris Continuum Shaders.fxplug”

    c3. Delete “Boris Continuum Shaders.fxplug”


    4. Reopen FCP 7.

    *Note: BCS Filters will no longer function nor will they appear in the effects list

    For further questions/information please contact Technical Support at:




  • My activation keeps failing. What do I do?
    • Make sure you click “Verify” before you click “Activate” in the registration window or the message “activation failed” will appear.
    • If you have a firewall set up, you may not be able to connect to the Boris FX server resulting in the “activation failed” message. You may want to modify your firewall to allow your system to contact our server or, as an alternative, use UPID activation.

    Thank you once again for your Boris FX Purchase.

  • My system crashed… How do I get my license back?
  • Serial number activation:

    Contact Boris FX Customer Service – customerservice@borisfx.com or 857-488-3572. A team member will verify your purchase and help you reactivate your license remotely!

    UPID activation:

    Submit your UPID to Boris FX Customer Service – customerservice@borisfx.com or 857-488-3572. Your UPID will be verified, processed, and an unlock code will be provided for activation.

  • Transferring Boris FX Products to another system
  • Serial Number Activation:

    • Open the Boris FX registration window, and hit “Deactivate.”
    • Uninstall the product.
    • Reinstall the product on your new system.
    • Enter the serial number in the registration window.
    • Click “Verify” and then “Activate”.

    For detailed instructions, click here

    UPID activation:

    • Contact customerservice@borisfx.com or call 857-488-3572 with your UPID #
    • Once your UPID has been processed, you will be sent an Unlock code.
    • Open the registration window and enter the Unlock Code. Click “unlock.”

    For detailed instructions, click here


    Want more Boris?
    Sign up to receive the latest news, events, contests, and training videos.