Peter Mcauley
Forum Replies Created
-
Hi,
Yes, the raster / vector paint engine was introduced to the product line with RED version 4 almost 2 years ago. You friend is correct – the paint in RED 3 is a stroked or filled spline shape only and offers no pressure data nor does it work with image or other media as a paint dab. I’m afraid that the only option for you is to upgrade to RED 4 to get this feature.
Thanks,
Peter.
-
It’s the second pop-up from the top in the paint tab in the controls window. Remember, this is only available when you have a paint path sub-track selected in the timeline.
I hope this helps.
Peter.
-
Hi,
If you would like to send me the project I can take a look at it to see if I can understand why this is happening. You can send it to me at peterm@borisfx.com. No need for any media elements … just the zipped up project setting.
Cheers,
Peter.
-
Glad to hear that it was something as easy as this Bill.
Cheers,
Peter.
-
Yep – you can do that alright. I’d suggest maybe 100×100 px because you have to realize that these are bitmap brushes and that as you scale the brush size over 100 percent you’ll see jaggies in the brush detail. Here are the steps to get them into RED:
• with RED launched, create a new paint layer
• click on the paint path sub-track in the RED timeline
• in the controls window, set the Color Source pop-up to Image + Image Alpha
• in the brush Image sub-track in the timeline click on the V1 icon beside the eyeball
• select the psd file of your choice
• now when you make a paint stroke, the brush will be the psd image
• next open the style palette window
• go to the brushes tab
• click on the icon at the left with a blue + sign – the brush is now saved and can be used on other projects.Cheers,
Peter.
-
Hi Bill,
If you are seeing jaggies in FCP then you most likely are viewing the comp at something other than 100 percent. Try setting the viewer window to 100 percent and see if this resolves the issue. On my machine here, I see the identical looking anti-aliased result on text elements … I have the comp window in RED set to 100 percent and the record monitor in FCP at 100 percent. If I change over to any other size of course, I see jaggies but this is expected and I think it is like this in every application.
I hope this helps.
Peter.
-
Hi,
We really need to reproduce the issue here in house on one of our systems before we can say wih any confidence where the problem might be – ie, in the host or in the plug-in. With that I would like to ask that you send in the details of this problem in an email to support@borisfx.com and let’s see if we can find a way to get the problem resolved, as I can understand that having to rerender your effects every time you reopen the project would not be conducive to good workflow. 🙂
Thanks,
Peter.
-
Hi Mark,
What are you doing when you see the slowdown in RED? Is OpenGL preview on or off? Remember that in RED we only use OpenGL for preview purposes, not for final rendering so are you seeing a slowdown in the renders or in the preview on screen?
Thanks,
Peter.
-
Hi Ray,
Well this is all very odd … I have a clip in a sequence to which I have applied the BCC 5 Velocity Remap filter. I set the filter to 10 percent of the speed of the original clip. Then I nest this clip by selecting Sequence>Nest Item and rendered the effect. The effect appears to be correct and I didn’t see any messages on screen per your experience. When you added the filer to the clip in the original, non-nested sequence, did you drag the clip from the project bin into the filter’s media well? If you dragged it from the timeline then I can understand how this may be a cause for the filter to behave as you describe so maybe that’s the problem? If you have not done so already, can you please try that to see if this helps?
Thanks,
Peter.
-
Hi,
To close a custom shape you need to select that last point that you created and then click on the first point that you created. This closes the loop.
Cheers,
Peter.