I copied over some backed up P2 footage and launched FCP 6.0.2. Then I repaired permissions and restarted. This took a while, as I also went to Griffith Observatory with my family, and wasn’t on hand to press the OK button or swap DVDs. Then I ran the Tiger Upgrade Install CD, then used the System Update System Preference to bring everything up to the most current version. I erased it and formatted it MacOS Extended. Purchased a new 320GB SATA drive…only because I wanted to start fresh, and these were on sale for $50, and I had stuff on the other drive that I wanted to keep and didn’t really want to copy it to another…WHATEVER…I got a new drive. ![]() Here is the whole rigamaroll I did THIS time to narrow it down, the troubleshooting steps used in getting P2 import working with FCP 6.0.2: ONly when I ran the Uninstaller did it actually clear things up. Uninstalling would be best (if possible), as one of the things I tried doing was removing ALL of the plugins from the Plugins folder, and it still failed. SO…if you have this, or maybe other FxPlug plugins, try removing those and running FCP again. It finally failed when I loaded FX Factory. Install FCS 2 fresh, update it, and then install applications and plugins, testing the Import option after each one. I even went so far as to get a new HD, install the OS fresh, update it. As soon as I removed those, my import function returned. So in my testing I found the culprit to be the FxPlug plugins from FX Factory. I started a threat on the Apple forums to track this issue. ![]() When I restarted, this didn’t work at all. Initially I solved this by zapping PRAM, running Disk First Aid and repairing permissions and trashing FCP prefs. Suddenly the LOG AND TRANSFER option for P2 didn’t work. ![]() There was an issue that cropped up when many of us upgraded FCP 6 to 6.0.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |