Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy PLEASE HELP: Boris Title 3D Crashes… everything else seems OK

  • Justin Keen

    June 17, 2009 at 1:26 pm

    Mark,

    Here’s what I did –
    1. Log on as administrator
    2. Ensure you quit all apps
    3. create a folder on desktop called Removed Fonts
    4. Move all fonts from your HD::Library::Fonts folder to the Removed Fonts folder
    5. You should also check fonts installed in the user account – User::Library::Fonts
    6. Move these into your Removed Fonts folder or id you need to keep separate use fonts create a separate folder for these – eg Removed User Fonts
    7. Launch fcp and select Boris > Title 3D in the viewer
    8. In Controls tab in the viewer, click on “Title 3D – Click for Options” button
    9. The Title 3D should launch – if not you have a more fundamental problem and should re-read this thread for clues.
    10. Close the text / style window you just opened.
    11. Drag a small group of fonts from the Removed Fonts folder back into HD::Library::Fonts folder (you can sort however you want – I suggest dragging in a simple group of ten fonts at a time
    12. In Controls tab in the viewer, click on “Title 3D – Click for Options” button
    13. If Title 3D launches go back to 10 and repeat until Title 3D and fcp crash out or until finished
    14. Drag the last 10 fonts back to Removed Fonts folder and then proceed thru steps 9 to 13 moving just 1 font at a time…
    15. done…

    Doing the above and finding and removing the bad fonts took about an hour – removed 25 fonts out of 500.

    Note:

    a. You do not need to quit fcp each time you move fonts back into the directory, just close the Title 3D window.
    b. Fonts can be installed in other directories from the ones I mentioned, but these are the key ones and the HD:System::Library::Fonts should only contain the essential system fonts and no user installed fonts – but you might need to check here as well in case something bad was done earlier…

    Hope that helps

    Justin

  • Robert Jueneman

    February 5, 2011 at 3:18 pm

    I’m going to try the suggestions made in the above thread, but it seems rather ridiculous that Apple (or Boris?) hasn’t been able to fix this bug after a year and a half and multiple releases.

    I’m running on a 8-core MAc pro with 16GB of memory, with nothing else running (that I know of) except Time Machine and ChronoSync. But the ABEND has happened multiple times, both before and after the upgrade to 7.03 and OS-X 10.6.6.

    Is anyone else seeing this problem now?

Page 2 of 2

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