[Peter Mcauley]

Hi,

Although it is a little bit late to add this feature request to the RED 4 release we will certainly add it to the list of features for RED 5. I’m sorry to hear that the time-code generator feature did not live up to your expectations and was not able to meet your needs for the piece that you were working on. We’ll take a look at the accuracy issue that you reported and let you know what if anything can be done to resolve this.

Cheers,

Peter.

[Peter Mcauley]

Hello,

Have you tried preprocessing the source to remove the jitter which the trackers are picking up? This jitter is usually caused by noise in the clip which is being tracked. You can reduce the noise that the tracker sees during analysis within the corner pin filter by clicking on the pre-blur button (if you are using the built-in corner pin effect in RED 3) or if you are using BCC4 Corner Pin filter you can enable the pre-blur and control the amount by going to the Preprocess tab and setting the amount of blur to add with the Blur – Sharpen parameter, which by default is set to zero.

I hope this helps.

Cheers,

Peter.

[Peter Mcauley]

Yes, if it was the same demo that I’m thinking of it was done with the motion tracker in RED. You can probably achieve the same result using BCC AVX also … the BCC AVX Corner Pin effect to be exact.

Cheers,

Peter.

[Peter Mcauley]

We will do everything that we can to resolve this issue with RED 4.

Thanks for bring this to my attention.

Peter.

[Peter Mcauley]

You’re welcome.

And yes, given the system specs that you sent over you should upgrade to BCC 4 and I’m fairly sure that this will put an end to the error messages that you are seeing. AE 7 and BCC 2 are not a qualified combination and actually I’m surprised that you are not experiencing hard crashes with this set up as there is an issue with earlier versions of BCC and AE 7 that would pretty much prevent this configuration from working at all.

Cheers,

Peter.

[Peter Mcauley]

That may do the trick alright, but I’m not 100 percent sure about that without first knowing what your complete system set up is. As you know you are currently two versions behind with the filters – I don’t know what your host version is though.

Before making a blind upgrade, I’d suggest that you pull down the try and buy version and run a few quick tests. If that solves the problem that you can make the purchase on-line by simply registering the trial version that you downloaded. You can download the software and use it for free for two weeks from the downloads section of the borisfx.com website.

Cheers,

Peter.

[Peter Mcauley]

hello,

what you are seeing is the result of RED being developed initially as a transition effect, in which case the effect would be correct. if you look at a 1 second comp in RED, you will see that although the application will indeed render out the correct number of frames (30), the timeline displays 31 frames. so … the problem lies in the fact that the timeline will trick you into believing that with the CTI at the end of the effect timeline that you are on the last frame of the effect when in fact you are actually one frame past the end of the effect. to get around this, you need to move the last keyframe back one frame – doing this should bypass the problem that you are seeing.

the clearest example of this that i can provide is to start with a 1 second comp, add a 3D plane, then set the spin of this track to 1 revolution across the timeline with linear interpolation. now move the CTI all the way to the end of the timeline and observe that the effect looks correct. render out the clip and when you play it back you will see that the result has indeed 30 frames but that the clip is still rotating and has not completed, in other words it doesn’t match the effect that you saw in the RED timeline. now return to the RED timeline and drag the last keyframe on the spinning track back one frame and render again. this result should appear correct and as expected. what you were seeing before moving the keyframe was that the CTI was sitting on the 31st frame, and not the 30th frame of the effect. this is because the frame counter starts at frame 0 and not frame 1, therefore the actual 30th frame is shown in the timecode indicator as frame 29 – if you see frame 30 in the counter then you are looking at the 31st frame, which is not going to be rendered in a 1 second effect.

if you need more information on this, please feel free to contact me directly.

i hope this helps.

peter.

[Peter Mcauley]

Hello,

Currently we don’t have a release date for the FX 8 or the Graffiti 4 updates, which will offer support for Xpress Pro 5.5, however we are aware that currently there is an incompatibility issue between these product versions and we are working on a solution.

The BCC AVX update will be the first update to arrive, with the others scheduled to follow sometime thereafter. You can probably expect an update to become available for BCC AVX 4.1 toward the end of July.

Please feel free to contact me off-list if you require more information.

I hope this helps.

Peter.

[Peter Mcauley]

hello,

you may have to add the clip to the image well for the filter within the fcp interface – i’ve seen this before in fcp. or you might just want to add a new track in the FX interface (command + K) to see if that does the trick.

i hope this helps

peter.

[Peter Mcauley]

hello,

please send a sample project to our tech support department along with a description of the issue and the tech guys will gladly help you with this. you will also have to send them all of your system information and the version of software that you are running, both the host and the plug-in. the tech support email address is support@borisfx.com.

i hope this helps,

peter.