-
Delirium Camera Shake Key ??
I was going to post this in the Digeffects forum, but there has only been 1 post in the past month so figured it would get better seen here.
I just recently started work at a new company and they have a copy of DigiEffects Delirium for AE. Quite a nice set of plug-ins I might add.
I am using the Camera Shake plug-in from them to give a logo a “rumble” effect. It works and looks amazing, much better than how I would do it normally (wiggle, or record motion and drawing a squiggly line myself).
Anyway here is the problem. It seems this plug-in does not allow alpha channels. Here is the scenario. Let’s make it simple. I have 1 layer with the logo on it that is the logo with a transparent background. Above this logo I have an adjustment layer with the camera shake applied. If you switch to view alpha in the comp preview window you see the logo keyed out nicely throughout the whole animation, UNTIL it reahces the point where the camera shake comes in. At this point the alpha is removed 100% and it adds a black background to the file.. VERY frustrating.
I’ve tried numerous things to fix it, I’ve tried applying the effect to the logo layer itself, same exact result, adjustment layer as mentioned above, even applied ANOTHER adjustment layer above everything with XMult applied at the camera shake moment hoping it would key out the black during the shake.. No dice..
For whatever reason it seems this plugin was ONLY designed to use with fullframe video, and trying to use it with anything else, it just removes all alpha and leaves you with full frame black.. Does anyone know of a work-around with this plugin? Or am I forced to go back to “rumbling” objects how I use to, which by the way don’t look nearly as nice..
Any help appreciated, sorry for the long post, just wanted to give as much details as I could. Also I’m running AE 6.5 on Windows XP. I’m not sure what version of Delirium it is, but when clicking “about” it does say copyright 1996-1999 so I’m assuming its a rather old version.. Would an update possibly fix this?