Toolfarm Network: AE Freemart | dvCreators.net | Maltaannon.com

Search the Store

Toolfarm's Plug-in Finder

Re:Vision Effects

From PlugInFinder

Jump to: navigation, search

RE:Vision, a visual effects R+D boutique, provides technical and artistic direction for effects development and realization. The RE:Vision team has proven experience in feature film, video, animation, advertising and internet-based projects. Additionally, RE:Vision designs, develops and supplies proprietary software tools and techniques available nowhere else!

Image:Aecs4small.jpgImage:aecs3.pngImage:ae7comp.jpgImage:macuniversal-sm.jpg

Products include

Note from RE:Vision Effects

Apple OS X 10.4.6 update may break our plugins.

Some of our users are having a problem after updating to Mac OS 10.4.6 when running our plugins. The error message will say something like "Can't load plugin, veclib missing", or "error in code fragment." The message varies depending on which host application you are running.

Turns out that there is a problem with the Mac OS 10.4.6 updater that removes a particular system file we rely on (the veclib.framework).

If you have updated to Mac OS X 10.4.6 and are seeing this problem with our plugins, then simply download and install the Mac OS X 10.4.6 Combo installer (not the simple updater), found here: Mac OS 10.4.6 Combo installer.

What to do if you are running FCP and after running the combo MacOS 10.4.6 installer you can successfully load RE:Vision Effects' plugins, but you get no parameter settings and black output frames.

First quit FCP. You need to remove the file "Final Cut Pro Obj Cache".

It's found in your home directory ( /Users/"your login account"), then go to the Library directory, then the Preferences directory, then the "Final Cut Pro User Data" directory.

It's a file that's built when FCP starts up and stores lots of things, like parameter for AE plugins. Because the first time you ran FCP our plugin didn't load, FCP *mistakenly* store no parameters for the plugin.

By deleting the file mentioned, FCP will then figure out what parameters our plugin(s) really need.

Warning: you may lose other preferences (but at this point, if you want to run our pugins, you don't have much of a choice... It's a bug with FCP, and this is the only fix). We think the file we are telling you delete is a fairly benign thing to do and you shouldn't lose any important prefs, however Apple doesn't tell us what is in each cache file for FCP.

If you are in a time crunch, then before deleting the "Final Cut Pro Obj Cache" file you should make a copy of it and save it somewhere else, then delete it from the directory described above. If important prefs or other favorites go away then you can put the file back (however, if you put the file back then you can't run our plugins until you delete that file).

Press