LiveType Major Problem: HELP!

Question

Level 1

0 points

LiveType Major Problem: HELP!

Running OS 10.4.11, FCS 2 6.0.3, QT 7.4.5 on both a Mac Pro Dual 3Ghz and MacBook. Livetype styles, effects, objects do not show in LiveType and renders are black. Old .ipr files display as plain text within FCP without styles or effects. This all stems from the last Pro Applications Update. Everything was fine until that was installed and now my finished project awaits a fix before I can output it. This has nothing to do with storing assets locally or on another volume. I do not have a problem with asset location.

Mac Pro, Mac OS X (10.4.11)

Posted on Apr 29, 2008 11:52 AM

Reply

Answer 1

D Gilmore

Level 4

3,525 points

Apr 29, 2008 2:00 PM in response to cinegrant

Close Live Type.

Go to: Users/your user name/Library/Preferences.

Drag the file named "com.apple.LiveType.plist" to the Trash

Go to: Applications/Utilities/Disk Utility

Select your system disk

Click on the Repair Permissions button. Wait for the repair to complete.

Restart your computer.

If this doesn't work then perhaps your textures etc were not installed correctly. Use spotlight to search for them.

When you installed your FCS2 did you do a clean install? That may also be an issue.

Hopefully it will resolve itself with the first suggestion.

One note...it is always wise to repair permissions after doing a software update.

Good luck

Reply

Answer 2

cinegrant Author

Level 1

0 points

Apr 29, 2008 6:44 PM in response to D Gilmore

Thanks, but I think it is a bigger problem than that. I religiously do and have done what you've suggested - good advice. I've had a great working solution - FCS2 - for quite some time and have made tons of graphics in LiveType and Motion with no problems. This just cropped up. I'm literally done with a project, but went to adjust the position of an .ipr in FC timeline (final fix) and realized it didn't look right at all. Then I opened the .ipr in LiveType to find what I stated before. This is for all historical .ipr files. So now I'm ready to output and can't.

Thanks for the suggestions again.

Reply

Answer 3

D Gilmore

Level 4

3,525 points

Apr 29, 2008 7:35 PM in response to cinegrant

That's not good news.

According to Digital Rebellion: Apple just released QuickTime 7.4.5 to coincide with the release of iTunes 7.6.2 and Front Row 2.1.3. The coincidence of these releases suggests that the QT update specifically affects those applications and offers no specific benefits to Final Cut Studio. If you have a working system, DON'T install it!

I posted a Macfixit link some time ago: http://www.macfixit.com/article.php?story=20080208085017788
but have since received an email saying it is no longer active.

There is a thread you may wish to read,
http://discussions.apple.com/thread.jspa?threadID=1392289&tstart=0
Ultimately based on your response I would guess you need to go back to a previous version of QT

Reply

Answer 4

cinegrant Author

Level 1

0 points

Apr 29, 2008 8:39 PM in response to D Gilmore

This one hurts, I don't really have a workaround. I have read in other forums that it all has to do with the latest Pro Applications update.

Reply

Answer 5

Apr 29, 2008 10:25 PM in response to cinegrant

Had this problem ever since QT7.4.5 released (2++weeks ago). Only way to make livetype works again is by downgrading to AT7.4.1 and also you have to drop FCP603 to FCP602. FCP603 doesn't work without QT7.4.5, (Some1 says QT wont affect FCP, it sure does mate)

Set back is, if your project is already opened in FCP603, FCP602 won't open it. Unless you have backup set up and have not ponder long enough like me. 😟. If you on Time Machine, you can recall back also. How? Ask the guys using Leopard.

So for the next few weeks I will be without Livetype. All projects are already in FCP603. Apple, can you just make the projects backward-compatible to at least all V6 can opened regardless of version number. You are choking us here. I lost a lot time attending to the client's request using LiveType. Time = Money.

Still awaits the remedy from Apple on this issue. Maybe they look into this since NAB is over.

Reply