[Jon Kozenko]

Steve,

This is actually a function rather than a setting, so you will need to do this after importing the still, but luckily it’s very quick. What you will want to do is first import the still image and then expand it so that you can see the Face track in the timeline. Highlight the Face track and in the Controls window, you should see a single tab that reads “Image Media” – inside there, click on the ‘Aspect’ drop-down and select ‘Fit to Project Size’. This should automatically re-size the image to match.

Thanks,

Jon

[Jon Kozenko]

Steve,

On its own, AvidFX/RED does not have this kind of function, but you could potentially do so with a setting that automatically scales all of your imported stills to the project resolution. If you made this effect, originally, with an image that matched the project resolution, then this should allow you to load alternate stills and have them re-size without having to manually re-sizing them to match.

If you were not using a still that matches the size of the AvidFX/RED project, then it might be easier to re-size the new image to match the old before importing it.

Thanks,

Jon

[Jon Kozenko]

Don,

Thanks for providing the before and after images of your problem. I looked it over with SQA, and it seems that everything is correct, not only in terms of BCC setup, but there also wasn’t anything in the Avid interface that suggested you are running in any kind of mode that might prevent this.

We’ll continue to look at this, but in the meantime, do you think that you can give me about the project? Such as, what is your Resolution and Codec, and what kind of files are these (such as XDCAM, P2 or normal Quicktime files)? Also, does this happen if you toggle between 16-bit rendering and 8-bit?

If you can reproduce this with a mock-project using just a still of your foreground clip, do you think you can send me your Avid project file, along with the two images? That way, we can take a look directly into the problem first-hand.

If you can do this, please send it to support@borisfx.com.

Thanks,

Jon

[Jon Kozenko]

Jaeson,

I compared the Lens Flare Adv effect and the Lens Flare 3D effect and found that this obscuration element is actually part of the Lens Flare 3D effect itself (rather than an After Effects function that Lens Flare 3D can utilize). As such, there is no direct way of creating such a direct obscuration with the Lens Flare Adv. In addition, the Lens Flare Adv does not have a Pixel Chooser tab, so this might be entirely manual in RED.

Thanks.

Jon

[Jon Kozenko]

Lon,

It’s possible that your version of BCC 7, on your new system, is of an earlier build than was used on your previous version. For reference, the last version of BCC AE 7.0 ever released was 7.0.7.4 – what version of BCC 7’s did you use to install? The exact version of the installer should be mentioned in the installer’s name.

Note that BCC 7 is not tested or supported for CS6, so it is possible that BCC 8 will load these effects and operate in CS6 (and later) perfectly. As such, I would recommend downloading the trial for BCC AE 8 (not BCC AE 8.3) and, if it works, upgrading to this version.

Thanks,

Jon

[Jon Kozenko]

Steve,

Thanks for the RED Project and the Crash report. I opened it up on two systems and found that RED crashed when opening the project itself. Note that this was even the Stand-Alone version of However, I was able to trace the problem to the display by enabling the Caps Lock before opening the Project File or Interface. This suspends the image from drawing, and allows me not only to open the project but alter it.

To allow the project to fully open, I set the Preview Quality from ‘Best’ to ‘Draft’ and Preview Resolution from ‘Full’ to ‘Quarter’. Then, when I released Caps Lock, I was actually able to change these back to ‘Best’ and ‘Full’ without RED crashing again; this seems to be exclusive to when RED first opens the file.

Hopefully this should help.

Thanks,

Jon

[Jon Kozenko]

Steve,

Interestingly enough, one of the things that the OpenGL will help with most is the preview of Extruded objects, such as text. Your Graphics Card is a strong one, so enabling OpenGL, preferably Max Caching, should not result in any problems and should speed things up. Also, you can try disabling either ‘Better Quality Field Rendering’ or ‘1:2:1 Deflickering’, but these will sometimes help the image quality when enabled. As such, try toggling these two (primarily Better Quality Field Rendering) and see if this speeds things up, perhaps without causing any lower-end renders to take place.

Thanks,

Jon

[Jon Kozenko]

Bart,

If the file is indeed an Illustrator 8 file, it should appear automatically once imported as an EPS. There might be a setting in the EPS itself, so, as such, do you think you can send me a copy of this EPS file? Send it to support@borisfx.com and I’ll take a look at it.

Thanks,

Jon

[Jon Kozenko]

David,

You mention slow renders in FCPX but that you have both FCPX and Motion – have you tried this effect in Motion as well, and if so, is it slow there as well? Also, is this effect applied to a video with any other effects applied to it, or perhaps video with an alpha channel? Lastly, try loading a few alternate presets for the effect, or minimizing a few aspects, as maybe one or two parameters, if turned down, will speed up the effect. If turning down one or two specific parameters do speed up the effect, let me know and maybe we can see why those specific ones are slowing it down.

One more thing – Which exact version of BCC are you using? You should be able to find this by performing a ‘Get Info’ on one of the main BCC files here –
Macintosh HD :: Library :: Plug-Ins :: FxPlug

Thanks,

Jon

[Jon Kozenko]

David,

The license for the BCC plugs will work with both FCPX and Motion, as they would be the same and would adhere to the same license file. If your Motion is 32-bit, or if they are installed on different boot drives, you may need to input the Serial a second time, otherwise the license will work with both.

Thanks,

Jon