This content has been marked as final. Show 5 replies
Don't know what is causing your problem, which doesn't happen here under XP, but it is easier to start a new Prefs file by starting PPro with CTRL+SHIFT until the splash screen appears. That resets Preference to factory defaults just the same as deleting the file by hand.
Actually, David, it doesn't do that anymore. I found this out myself not too long ago after believing for a long time that the prefs file was deleted.
Ctrl+Shift just empties the plug-in cache, allowing Pr to load the plug-ins from the source. However, sometimes emptying the cache works as well as deleting the prefs file.
Thanks to both David and Jeff. I tried the Ctrl+Shift and, as Jeff explained, nothing happened. I tried a complete reinstall of PPro to no avail. I read somewhere that Encore CS3 and PPro CS3 had some compatability quirks...I'm uninstalling Encore and will see if the "Set to Unnumbered Markers" selection re-appears when I do yet another clean install of PPro.
I just found that out the hard way trying to troubleshoot someone's problems on the phone.
Seems you have to locate the ...\Adobe\Premiere Pro\3.0 folder in your user area and delete/change the name of the 3.0 folder nowadays to restart the many individual files that hold all the preferences nowadays.
Looks like a useful folder to which to create a shortcut on the desktop to save having to keep looking for it if you have problems.
For Tom: I guess it's the same with CS3, but with earlier versions the Preferences files were not replaced by a re-install of the program (nor deleted by the uninstall). Logic being that they are created if not there - so if they are there already the old ones are re-used. So you do need to deal with the preferences files to sort corruptions to the user interface or whatever, and a reinstall is unlikely to fix the problem.
It turns out, and I'm embarassed to say, that the prefs file was there, just hidden! I deleted it, restarted PPro and all was good. Another find, it apparently has nothing to do with any compatability issues with Encore (the problem reappeared after I had uninstalled Encore and before I reinstalled it).
Thanks to both David and Jeff for taking the time and expending a few brain cells to help.