Josh Hatter
Forum Replies Created
-
we havent upgraded to leopard yet. anyone on 10.4.11 having a positive experience with 7.4.1?
thanks for the info
-
Any chance you are running Boris Continuum Complete 4.1 with FCP 6.0.2? We had this problem in the one room that had those plugins and it turns out thats not compatible with 6.0.2.
-
kind 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
-
You might want to boot off of the install CD and try repairing permissions, or use Disk Warrior.
Also, remove any 3rd party fonts and see if you can load.
and finally, try double clicking a project that isnt whatever is loading to start the application. Sometimes a corrupt project will cause that and i could see if you are clicking the FCP icon and its loading the same project and that project is corrupt, causing the app to crash.
Josh Hatter
HDNet Engineering -
We had no problems with multiclip Media Managed projects in FCP 5.1.4, then it stopped working properly in 6.0.1, and is back to being fully functional for us in 6.0.2. We MM DVCPro HD and XDCam multiclip shows, nothing less than 30 min.
Symptoms would be not having the right part of a master clip in the timeline, audio sync issues, just a messy messy deadline missing experience.
I havent heard any complaints since the upgrade to 6.0.2.
Good luck and sorry for the pain.
Josh Hatter
HDNet Engineering -
There are so many fixes in 6.0.2 that came up in 6.0.1 that i would encourage you to forget about 6.0.1 (might even be why they pulled it from the standalone downloads).
We are running 25 edit suites with FCP 6.0.2 and OS X 10.4.11 with nary a hiccup.
are you using the Software Update Utility? There’s a sequence of upgrades that have to happen before 6.0.2. Not in front of an edit suite but you need to install an Apple Pro Apps update, a security update, and i think Quicktime 7.3.1 in order to even see the 6.0.2 update in the Software Update Utility.
As a general rule I would avoid updating with standalones so you can let the system keep track of your updates for you. If you dont have internet access from your edit suite but are running OS X server you could serve any updates from there.
Hope this helps,
Josh Hatter
HDNet Engineering -
we use Moving Pictures here
the editors gush about how great it is for scaling. they also point out it can have some issues if the project is bounced back and forth between machines….
They all agree that scaling past 100% size for stills is really bad in FCP….
Josh Hatter
HDNet Engineering -
do the files show the quicktime icon in the capture scratch? if not, then you can simply create new resource forks by batch or script using something like A Better Finder Attributes 4. we had a backup drive deleting the resource forks on files and they all were showing up as linux exe files in the finder and we could not relink to them until I made them back to being Quicktime movies.
We had errors like this on our xsan because of permissions. you could try setting that volume (assuming its not shared or networked) to ignore permissions, or you could change permissions on everything on the drive to be owned by the account you normally log in as.
A couple of things to try i guess before recapturing…
-
The 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 -
We have 8 XServe RAIDs here and have had 1 drive failure in the last year. We bang on these drives at least 16 hours a day from 15 edit suites with no problems.
We also just bought two more RAIDs populated with 750gig drives and the Apple rep never said one thing about problems.
What your salesperson did would make me very nervous about their integrity.
Josh