Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP 6.02 VERY VERY VERY BUGGY

  • Jeremy Garchow

    December 16, 2007 at 11:09 pm

    [David Roth Weiss] “but no one should think for a minute that his findings, or those of Lumiere (where’s his real name BTW?) are universal to all FCP users with 6.0.2 installed.”

    Of course not.

  • Rene Hazekamp

    December 16, 2007 at 11:20 pm

    can you specify the configurations you’re using,
    I had my share of bugs in version 6.0.0 but after 6.01
    I had no problems with final cut ( color is a different story, butyoucan get it to work)
    I just finished five 50 minute programs (prorez hq , SD though)

    Ren

  • Walter Biscardi

    December 17, 2007 at 12:36 am

    [Lumiere] “(snapping snaps off on its own”

    This happens when you Option Select an audio or video track. This is the only new “bug” I’ve noticed with FCP 6.0.2, albeit an INCREDIBLY annoying one.

    I submitted a Feedback form request to Apple on this one. Other than that, really haven’t noticed anything unusual on the two systems running 6.0.2.

    Walter Biscardi, Jr.
    Biscardi Creative Media
    HD and SD Production for Broadcast and Independent Productions.

    STOP STARING AND START GRADING WITH APPLE COLOR
    The new Color Training DVD now available from the Creative Cow!

    Read my Blog!

  • Warren Eig

    December 17, 2007 at 6:19 am

    I just read Jeremy’s report and I don’t have any of these issues with FCP 6.0.2 and OS X 10.4.11 on an 8 core machine.

    Warren

    Warren Eig
    O 310-470-0905

    email: warren@babyboompictures.com
    website: https://www.babyboompictures.com

    https://www.atomfilms.com/af/content/knitwits
    https://www.atomfilms.com/film/family_xmas.jsp

  • Uli Plank

    December 17, 2007 at 7:20 am

    We have X1900s in all machines we are using with Prores and have no rendering issues with these. But recently a collegue of mine who is using ProRes only occasionally reported something similar as you do, and he has the standard NVidia card.

    Regards,

    Uli

  • Jeremy Garchow

    December 17, 2007 at 2:55 pm

    Hey Warren. That’s awesome! Glad to know that someone has it sorted out.

    The article was written for FCP 6.0.1, OS 10.4.10 and QT 7.2

    Some of the problems were fixed in FCP 6.0.2 (like the render file bug), but let me ask you this.

    Interlaced clips work in progressive timelines for you without changing the field dominance of the actual clip? Do 24p clips in 29.97 timelines render out as anything but 2:2:2:4 pulldown? And you can get virtual clusters to work on multi-pass VBR material? If you have the answers to these questions, please let me know. I will be happy to update the article if you can tell me how you have managed to get it all up and running.

    Jeremy

  • Jeremy Garchow

    December 17, 2007 at 2:57 pm

    X1900 with the firmware update. I am able to eradicate all artifacts by putting a nonsense filter on (such as desaturate set to 0, or a matte with 0 opacity). This forces FCP to render correctly.

    Jeremy

  • Warren Eig

    December 17, 2007 at 4:22 pm

    [Jeremy Garchow] “Interlaced clips work in progressive timelines for you without changing the field dominance of the actual clip? Do 24p clips in 29.97 timelines render out as anything but 2:2:2:4 pulldown? And you can get virtual clusters to work on multi-pass VBR material? If you have the answers to these questions, please let me know. I will be happy to update the article if you can tell me how you have managed to get it all up and running.

    Jeremy,

    I just did a project that was NTSC 23.98. It wasn’t 24p Advanced, which is what you are having the problem with? I created all titles and graphics in After Effects and they imported fine in the timeline. Could this be the way AE creates the 29.97 files? The footage was digitized at ADS in Los Angeles and brought to me on a Hard Drive. I believe they use the Kona card as I do.

    As for Compressor and Multi Cluster. I have the setting set to 4, not 8 I believe and do not have any problems so far. I have to clarify, that this is a production machine only. There is no MS Office installed or any other plugins or software other than Adobe Creative Suite and FCS 2.

    Warren

    Warren Eig
    O 310-470-0905

    email: warren@babyboompictures.com
    website: https://www.babyboompictures.com

    https://www.atomfilms.com/af/content/knitwits
    https://www.atomfilms.com/film/family_xmas.jsp

  • Jeremy Garchow

    December 17, 2007 at 4:29 pm

    [Warren Eig] “I just did a project that was NTSC 23.98. It wasn’t 24p Advanced, which is what you are having the problem with?”

    No. I am talking about Multiformat timelines. Take your 23.98 clip and put it in a 29.97 timeline and you will see the pulldown pattern rendered in will be 2224 and not 3:2.

    Also, if you have a progressive timeline, and you add an interlaced clip, you will see that it’s soft until you change the field dominance of the actual interlaced clip to ‘none’, even though the clip should be ‘lower’ as it’s a normal interlaced clip.

    [Warren Eig] “As for Compressor and Multi Cluster. I have the setting set to 4, not 8 I believe and do not have any problems so far.”

    That’s what mine is set up to, but on VBR and multi-pass codecs, it grinds the 8 core to a snails pace. If I turn off the Virtual Cluster, everything speeds up, but it only using 200-400% of the processor speed instead of 600-700% when I have a virtual cluster running. It really depends on what I am compressing as to whether or not I turn the virtual clustering on or keep it off.

    Jeremy

  • Chris Borjis

    December 17, 2007 at 6:13 pm

    Jeezus, I’m glad I didn’t update to 6.02

    great that some of you are not having any issues, but
    damn, there’s no way I’m updating until the next release.

    I learned long ago (IT Background) that if its not broken
    you don’t fix it, and if you do, be prepared to waste
    alot of time dealing with issues.

    I have absolutely no reason to update to 6.02 until
    we see how 6.03 does when its released.

Page 2 of 3

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