After using Premiere 6.5 for several years on Windows XP with no problems, it now crashes and Windows kills the Premiere task when going into the titler. I completely uninstalled Premiere and re-installed it. Same problem. I bet Microsoft has received several dozen crash reports from me on this one. I usually do not connect this system to the internet, but at times I do and Microsoft updated windows sometime lately. In an effort to try to fix the problem I updated Windows to Service Pack 3. Titler still fails. I also have Premiere Pro which works, but I like 6.5 better. Has anyone run into this problem? I am lost without this tool.
OK. I an up and running again. I will tell you how I located the problem as it might help someone else. The crash was in the Microsoft C++ Run Time Library routine MSCRT.exe which is probably not unusual. The suggestion to look for corrupt fonts was a good one as it narrowed down the search. The article recommended in the last post suggested eliminating fonts with a binary search scheme, which I decided to leave for a last resort as it would be very time consuming as I found fonts in places I would never think to look.
I installed Premiere 6.5 on another of my systems which was at the same windows level and it ran OK. Then I added a new user on the failing system and again it ran OK. So I determined that the trigger must be stored in the area common just to a single user where Adobe stores info about that user. After comparing and eraseing files where preferences are stored with no success, I discovered the file where the users titler styles are stored. I copied this file from the working user id to my user id and now all is working. The bad font is still out there, but if I load a style from the Adobe supplied set in the future, I will be able to locate it quickly now that I know what to look for.
The idea of creating a new user ID might be good for finding other problems.
The file was "documents and settings\username\my documents\adobe\premiere\styles\workingset.prsl
Thanks to all who responded with hints.
Thank you for your comprehensive report. I would not have thought to check user Type Styles, but will from now on. I plan on adding your report to my article on font issues with Titler.
If you do find the problem font, and that font file is not corrupt, please report its name. That will likely help others. That is how we found the Deja Vu font, which was not corrupt, but killed Titler (thanks to Jeff Bellune's efforts).
Now, I have also found several non-corrupt fonts, that will just not display in Titler. There are several versions of Isabelle, and Isabella, from a couple of foundries, that just will not display anything but boxes. Why? Can only guess that there is something in their metrics that smurfs Titler. It does not crash, but just will not display these.
Your work is appreciated. Now, off to add your comments to my article.
Hunt
[Edit] Done. Your efforts and your post might well same others grief and get Titler up and running for them too.
Message was edited by: the_wine_snob - Added [Edit]
I tried to reproduce this problem with no success. A few days before I
experienced this problem I had added several Adobe supplied styles to the
Titler font set. To try to reproduce this failure I added all of the Adobe
supplied styles to the titler a few at a time and it never failed. I would
not expect any Adobe fonts supplied on the distribution disk to fail as I am
sure they are well tested. I have never used any fonts other than those
supplied. Also, you will observe that the titler window appears before it
start loading fonts at the bottom of the window. In my case the window never appeared before the crash. I have to assume that the
file "workingset.prsl" got corrupted somewhere in the process. I am very
happy that the problem has been solved and if it happens again we will have
one more trick up our sleeves to solve it.
Bill
North America
Europe, Middle East and Africa
Asia Pacific
Copyright © 2012 Adobe Systems Incorporated. All rights reserved.
Use of this website signifies your agreement to the Terms of Use and Online Privacy Policy (updated 07-14-2009).