Jonan Grobler
Forum Replies Created
-
You probably have the piece of music that you’re editing to underneath the clips, right? FCP doesn’t know how to deal with the Roll Tool or the shift-del command when there’s a sound file underneath that it wants to move around with the clips.
If you lock the music track, all should be fine.
Jonan Grobler
Editor/Motion Graphics
GTG MOTION PICTURES
filmstudio.co.za -
You can drag the Scale In behavior longer and shorter, to make it take longer/shorter.
Unless you have all the text under one Scale In behavior. Then I’d suggest breaking up the text into smaller chunks, and putting Scale In on them individually, adjusting each as you desire.
The constant/variable speed doesn’t apply to text, no, as Motion gives you enough control to change the timing of text animations. If you’d like to mess with variable speed, pull a movie file in and put in keyframes as you did, dragging them around in the Timeline to the desired location.
Jonan Grobler
Editor/Motion Graphics
GTG MOTION PICTURES
filmstudio.co.za -
Ah, thanks. I was dragging the correct font on from the Library. A pain. Thanks again.
Jonan Grobler
Editor/Motion Graphics
GTG MOTION PICTURES
filmstudio.co.za -
Nope, you’re going to have to reconnect the media from drive B.
-
Is there somewhere I can go to trash the Motion pref file? Can’t find it anywhere.
-
That’s what I do. But next time I start up Motion, and select text tool, it’s chosen the LiveFont “Nitro” for me. And the dropdown list of fonts in the HUD are all LiveFonts.
Grrr.
-
Hey man, I had a similar problem recently, was on a deadline, messed with codecs and framerates till I was blue in the face… till eventually, I changed the Internal Pixel Format (under User Prefs) from Floating Point to 10-bit. Anything over that, and the footage was messed up, with random blocks of green and black all over. I don’t have a clue why this should be; my iMac’s always handled floating point up till now. Was a pretty huge project though.
Give that a shot – maybe it works.
-
If your sound designer worked in a program that had a “sync” option, and it was set to NTSC specs, i.e. 23.97 fps or such, then FCP reads that sync info and it would cause exactly the problem you’re describing.
I’ve had the same problem before, causing me to pull my hair out. If you open the .WAV file in Finder, it should be the correct length. But when you pull it into FCP it magically changes length.
Get your sound designer to change his settings to 25fps, re-export, and all should be fine and dandy.
-
Do you have space left on your scratch disk – i.e. where your render files are being written to?
Other reasons this happens is if you have weird resolution photos in your timeline, or your computer is actually short on memory and it’s time to upgrade that RAM. You can try shutting all programs, reopening just Final Cut Pro, selecting just those clips, pressing (CMD + R) to render selection.
-
Well, it depends on the specs of the projector itself.
Seeing as you’re working with HD content though, I would definitely recommend changing the sequence settings to say 1280×720 (HD (960×720) (16:9)). This should be fine for most projectors.
Also, your photograph sizes aren’t optimal for the higher 1920×1080 resolution, you would have to zoom them up for that. So stick with 1280×720.