Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Green noise dots in FCP5 with Text.

  • Mark Raudonis

    August 19, 2005 at 12:16 am

    I have seen this occasionally. You may want to check your “broadcast safe” filter. In our case that was the culprit.

    Mark

  • Rick Sebeck

    August 19, 2005 at 12:21 am

    I still haven’t figured out the green ghost!

    I have noticed that rendering in RGB cures the problem, as well as changing the scale of the clip.

    Sometimes just re-rendering it several times makes them go away.

    By any chance are you using a Kona2 card? or using an Xserve? – just trying to see if it is FCP related. I am assuming so, since I have also had to set all of my sequences field dominances to “none” since the upgrade to fcp5 as well… seems like there have been some strange render issues.

  • Rick Sebeck

    August 19, 2005 at 12:41 am

    I noticed that PNG’s with an alpha channel do it ALL the time. I just took one and saved it as a PSD… problem solved. But some text generators do it too. Definitely an alpha channel issue with YUV rendering. I haven’t upgraded my FCP or OS since my Fibre Channel software (FibreJet) doesn’t like mismatched OS’s… wonder if it is fixed in the update?

    I’m thinking about pulling the trigger to find out! My home G5 is my guinea pig, and it has 10.4.2 and FCP 5.0.2 and no problems… but no Kona either… it may be a 10 bit thing.

    Dual 2.5 G5, 4GB RAM, OS 10.4.1, FCP 5.0, QT 7.0.1, Kona 1.1.2, FibreJet 2.0.4, Xserve

  • Rick Sebeck

    August 19, 2005 at 12:46 am

    Okay… definitely a 10 bit problem. I took a PNG that had an alpha channel, stacked it on top of a basic matte color. In Kona 10bit sequence set to YUV renders with green crap.
    Kona 10bit sequence set to RGB renders fine.
    DV NTSC sequence renders fine.

  • Rick Sebeck

    August 19, 2005 at 12:52 am

    Just noticed one more thing….

    It seems to only happen when you apply settings that affect the alpha channel… like a drop shadow. PSD with an alpha with no drop shadow, rendered in YUV 10bit… looks great. With a drop shadow,, you get the green dots!

    Speaking of looking great.. why do you have to set the field dominance to none in order to get a good looking render in FCP 5?

  • Rick Sebeck

    August 19, 2005 at 12:59 am

    https://docs.info.apple.com/article.html?artnum=93871

    “When using 10-bit high precision rendering, clips with motion blur and a drop shadow do not render. This can happen when working with uncompressed material, or when working with DV if the 10-bit high precision rendering option is enabled.”

    Well there’s the answer! Wow… this is the first time I’ve seen this article… and it applies to FCP 4.

  • Dan Riley

    August 19, 2005 at 2:16 am

    If you are using Aurora Pipe Studio, you will see white dots
    on some clips in 10bit uncompressed rendering,
    especially if you use the color correction 3 way filter
    and lower the blacks a little bit. This problem will
    completely go away with 8 bit rendering.

    Today Aurora support told me (because I had asked
    them about this previously) that their new driver 4.4,
    released soon, will fix this. They also mentioned
    Apple has some bugs they are working on in this area
    as well.

    Dan

  • Aaron Neitz

    August 19, 2005 at 4:14 pm

    Fields = None looks SO much sharper for things like Widescreen, Cropping, and Text. But in FCP 5 with 10bit UC, and a Kona SD, I see this wierd strobing in the motion (like the 3:2 jitter frames are being played in the wrong order. . . . .). So I’m forced into Fields = Lower.

    Buggy, buggy, bug ridden.

    Some things that used to work well, they just don’t now.

  • Rick Sebeck

    August 19, 2005 at 4:25 pm

    Exactly… I get a weird jitter as well. I have been keeping my sequences to “none” so that my text looks sharp and crisp, then removing field dominance on clips that have jitter. I have noticed film clips that have been telecined, when scaled to less than 100% are the worst. You can actually see the bars of interlacing when parked on a B frame.

    I never noticed this before FCP 5

  • Aaron Neitz

    August 19, 2005 at 6:20 pm

    On the B frame? Like FCP is reading a field ahead of itself?

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy