Activity › Forums › Apple Final Cut Pro Legacy › Livetype — treated as text or image?
-
Livetype — treated as text or image?
Posted by Brian Pitt on May 25, 2006 at 4:32 pmIf I render out a quick text animation in Livetype and bring it into FCP, do I have to make sure that it is in the text safe area, or can I go all the way to the image safe boundry? I guess it is not actually text anymore because it has been rendered out to a quicktime file.
Any ideas?
David Bogie replied 19 years, 11 months ago 7 Members · 10 Replies -
10 Replies
-
David Bogie
May 25, 2006 at 5:15 pmThe question implies you do not understand what those safety areas are actually for and how they are used. The explanation in the FCP manual is a good place to start.
The decision on the edges of your frame depends on your final output. If you’re going to television, use the safe areas. If you’re going to computer, it doesn’t matter.bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Brian Pitt
May 25, 2006 at 5:18 pmThank you for the insult, but I do understand what safe areas are for.
I am going to television, therefore, safe areas do matter. Because the text I am using isn’t in text form, I am wondering if I can go a little outside of the text safe area and still be okay.
-
Debe
May 25, 2006 at 5:20 pmI’m not sure I understand the question.
Title safe is title safe. If you have an image, whether it is text, graphic animation, or whatever, if it goes outside of title safe, you are not guaranteed that it will not be cut off on every television. You can push it to action safe, but you run a risk of it being cut off. You can push it to the edges of the screen, but you run a much bigger, more likely risk, of it being cut off.
Does this make sense?
debe
-
Brian Pitt
May 25, 2006 at 5:28 pmyeah. I guess I was a bit unclear. I was under the impression that as long as you were in the image safe area, everything but text would be safe from being cut off. thanks for the quick explaination.
-
Chris Poisson
May 25, 2006 at 6:45 pmIf you want to fly it in like any graphic, all that matters is that it is in title safe for a period during which you want to read it.
Have a wonderful day.
-
David Roth weiss
May 25, 2006 at 6:46 pmBrian,
Title safe was originally created by broadcasters in the 40’s and 50’s to avoid legal wrangling for and with advertisers when it was determined that every brand of consumer TV on the market had different cutoff points near the screen edge. If the advertisers text, logo, legal disclaimers, etc. are inside title safe, then no lawyers can say the advertisers message is not on-screen as stated in their contract. Its makes no difference what form the message takes, text, graphic, logo, just that important info is guaranteed to hit every screen on the viewers end no matter what type of display they might use.
DRW
-
Bret Williams
May 25, 2006 at 10:42 pmYou apparently don’t understand. Text, whether text or a graphic, may not be visible on a television if outside the safe area. Different TVs cut off different amounts of the image. That’s all there is to it.
-
Justin Toops
May 26, 2006 at 1:45 pmDon’t bother exporting as a quicktime from Livetype (unless you have a slower computer). Instead, just save the file as a livetype, and then import it as such into FCP. Then you can scrub through the file on your timeline to see how it works. If it doesn’t look any good (eg, too big and outside sife areas…) then right click on the clip and select “open in editor”. FCP will open Livetype for you and you can make your changes there. Once you save your changes, it will update it in FCP automatically. This saves you tons of exporting in livetype time.
Hope this helps.
-
David Bogie
May 26, 2006 at 5:00 pm> Thank you for the insult, but I do understand what safe areas are for. I am going to television, therefore, safe areas do matter. Because the text I am using isn’t in text form, I am wondering if I can go a little outside of the text safe area and still be okay.
< Nobody insulted you. You didn't know what you were talking about and we can't answer a question using your own made up terminology. You got the explanations you needed and you said thanks. Now you just need to say you're sorry. bogiesan This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
Reply to this Discussion! Login or Sign Up