Activity › Forums › Apple Final Cut Pro Legacy › FCP 6.02 VERY VERY VERY BUGGY
-
Uli Plank
December 17, 2007 at 6:51 pmI see!
We need to render most of our stuff, since it’s loaded with FX. That’s why I haven’t seen the issue.Thanks,
Uli
-
Melissa Hore
December 17, 2007 at 8:17 pmJust curious have you run into any bugs that are effecting the autosave….It seems dispite my settings my projects are not consistantly autosaving…No big deal just frustraiting when i crash and i haven’t saved….
-
Walter Biscardi
December 18, 2007 at 1:55 am[Melle01] “Just curious have you run into any bugs that are effecting the autosave….”
Funny, AutoSave is one feature I have never used in FCP. It’s the first thing I turn off when I re-set my Prefs. I always have my left hand near the Apple and S keys so I just Save pretty much every couple of edits.
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! -
Josh Hatter
December 18, 2007 at 8:03 pmThe DVCPro HD frame size issue has not occurred for us since the upgrade in 18 edit suites.
We also have not had a clip export without timecode since the upgrade.
Also, the loss of render files has not reared its ugly head.
That having been said, my editors say things seem a little bit slower now. Little things, like the pinwheel of death is around longer when switching between Finder and FCP. Opening projects takes longer. Its sort of an intangible issue, defining time in moments, so I dont know how to qualify this.
Also, media managed projects all seem to have suffixes on their media, which is good for us and our backup system that was having issues with appledouble files.
Josh Hatter
HDNet Engineering -
Chad Greene
January 23, 2008 at 6:46 pmI am having some of these issues as well. The worst is the slow response times. Currently I am working on a 2 hour documentary consisting of three projects. Reel A, Reel B, and a Media project (I had to break it apart a few years ago because of its size). I am also working completely off shared storage. I am connected, via Fiber, to an Avid Unity LS.
Slowness
Yesterday it took 8 minutes to open all three projects, and switching from the finder to FCP took 1min 20sec. The day before my switch time was 55sec. When I watch the Activity Monitor, I can see FCP dump a load of Ram when I leave, and when I switch back it slowly reloads the ram before letting me work.Renders
When I leave FCP and come back, I am still loosing renders like I was in 6.0.1These are my most serious issues, but I am getting worried about the HD ProRes HQ stuff. I have played around with it, and am getting ready to Online the doc using HD ProRes HQ, but am wondering if this is workable or not. I have a mix of formats. Are there things I should be watching for so this goes smoothly?
Chad Greene Mahoney Media Group Minneapolis, Minnesota 2x3GHz Quad-Core, 4GB Ram, OS 10.4 FCP 6, Kona-LH
-
Josh Hatter
January 23, 2008 at 6:56 pmkind of a shot in the dark, but its something we FINALLY figured out this week on one of our machines.
Machine was really bogging down tabbing between FCP and Finder. Certain projects using Boris would bomb out FCP the minute the project opened, ONLY if the title clip was VISIBLE in the timeline. if it was off the page so to speak, no prob. then you move down the timeline, that title shows up (not even in playout, just on the timeline on the screen) and poof the app quits.
We were running Boris Continuum Complete 4.1 on FCP 6.0.2 because on the boris site it says you can. I finally called them and found out thats a typo and we had to upgrade (they call it a cross grade) to FCPlug 5.
In short, BCC 4.1 does not work with FCP 6.0.1. If you are trying to use this that could very well be your problem. Its an easy uninstall but i threw away the piece of paper i wrote down the components on.
Josh
-
Jeremy Garchow
January 23, 2008 at 7:06 pm
Reply to this Discussion! Login or Sign Up